| /openbmc/linux/Documentation/leds/ |
| H A D | leds-class-flash.rst | 5 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
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/qcom/ |
| H A D | qcom,smd.yaml | 19 directly below the device node representing the respective remote subsystem
33 Each subnode of the SMD node represents a remote subsystem or a remote
44 # "rpm" subsystem. For the "rpm" subsystem we have a device tied to the
|
| /openbmc/linux/Documentation/mm/damon/ |
| H A D | maintainer-profile.rst | 6 The DAMON subsystem covers the files that are listed in 'DATA ACCESS MONITOR'
9 The mailing lists for the subsystem are damon@lists.linux.dev and
19 management subsystem maintainer. After more sufficient tests, the patches will
21 memory management subsystem maintainer.
45 mm-stable[3] trees depend on the memory management subsystem maintainer.
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A D | mport_cdev.rst | 2 RapidIO subsystem mport character device driver (rio_mport_cdev.c)
16 This driver (MPORT_CDEV) provides access to basic RapidIO subsystem operations
25 following RapidIO bus and subsystem operations:
56 - Manage device objects supported by RapidIO subsystem (RIO_DEV_ADD/RIO_DEV_DEL).
59 kernel RapidIO subsystem.
64 This device driver uses standard interfaces defined by kernel RapidIO subsystem
66 subsystem with limitations set by available mport implementation.
|
| /openbmc/linux/net/bluetooth/ |
| H A D | Kconfig | 3 # 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
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | MIGRATION.txt | 14 The subsystem itself has been converted and maintainers should submit patches
24 The subsystem itself has been converted along with many of the host controller
34 The subsystem itself has been converted along with many of the host controller
95 The PCI subsystem has supported driver model since mid 2015. Maintainers should
104 The video subsystem has supported driver model since early 2016. Maintainers
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | rapidio.rst | 18 subsystem internals.
39 subsystem to gather info on devices, request/map memory region
58 subsystem.
96 The following people have contributed to the RapidIO subsystem directly
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/recipes-amd/amd-fpga/files/ |
| H A D | ip-to-fpga.service | 3 BindsTo=sys-subsystem-net-devices-eth0.device
4 After=sys-subsystem-net-devices-eth0.device
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | index.rst | 6 Media subsystem kernel internal API
9 This section contains usage information about media subsystem and
16 - for usage information about media subsystem and supported drivers;
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | index.rst | 6 Media subsystem admin and user guide
9 This section contains usage information about media subsystem and
23 The media subsystem
|
| /openbmc/qemu/qapi/ |
| H A D | pci.json | 115 # @subsystem: the PCI subsystem id (since 3.1)
117 # @subsystem-vendor: the PCI subsystem vendor id (since 3.1)
122 'data': {'device': 'int', 'vendor': 'int', '*subsystem': 'int',
123 '*subsystem-vendor': 'int'} }
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/dhcpcd/files/ |
| H A D | dhcpcd@.service | 5 BindsTo=sys-subsystem-net-devices-%i.device
6 After=sys-subsystem-net-devices-%i.device
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | maintainer-entry-profile.rst | 8 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
|
| H A D | feature-and-driver-maintainers.rst | 17 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
149 to remember to include the maintainers in discussions and subsystem
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | hotplug.rst | 45 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
|
| H A D | writing_usb_driver.rst | 12 The Linux USB subsystem has grown from supporting only two different
44 excellent introduction to the Linux USB subsystem can be found at the
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
94 /* register this driver with the USB subsystem */
108 itself with the USB subsystem. This is done with usb_deregister()
113 /* deregister this driver with the USB subsystem */
188 subsystem. This can be seen in the following code::
217 called when the urb is finished by the USB subsystem. The callback
[all …]
|
| /openbmc/phosphor-net-ipmid/ |
| H A D | phosphor-ipmi-net@.service | 4 Requires=sys-subsystem-net-devices-%i.device
5 After=sys-subsystem-net-devices-%i.device
|
| /openbmc/linux/Documentation/devicetree/bindings/display/ |
| H A D | st,stih4xx.txt | 21 - sti-display-subsystem: Master device for DRM sub-components
25 - compatible: "st,sti-display-subsystem"
29 must be a child of sti-display-subsystem
45 must be a child of sti-display-subsystem
57 must be a child of sti-display-subsystem
74 must be a child of sti-display-subsystem
87 must be a child of sti-display-subsystem
102 must be a child of sti-display-subsystem
175 sti-display-subsystem {
176 compatible = "st,sti-display-subsystem";
|
| /openbmc/linux/drivers/fpga/tests/ |
| H A D | Kconfig | 2 bool "KUnit test for the FPGA subsystem" if !KUNIT_ALL_TESTS
6 This builds unit tests for the FPGA subsystem
|
| /openbmc/linux/drivers/rapidio/ |
| H A D | Kconfig | 33 this switch is set the RapidIO subsystem will enable all
52 bool "RapidIO subsystem debug messages"
55 Say Y here if you want the RapidIO subsystem to produce a bunch of
57 problem with the RapidIO subsystem and want to see more of what is
68 for RapidIO subsystem. You may select single built-in method or
|
| /openbmc/openpower-hw-diags/attn/pel/ |
| H A D | user_header.cpp | 27 void UserHeader::setSubsystem(uint8_t subsystem) in setSubsystem() argument
29 _eventSubsystem = subsystem; in setSubsystem()
|
| /openbmc/linux/drivers/cpuidle/ |
| H A D | Kconfig.powerpc | 12 through cpuidle subsystem.
21 through cpuidle subsystem.
|
| /openbmc/u-boot/drivers/net/ti/ |
| H A D | Kconfig | 10 subsystem found in the TI SoCs.
20 This driver supports the TI Keystone 2 Ethernet subsystem
|
| /openbmc/linux/Documentation/accel/ |
| H A D | introduction.rst | 7 The Linux compute accelerators subsystem is designed to expose compute
47 characteristics as those of GPUs, the accel subsystem will use the
48 DRM subsystem's code and functionality. i.e. the accel core code will
49 be part of the DRM subsystem and an accel device will be a new type of DRM
81 accel subsystem.
104 * `Initial discussion on the New subsystem for acceleration devices <https://lkml.org/lkml/2022/7/3…
105 * `patch-set to add the new subsystem <https://lkml.org/lkml/2022/10/22/544>`_ - Oded Gabbay (2022)
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | scsi.rst | 4 SCSI subsystem documentation
8 the SCSI subsystem in the Linux kernel (lk) 2.4 series. See:
12 Notes on using modules in the SCSI subsystem
25 the SCSI subsystem.
|