Home
last modified time | relevance | path

Searched refs:Device (Results 1 – 25 of 1724) sorted by relevance

12345678910>>...69

/linux/Documentation/PCI/endpoint/
A Dpci-endpoint-cfs.rst35 Creating EPF Device
44 ... <EPF Device 11>/
45 ... <EPF Device 21>/
46 ... <EPF Device 31>/
48 ... <EPF Device 12>/
49 ... <EPF Device 22>/
61 ... <EPF Device 11>/
72 ... <Symlink EPF Device 31>/
84 The <EPF Device> directory can have a list of symbolic links
85 (<Symlink EPF Device 31>) to other <EPF Device>. These symbolic links should
[all …]
A Dpci-ntb-howto.rst15 Endpoint Device
49 Creating pci-epf-ntb Device
81 Configuring pci-epf-ntb Device
111 Binding pci-epf-ntb Device to EP Controller
138 RootComplex Device
145 "Creating pci-epf-ntb Device" section above::
148 0000:00:00.0 PCI bridge: Texas Instruments Device b00d
149 0000:01:00.0 RAM memory: Texas Instruments Device b00d
152 Using ntb_hw_epf Device
A Dpci-test-howto.rst13 Endpoint Device
44 Creating pci-epf-test Device
75 Configuring pci-epf-test Device
88 Binding pci-epf-test Device to EP Controller
110 RootComplex Device
119 00:00.0 PCI bridge: Texas Instruments Device 8888 (rev 01)
120 01:00.0 Unassigned class [ff00]: Texas Instruments Device b500
123 Using Endpoint Test function Device
/linux/Documentation/firmware-guide/acpi/
A Di2c-muxes.rst8 Device () scope per mux channel.
19 Device (SMB1)
22 Device (MUX0)
31 Device (CH00)
35 Device (CLIA)
46 Device (CH01)
50 Device (CLIB)
A Dintel-pmc-mux.rst22 Device modes. The driver is located here: drivers/usb/typec/mux/intel_pmc_mux.c.
37 Device (CH0)
42 Device (CH1)
48 _PLD (Physical Location of Device)
56 Device (CH0)
67 Mux-agent specific _DSD Device Properties
119 Device (MUX)
123 Device (CH0)
138 Device (CH1)
A DDSD-properties-rules.rst4 _DSD Device Properties Usage Rules
10 The _DSD (Device Specific Data) configuration object, introduced in ACPI 5.1,
23 generic Device Properties UUID in the _DSD return package as specified in the
24 Device Properties UUID definition document [1]_.
27 that can be returned by _DSD in the Device Properties UUID sub-package for a
32 can be returned in the Device Properties UUID sub-package for the device in
48 Valid property sets must follow the guidance given by the Device Properties UUID
56 associated with the Device Properties UUID.
78 Property Sets and Device Tree Bindings
81 It often is useful to make _DSD return property sets that follow Device Tree
A Denumeration.rst4 ACPI Based Device Enumeration
125 Device (I2C0)
155 Device (EEP0)
194 Device (EEP0)
268 Device (DEV)
303 Device (DEV)
460 Device (TMP0)
572 Device (RP02)
595 Device (BRG1) //Bridge
599 Device (BRG2) //Bridge
[all …]
/linux/drivers/scsi/device_handler/
A DKconfig3 # SCSI Device Handler configuration
7 bool "SCSI Device Handlers"
11 SCSI Device Handlers provide device specific support for
16 tristate "LSI RDAC Device Handler"
22 tristate "HP/COMPAQ MSA Device Handler"
30 tristate "EMC CLARiiON Device Handler"
36 tristate "SPC-3 ALUA Device Handler"
39 SCSI Device handler for generic SPC-3 Asymmetric Logical Unit
/linux/Documentation/driver-api/
A Dinfrastructure.rst1 Device drivers infrastructure
4 The Basic Device Driver-Model Structures
11 Device Drivers Base
47 Device Drivers DMA Management
53 Device drivers PnP support
/linux/Documentation/devicetree/bindings/usb/
A Dlpc32xx-udc.txt1 * NXP LPC32xx SoC USB Device Controller (UDC)
8 * USB Device Low Priority Interrupt
9 * USB Device High Priority Interrupt
10 * USB Device DMA Interrupt
/linux/Documentation/admin-guide/auxdisplay/
A Dks0108.rst24 2. Device Information
28 :Device Name: KS0108 LCD Controller
29 :Device Code: ks0108
31 :Device Webpage: -
/linux/sound/soc/img/
A DKconfig8 tristate "Imagination I2S Input Device Driver"
16 tristate "Imagination I2S Output Device Driver"
24 tristate "Imagination Parallel Output Device Driver"
32 tristate "Imagination SPDIF Input Device Driver"
40 tristate "Imagination SPDIF Output Device Driver"
/linux/arch/arm/mach-spear/
A DKconfig30 bool "SPEAr1310 Machine support with Device Tree"
37 bool "SPEAr1340 Machine support with Device Tree"
57 bool "SPEAr300 Machine support with Device Tree"
63 bool "SPEAr310 Machine support with Device Tree"
69 bool "SPEAr320 Machine support with Device Tree"
/linux/Documentation/hwmon/
A Dsmsc47b397.rst41 HWM Base address can be obtained from Logical Device 8, registers 0x60 (MSB)
126 a. Write the index of the Logical Device Number Configuration Register
146 The following is an example of how to read the SIO Device ID located at 0x20:
164 The registers of interest for identifying the SIO on the dc7100 are Device ID
165 (0x20) and Device Rev (0x21).
167 The Device ID will read 0x6F (0x81 for SCH5307-NS, and 0x85 for SCH5317)
168 The Device Rev currently reads 0x01
174 Logical Device 8::
187 OUT DX,AL;Point to Logical Device 8
/linux/Documentation/userspace-api/media/mediactl/
A Dmedia-types.rst302 - Device node interface for video (V4L)
306 - Device node interface for VBI (V4L)
310 - Device node interface for radio (V4L)
314 - Device node interface for a V4L subdevice
326 - Device node interface for ALSA PCM Capture
330 - Device node interface for ALSA PCM Playback
334 - Device node interface for ALSA Control
338 - Device node interface for ALSA Compress
342 - Device node interface for ALSA Raw MIDI
350 - Device node interface for ALSA Sequencer
[all …]
/linux/Documentation/arm/
A Dmicrochip.rst205 Device Tree for AT91 SoCs and boards
207 All AT91 SoCs are converted to Device Tree. Since Linux 3.19, these products
211 Device Tree files and Device Tree bindings that apply to AT91 SoCs and boards are
213 any time. So, be sure to use a Device Tree Binary and a Kernel Image generated from
221 - SoCs Device Tree Source Include files are named after the official name of
223 - Device Tree Source Include files (.dtsi) are used to collect common nodes that can be
228 - board Device Tree Source files (.dts) are prefixed by the string "at91-" so
/linux/drivers/of/
A DKconfig6 bool "Device Tree and Open Firmware support"
16 bool "Device Tree runtime unit tests"
29 bool "Build all Device Tree Blobs"
33 This option builds all possible Device Tree Blobs (DTBs) for the
80 bool "Device Tree overlays"
/linux/Documentation/firmware-guide/acpi/dsd/
A Dleds.rst14 Referring to LEDs in Device tree is documented in [4], in "flash-leds" property
17 While Device tree allows referring to any node in the tree[1], in ACPI
40 Device (LED)
69 Device (SEN)
93 [1] Device tree. https://www.devicetree.org, referenced 2019-02-21.
103 [5] Device Properties UUID For _DSD.
A Dphy.rst16 These properties are defined in accordance with the "Device
18 daffd814-6eba-4d8c-8a91-bc9bbf4aa301 UUID must be used in the Device
34 Device(PHY1) {
38 Device(PHY2) {
84 Device(MDI0) {
106 Device(PHY1) {
110 Device(PHY2) {
/linux/arch/arm/mach-sti/
A DKconfig23 STiH418 family SoCs using the Device Tree for discovery. More
35 and other digital audio/video applications using Flattned Device
44 and other digital audio/video applications using Flattened Device
54 and other digital audio/video applications using Flattened Device
/linux/drivers/usb/class/
A DKconfig5 comment "USB Device Class drivers"
12 Communication Device Class Abstract Control Model interface.
32 tristate "USB Wireless Device Management support"
34 This driver supports the WMC Device Management functionality
/linux/Documentation/ABI/testing/
A Dsysfs-block-dm5 Description: Device-mapper device name.
13 Description: Device-mapper device UUID.
22 Description: Device-mapper device suspend state.
45 Description: Request-based Device-mapper blk-mq I/O path mode.
/linux/drivers/staging/media/av7110/
A Daudio-get-status.rst41 - Returns the current state of Audio Device.
46 This ioctl call asks the Audio Device to return the current state of the
47 Audio Device.
A Daudio-fopen.rst72 the Linux manual page for fcntl. Only one user can open the Audio Device
74 fail, and an error code will be returned. If the Audio Device is opened
91 - Device driver not loaded/available.
97 - Device or resource busy.
A Dvideo-fopen.rst74 user can open the Video Device in O_RDWR mode. All other attempts to
76 returned. If the Video Device is opened in O_RDONLY mode, the only
93 - Device driver not loaded/available.
105 - Device or resource busy.

Completed in 38 milliseconds

12345678910>>...69