Home
last modified time | relevance | path

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

12345678910>>...120

/linux-6.12.1/Documentation/dev-tools/kunit/
Dstyle.rst24 suite is a group of tests which test a related area of the kernel. A subsystem
25 is a set of test suites which test different parts of a kernel subsystem
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
33 test subsystem should match a single kernel module. If the code being tested
34 cannot be compiled as a module, in many cases the subsystem should correspond to
42 If a test subsystem name has multiple components, they should be separated by
43 underscores. *Do not* include "test" or "kunit" directly in the subsystem name
64 suffix. ``qos`` is also ambiguous as a subsystem name, because several parts
65 of the kernel have a ``qos`` subsystem. ``power_qos`` would be a better name.
67 The corresponding module name is ``parport_pc``, so this subsystem should also
[all …]
/linux-6.12.1/arch/arm/mach-pxa/
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 …]
/linux-6.12.1/Documentation/filesystems/
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,
300 mkdir(2) in the group's directory. The subsystem allocates a new
305 If the subsystem wants the child to be a group itself, the subsystem
[all …]
/linux-6.12.1/drivers/target/
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
/linux-6.12.1/Documentation/admin-guide/cgroup-v1/
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
109 At one extreme, each resource controller or subsystem could be in a
181 cgroup_subsys_state objects, one for each cgroup subsystem
186 subsystem state is something that's expected to happen frequently
219 It's not currently possible to bind a new subsystem to an active
220 cgroup hierarchy, or to unbind a subsystem from an active cgroup
[all …]
/linux-6.12.1/Documentation/driver-api/rapidio/
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 …]
/linux-6.12.1/Documentation/admin-guide/
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 …]
/linux-6.12.1/Documentation/maintainer/
Dfeature-and-driver-maintainers.rst17 subsystem.
28 a subsystem could well have a hundred such drivers. Subsystem
31 The exact expectations on the response time will vary by subsystem.
32 The patch review SLA the subsystem had set for itself can sometimes
33 be found in the subsystem documentation. Failing that as a rule of thumb
35 review delay of the subsystem maintainer. The resulting expectations
43 Maintainers must be subscribed and follow the appropriate subsystem-wide
63 than the expected review timeline for the subsystem, maintainer should
90 should be conducted in a manner typical for the larger subsystem.
154 Subsystem maintainers may remove inactive maintainers from the MAINTAINERS
[all …]
Dmaintainer-entry-profile.rst8 subsystem/device-driver-local customs as well as details about the patch
17 Provide an introduction to how the subsystem operates. While MAINTAINERS
19 convey other subsystem-local infrastructure and mechanisms that aid
26 - Does the subsystem have a patchwork instance? Are patchwork state
29 testing feedback that the subsystem uses to gate acceptance?
33 device-driver may point to an entry for its parent subsystem. This makes
46 of related hardware specifications. For example, does the subsystem
/linux-6.12.1/drivers/pinctrl/qcom/
DKconfig59 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
68 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
77 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
86 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
95 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
104 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
114 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
123 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
132 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
142 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
/linux-6.12.1/Documentation/admin-guide/aoe/
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"
/linux-6.12.1/samples/configfs/
Dconfigfs_sample.c22 * This first example is a childless subsystem. It cannot create
26 * This is not necessary if a subsystem has no attributes directly
27 * on the subsystem. See the next example, 02-simple-children, for
28 * such a subsystem.
77 "The childless subsystem is the simplest possible subsystem in\n" in childless_description_show()
118 * subsystem, as it has no attributes of its own.
202 "This subsystem allows the creation of child config_items. These\n" in simple_children_description_show()
252 * the simple_children group is not the subsystem itself, it is a
253 * child of the subsystem. Creation of a group in the subsystem creates
280 "This subsystem allows the creation of child config_groups. These\n" in group_children_description_show()
[all …]
/linux-6.12.1/Documentation/driver-api/media/
Dmaintainer-entry-profile.rst1 Media Subsystem Profile
7 The media subsystem covers support for a variety of devices: stream
24 by them before being merged via the media subsystem's development
29 add new features to the subsystem must also bring changes to the
32 Due to the size and wide scope of the media subsystem, media's
34 knowledge of a specific aspect of the subsystem. It is the sub-maintainers'
36 following the subsystem rules and are properly using the media kernel and
39 Patches for the media subsystem must be sent to the media mailing list
66 At the media subsystem, we have a group of senior developers that
69 subsystem as a whole. For core changes, whenever possible, multiple
[all …]
/linux-6.12.1/drivers/remoteproc/
Dqcom_common.c55 * struct minidump_subsystem - Subsystem's SMEM Table of content
56 * @status : Subsystem toc init status
58 * @encryption_status: Encryption status for this subsystem
59 * @encryption_required : Decides to encrypt the subsystem regions or not
60 * @region_count : Number of regions added in this subsystem toc
61 * @regions_baseptr : regions base pointer of the subsystem
106 static int qcom_add_minidump_segments(struct rproc *rproc, struct minidump_subsystem *subsystem, in qcom_add_minidump_segments() argument
122 seg_cnt = le32_to_cpu(subsystem->region_count); in qcom_add_minidump_segments()
123 ptr = ioremap((unsigned long)le64_to_cpu(subsystem->regions_baseptr), in qcom_add_minidump_segments()
152 struct minidump_subsystem *subsystem; in qcom_minidump() local
[all …]
/linux-6.12.1/Documentation/driver-api/usb/
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`
76 another kernel subsystem, such as the SCSI, network or TTY subsystem.
78 subsystem, and any user-space interactions are provided through that
79 interface. But for drivers that do not have a matching kernel subsystem,
81 is needed. The USB subsystem provides a way to register a minor device
94 /* register this driver with the USB subsystem */
[all …]
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
/linux-6.12.1/drivers/net/ethernet/ti/
DKconfig89 the CPSW Ethernet Switch and Keystone 2 1g/10g Switch Subsystem.
106 This driver supports TI K3 AM654/J721E CPSW2G Ethernet SubSystem.
107 The two-port Gigabit Ethernet MAC (MCU_CPSW0) subsystem provides
135 and PCIe Subsystem Precision Time Measurement (PTM).
162 tristate "TI Keystone NETCP Ethernet subsystem Support"
195 Support dual Gigabit Ethernet ports over the ICSSG PRU Subsystem.
196 This subsystem is available starting with the AM65 platform.
211 Support dual Gigabit Ethernet ports over the ICSSG PRU Subsystem.
212 This subsystem is available on the AM65 SR1.0 platform.
225 Peripheral within a PRU-ICSS subsystem present on various TI SoCs.
/linux-6.12.1/Documentation/driver-api/fpga/
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
/linux-6.12.1/net/bluetooth/
DKconfig3 # Bluetooth subsystem configuration
7 tristate "Bluetooth subsystem support"
26 Linux Bluetooth subsystem consist of several layers:
42 To use Linux Bluetooth subsystem, you will need several user-space
125 Run self tests when initializing the Bluetooth subsystem. This
129 When the Bluetooth subsystem is built as module, then the test
131 subsystem is compiled into the kernel image, then the test cases
/linux-6.12.1/Documentation/timers/
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 …]
/linux-6.12.1/Documentation/doc-guide/
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.
48 I am the sole maintainer for the documentation subsystem, and I am doing
/linux-6.12.1/include/linux/
Dhte.h28 * enum hte_return - HTE subsystem return values used during callback.
32 * HTE subsystem calls secondary callback provided by the consumer where it
107 * This structure is a communication token between consumers to subsystem
108 * and subsystem to providers.
111 * @hte_data: Subsystem's private data, set by HTE subsystem.
131 * success HTE subsystem fills up provided struct hte_clk_info.
133 * xlated_id parameter is used to communicate between HTE subsystem and the
160 * @gdev: HTE subsystem abstract device, internal to the HTE subsystem.
/linux-6.12.1/sound/pci/emu10k1/
Demu10k1_main.c945 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10241102,
991 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,
1018 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10011102,
1057 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x20011102,
1070 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x42011102,
1083 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40041102,
1097 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40071102,
1109 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40011102,
1119 {.vendor = 0x1102, .device = 0x0008, .subsystem = 0x40021102,
1130 {.vendor = 0x1102, .device = 0x0004, .subsystem = 0x40021102,
[all …]
/linux-6.12.1/Documentation/leds/
Dleds-class-flash.rst5 Some LED devices provide two modes - torch and flash. In the LED subsystem
13 registered in the LED subsystem with led_classdev_flash_register function.
29 A LED subsystem driver can be controlled also from the level of VideoForLinux2
30 subsystem. In order to enable this CONFIG_V4L2_FLASH_LED_CLASS symbol has to
34 V4L2 subsystem. The function takes six arguments:
88 Opening the V4L2 flash sub-device makes the LED subsystem sysfs interface
/linux-6.12.1/drivers/platform/surface/
DKconfig76 tristate "Surface System Aggregator Module Subsystem Device Hubs"
80 Device-hub drivers for Surface System Aggregator Module (SSAM) subsystem
83 Provides subsystem hub drivers which manage client devices on various
84 SSAM subsystems. In some subsystems, notably the BAS subsystem managing
85 devices contained in the base of the Surface Book 3 and the KIP subsystem
100 respective subsystem hubs. Both drivers and device specification (e.g.
136 using the KIP subsystem for detachable keyboards (e.g. keyboard covers)
137 or the POS subsystem for device/screen posture changes.
139 The KIP subsystem is used on newer Surface generations to handle
142 subsystem is used for device posture change notifications on the Surface

12345678910>>...120