Home
last modified time | relevance | path

Searched full:subsystem (Results 1 – 25 of 2749) sorted by relevance

12345678910>>...110

/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/linuxconsole/linuxconsole/
H A D51-these-are-not-joysticks-rm.rules6 SUBSYSTEM=="input", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c30a", ENV{ID_INPUT_JOYSTICK}=="?*"…
7 SUBSYSTEM=="input", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c30a", KERNEL=="js[0-9]*", RUN+="/b…
8 SUBSYSTEM=="input", ATTRS{idVendor}=="04d9", ATTRS{idProduct}=="a0df", ENV{ID_INPUT_JOYSTICK}=="?*"…
9 SUBSYSTEM=="input", ATTRS{idVendor}=="04d9", ATTRS{idProduct}=="a0df", KERNEL=="js[0-9]*", RUN+="/b…
10 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0010", ENV{ID_INPUT_JOYSTICK}=="?*"…
11 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0010", KERNEL=="js[0-9]*", RUN+="/b…
12 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0011", ENV{ID_INPUT_JOYSTICK}=="?*"…
13 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0011", KERNEL=="js[0-9]*", RUN+="/b…
14 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0012", ENV{ID_INPUT_JOYSTICK}=="?*"…
15 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0012", KERNEL=="js[0-9]*", RUN+="/b…
[all …]
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/udev/eudev/
H A Dpermissions.rules6 SUBSYSTEM=="scsi", KERNEL=="[0-9]*:[0-9]*", WAIT_FOR_SYSFS="ioerr_cnt"
8 SUBSYSTEM=="net", WAIT_FOR_SYSFS="address"
10 SUBSYSTEM=="net", ENV{DRIVER}=="?*", WAIT_FOR_SYSFS="device/driver"
18 SUBSYSTEM=="block", GROUP="disk"
20 SUBSYSTEM=="block", ATTRS{removable}=="1", \
23 SUBSYSTEM=="block", SUBSYSTEMS=="usb|ieee1394|mmc|pcmcia", GROUP="floppy"
48 SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", \
52 SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GROUP="plugdev", \
56 SUBSYSTEM=="tty", GROUP="dialout"
57 SUBSYSTEM=="capi", GROUP="dialout"
[all …]
H A Dinit61 PLATFORM_BUS_NOMATCH="--subsystem-nomatch=platform"
65 …subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole…
/OK3568_Linux_fs/kernel/Documentation/dev-tools/kunit/
H A Dstyle.rst25 the kernel, and a subsystem is a set of test suites which test different parts
26 of the same kernel subsystem or driver.
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
33 rule of thumb is that a test subsystem should match a single kernel module. If
34 the code being tested can't be compiled as a module, in many cases the subsystem
43 If a test subsystem name has multiple components, they should be separated by
44 underscores. *Do not* include "test" or "kunit" directly in the subsystem name
66 suffix, and ``qos`` is ambiguous as a subsystem name. ``power_qos`` would be a
69 The corresponding module name is ``parport_pc``, so this subsystem should also
86 Test suites are named after the subsystem they are part of. If a subsystem
[all …]
/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A Dconfigfs.rst50 subsystems. Once a client subsystem is loaded, it will appear as a
122 object in the subsystem. It has attributes that match values on that
124 and its attributes, allowing the subsystem to ignore all but the
132 A subsystem is the top level of a client module. During initialization,
133 the client module registers the subsystem with configfs, the subsystem
135 subsystem is also a config_group, and can do everything a config_group
162 structure that actually represents what the subsystem is doing. The
176 Usually a subsystem wants the item to display and/or store attributes,
301 mkdir(2) in the group's directory. The subsystem allocates a new
306 If the subsystem wants the child to be a group itself, the subsystem
[all …]
/OK3568_Linux_fs/kernel/drivers/input/touchscreen/gt1x/
H A Dgt1x_update.c69 15 6 TP subsystem PID
70 21 3 TP subsystem version
71 24 1 subsystem count
74 32 8 subsystem info[0]
75 32 8 subsystem info[1]
77 120 8 subsystem info[11]
79 128 N0 subsystem[0]
80 128+N0 N1 subsystem[1]
82 2. subsystem info structure
84 0 1 subsystem type
[all …]
/OK3568_Linux_fs/kernel/Documentation/admin-guide/cgroup-v1/
H A Dcgroups.rst34 3.3 Subsystem API
53 A *subsystem* is a module that makes use of the task grouping
55 particular ways. A subsystem is typically a "resource controller" that
58 virtualization subsystem.
62 hierarchy, and a set of subsystems; each subsystem has system-specific
107 At one extreme, each resource controller or subsystem could be in a
179 cgroup_subsys_state objects, one for each cgroup subsystem
184 subsystem state is something that's expected to happen frequently
217 It's not currently possible to bind a new subsystem to an active
218 cgroup hierarchy, or to unbind a subsystem from an active cgroup
[all …]
/OK3568_Linux_fs/kernel/Documentation/driver-api/rapidio/
H A Drapidio.rst10 This document describes the basics of the Linux RapidIO subsystem and provides
16 Because the RapidIO subsystem follows the Linux device model it is integrated
20 The Linux RapidIO subsystem is architecture independent and therefore defines
22 subsystem operations.
28 Each of these components is represented in the subsystem by an associated data
29 structure. The core logical components of the RapidIO subsystem are defined
37 packets (transactions). In the RapidIO subsystem each master port is represented
43 RapidIO master ports are serviced by subsystem specific mport device drivers
44 that provide functionality defined for this subsystem. To provide a hardware
45 independent interface for RapidIO subsystem operations, rio_mport structure
[all …]
/OK3568_Linux_fs/kernel/arch/arm/mach-pxa/include/mach/
H A Dpxa3xx-regs.h40 #define ASCR __REG(0x40f40000) /* Application Subsystem Power Status/Configuration */
41 #define ARSR __REG(0x40f40004) /* Application Subsystem Reset Status */
42 #define AD3ER __REG(0x40f40008) /* Application Subsystem Wake-Up from D3 Enable */
43 #define AD3SR __REG(0x40f4000c) /* Application Subsystem Wake-Up from D3 Status */
44 #define AD2D0ER __REG(0x40f40010) /* Application Subsystem Wake-Up from D2 to D0 Enable */
45 #define AD2D0SR __REG(0x40f40014) /* Application Subsystem Wake-Up from D2 to D0 Status */
46 #define AD2D1ER __REG(0x40f40018) /* Application Subsystem Wake-Up from D2 to D1 Enable */
47 #define AD2D1SR __REG(0x40f4001c) /* Application Subsystem Wake-Up from D2 to D1 Status */
48 #define AD1D0ER __REG(0x40f40020) /* Application Subsystem Wake-Up from D1 to D0 Enable */
49 #define AD1D0SR __REG(0x40f40024) /* Application Subsystem Wake-Up from D1 to D0 Status */
[all …]
/OK3568_Linux_fs/kernel/drivers/target/
H A DKconfig14 subsystem logic for virtual LUN 0 access
19 tristate "TCM/IBLOCK Subsystem Plugin for Linux/BLOCK"
22 Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
26 tristate "TCM/FILEIO Subsystem Plugin for Linux/VFS"
28 Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
32 tristate "TCM/pSCSI Subsystem Plugin for Linux/SCSI"
35 Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
39 tristate "TCM/USER Subsystem Plugin for Linux"
42 Say Y here to enable the TCM/USER subsystem plugin for a userspace
/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dsysfs-rules.rst68 - subsystem (``block``, ``tty``, ``pci``, ...)
71 - retrieved by reading the "subsystem"-link and using only the
108 - Classification by subsystem
115 classification directories into one place at ``/sys/subsystem``,
117 classes, including the converted block subsystem, will show up
119 The devices belonging to a subsystem will create a symlink in the
120 "devices" directory at ``/sys/subsystem/<name>/devices``,
122 If ``/sys/subsystem`` exists, ``/sys/bus``, ``/sys/class`` and ``/sys/block``
124 places, as the kernel is free to move a subsystem from one place to
126 subsystem name.
[all …]
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/systemd/systemd/
H A Dinit81 …subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole…
/OK3568_Linux_fs/buildroot/board/kontron/smarc-sal28/rootfs_overlay/etc/udev/rules.d/
H A D70-enetc-networking.rules1 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.0", DRIVERS=="fsl_enetc", NAME="eno0"
2 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.1", DRIVERS=="fsl_enetc", NAME="eno1"
3 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.2", DRIVERS=="fsl_enetc", NAME="eno2"
4 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.6", DRIVERS=="fsl_enetc", NAME="eno3"
5 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.0", DRIVERS=="fsl_enetc_vf", NAME="eno0vf0"
6 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.1", DRIVERS=="fsl_enetc_vf", NAME="eno0vf1"
7 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.2", DRIVERS=="fsl_enetc_vf", NAME="eno1vf0"
8 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.3", DRIVERS=="fsl_enetc_vf", NAME="eno1vf1"
H A D70-felix-networking.rules1 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_nam…
2 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_nam…
3 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_nam…
4 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_nam…
5 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_nam…
6 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_nam…
H A D71-smarc-networking.rules8 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.1", DRIVERS=="fsl_enetc", ENV{sl28_compatible…
11 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_nam…
12 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_nam…
15 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.0", DRIVERS=="fsl_enetc", ENV{sl28_compatible…
18 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.0", DRIVERS=="fsl_enetc", ENV{sl28_compatible…
19 ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.1", DRIVERS=="fsl_enetc", ENV{sl28_compatible…
/OK3568_Linux_fs/kernel/samples/configfs/
H A Dconfigfs_sample.c24 * This first example is a childless subsystem. It cannot create
28 * This is not necessary if a subsystem has no attributes directly
29 * on the subsystem. See the next example, 02-simple-children, for
30 * such a subsystem.
79 "The childless subsystem is the simplest possible subsystem in\n" in childless_description_show()
120 * subsystem, as it has no attributes of its own.
204 "This subsystem allows the creation of child config_items. These\n" in simple_children_description_show()
254 * the simple_children group is not the subsystem itself, it is a
255 * child of the subsystem. Creation of a group in the subsystem creates
282 "This subsystem allows the creation of child config_groups. These\n" in group_children_description_show()
[all …]
/OK3568_Linux_fs/kernel/Documentation/admin-guide/aoe/
H A Dudev.txt3 # 8 udev manpage to see whether your udev supports SUBSYSTEM, and
4 # whether it uses one or two equal signs for SUBSYSTEM and KERNEL.
19 SUBSYSTEM=="aoe", KERNEL=="discover", NAME="etherd/%k", GROUP="disk", MODE="0220"
20 SUBSYSTEM=="aoe", KERNEL=="err", NAME="etherd/%k", GROUP="disk", MODE="0440"
21 SUBSYSTEM=="aoe", KERNEL=="interfaces", NAME="etherd/%k", GROUP="disk", MODE="0220"
22 SUBSYSTEM=="aoe", KERNEL=="revalidate", NAME="etherd/%k", GROUP="disk", MODE="0220"
23 SUBSYSTEM=="aoe", KERNEL=="flush", NAME="etherd/%k", GROUP="disk", MODE="0220"
/OK3568_Linux_fs/kernel/Documentation/driver-api/usb/
H A Dwriting_usb_driver.rst12 The Linux USB subsystem has grown from supporting only two different
44 excellent introduction to the Linux USB subsystem can be found at the
46 subsystem is structured and introduces the reader to the concept of USB
50 the Linux USB subsystem, giving it some information about which devices
53 information is passed to the USB subsystem in the :c:type:`usb_driver`
73 another kernel subsystem, such as the SCSI, network or TTY subsystem.
75 subsystem, and any user-space interactions are provided through that
76 interface. But for drivers that do not have a matching kernel subsystem,
78 is needed. The USB subsystem provides a way to register a minor device
91 /* register this driver with the USB subsystem */
[all …]
H A Dhotplug.rst45 The /sbin/hotplug program can be invoked by any subsystem as part of its
46 reaction to a configuration change, from a thread in that subsystem.
47 Only one parameter is required: the name of a subsystem being notified of
50 the subsystem making that invocation.
62 The USB subsystem currently invokes ``/sbin/hotplug`` when USB devices
122 Most USB device drivers should pass these tables to the USB subsystem as
123 well as to the module management subsystem. Not all, though: some driver
127 Drivers that connect directly to the USB subsystem should be declared
145 When the USB subsystem knows about a driver's device ID table, it's used when
/OK3568_Linux_fs/kernel/Documentation/power/
H A Druntime_pm.rst54 are executed by the PM core for the device's subsystem that may be either of
67 If the subsystem chosen by applying the above rules doesn't provide the relevant
75 are referred to as subsystem-level callbacks in what follows.
86 The subsystem-level suspend callback, if present, is _entirely_ _responsible_
90 callback in a device driver as long as the subsystem-level suspend callback
93 * Once the subsystem-level suspend callback (or the driver suspend callback,
121 The subsystem-level resume callback, if present, is **entirely responsible** for
125 callback in a device driver as long as the subsystem-level resume callback knows
128 * Once the subsystem-level resume callback (or the driver resume callback, if
140 The idle callback (a subsystem-level one, if present, or the driver one) is
[all …]
/OK3568_Linux_fs/kernel/net/bluetooth/
H A DKconfig3 # Bluetooth subsystem configuration
7 tristate "Bluetooth subsystem support"
26 Linux Bluetooth subsystem consist of several layers:
41 To use Linux Bluetooth subsystem, you will need several user-space
114 Run self tests when initializing the Bluetooth subsystem. This
118 When the Bluetooth subsystem is built as module, then the test
120 subsystem is compiled into the kernel image, then the test cases
/OK3568_Linux_fs/kernel/Documentation/driver-api/fpga/
H A Dintro.rst4 The FPGA subsystem supports reprogramming FPGAs dynamically under
7 * The FPGA subsystem is vendor agnostic.
9 * The FPGA subsystem separates upper layers (userspace interfaces and
27 this is the subsystem for you. Low level FPGA manager drivers contain
28 the knowledge of how to program a specific device. This subsystem
40 of an FPGA. This subsystem includes fpga-bridge.c and the low level
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-bus-iio-counter-104-quad-89 This interface is deprecated; please use the Counter subsystem.
18 This interface is deprecated; please use the Counter subsystem.
54 This interface is deprecated; please use the Counter subsystem.
64 This interface is deprecated; please use the Counter subsystem.
73 This interface is deprecated; please use the Counter subsystem.
96 This interface is deprecated; please use the Counter subsystem.
106 This interface is deprecated; please use the Counter subsystem.
115 This interface is deprecated; please use the Counter subsystem.
/OK3568_Linux_fs/kernel/Documentation/timers/
H A Dhrtimers.rst2 hrtimers - subsystem for high-resolution kernel timers
5 This patch introduces a new subsystem for high-resolution kernel timers.
7 One might ask the question: we already have a timer subsystem
36 - the implementation of the current posix-timer subsystem on top of
51 largely expect the timer subsystem to have near-zero overhead.
62 high-resolution timer subsystem as well.
64 While this subsystem does not offer high-resolution clock sources just
65 yet, the hrtimer subsystem can be easily extended with high-resolution
75 hrtimers. E.g. we could decrease the frequency of the timeout subsystem
78 hrtimer subsystem implementation details
[all …]
/OK3568_Linux_fs/kernel/Documentation/doc-guide/
H A Dmaintainer-profile.rst3 Documentation subsystem maintainer entry profile
6 The documentation "subsystem" is the central coordinating point for the
12 It's worth noting, though, that the boundaries of this subsystem are rather
13 fuzzier than normal. Many other subsystem maintainers like to keep control
17 always) maintained by the relevant subsystem maintainer.
41 I am the sole maintainer for the documentation subsystem, and I am doing

12345678910>>...110