Searched refs:Device (Results 1 – 25 of 1912) sorted by relevance
12345678910>>...77
35 Creating EPF Device44 ... <EPF Device 11>/45 ... <EPF Device 21>/46 ... <EPF Device 31>/48 ... <EPF Device 12>/49 ... <EPF Device 22>/56 (These entries are created by the framework when any new <EPF Device> is61 ... <EPF Device 11>/72 ... <Symlink EPF Device 31>/84 The <EPF Device> directory can have a list of symbolic links[all …]
15 Endpoint Device45 Creating pci-epf-vntb Device77 Configuring pci-epf-vntb Device112 Binding pci-epf-ntb Device to EP Controller133 RootComplex Device140 "Creating pci-epf-ntb Device" section above::143 00:00.0 PCI bridge: Freescale Semiconductor Inc Device 0000 (rev 01)144 01:00.0 RAM memory: Freescale Semiconductor Inc Device 0809146 Endpoint Device / Virtual PCI bus153 "Creating pci-epf-ntb Device" section above::[all …]
15 Endpoint Device49 Creating pci-epf-ntb Device81 Configuring pci-epf-ntb Device111 Binding pci-epf-ntb Device to EP Controller138 RootComplex Device145 "Creating pci-epf-ntb Device" section above::148 0000:00:00.0 PCI bridge: Texas Instruments Device b00d149 0000:01:00.0 RAM memory: Texas Instruments Device b00d152 Using ntb_hw_epf Device
13 Endpoint Device44 Creating pci-epf-test Device75 Configuring pci-epf-test Device88 Binding pci-epf-test Device to EP Controller110 RootComplex Device119 00:00.0 PCI bridge: Texas Instruments Device 8888 (rev 01)120 01:00.0 Unassigned class [ff00]: Texas Instruments Device b500123 Using Endpoint Test function Device
8 Device () scope per mux channel.19 Device (SMB1)22 Device (MUX0)31 Device (CH00)35 Device (CLIA)46 Device (CH01)50 Device (CLIB)
4 _DSD Device Properties Usage Rules10 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 the25 "Device Properties UUID" in _DSD (Device Specific Data) Implementation Guide29 that can be returned by _DSD in the Device Properties UUID sub-package for a34 can be returned in the Device Properties UUID sub-package for the device in42 "Hierarchical Data Extension UUID" in _DSD (Device Specific Data)52 Valid property sets must follow the guidance given by the Device Properties UUID60 associated with the Device Properties UUID.82 Property Sets and Device Tree Bindings[all …]
22 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 Properties119 Device (MUX)123 Device (CH0)138 Device (CH1)
4 ACPI Based Device Enumeration26 As both ACPI and Device Tree represent a tree of devices (and their27 resources) this implementation follows the Device Tree way as much as124 Device (I2C0)157 Device (DEV0) {192 Device (EEP0)228 Device (EEP0)295 Device (DEV)325 the device to the driver. ACPI 5.1 extended this with _DSD (Device330 Device (DEV)[all …]
3 # SCSI Device Handler configuration7 bool "SCSI Device Handlers"11 SCSI Device Handlers provide device specific support for16 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
1 Device drivers infrastructure4 The Basic Device Driver-Model Structures11 Device Drivers Base47 Device Drivers DMA Management53 Device drivers PnP support
1 * NXP LPC32xx SoC USB Device Controller (UDC)8 * USB Device Low Priority Interrupt9 * USB Device High Priority Interrupt10 * USB Device DMA Interrupt
24 2. Device Information28 :Device Name: KS0108 LCD Controller29 :Device Code: ks010831 :Device Webpage: -
8 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"
30 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"
3 // Device Tree Source for UniPhier PXs3 Reference Board (for USB-Device #0)12 model = "UniPhier PXs3 Reference Board (USB-Device #0)";
3 // Device Tree Source for UniPhier PXs3 Reference Board (for USB-Device #1)12 model = "UniPhier PXs3 Reference Board (USB-Device #1)";
41 HWM Base address can be obtained from Logical Device 8, registers 0x60 (MSB)126 a. Write the index of the Logical Device Number Configuration Register146 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 ID165 (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 0x01174 Logical Device 8::187 OUT DX,AL;Point to Logical Device 8
23 STiH418 family SoCs using the Device Tree for discovery. More35 and other digital audio/video applications using Flattned Device44 and other digital audio/video applications using Flattened Device54 and other digital audio/video applications using Flattened Device
6 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 the80 bool "Device Tree overlays"
41 - Returns the current state of Audio Device.46 This ioctl call asks the Audio Device to return the current state of the47 Audio Device.
72 the Linux manual page for fcntl. Only one user can open the Audio Device74 fail, and an error code will be returned. If the Audio Device is opened91 - Device driver not loaded/available.97 - Device or resource busy.
205 Device Tree for AT91 SoCs and boards207 All AT91 SoCs are converted to Device Tree. Since Linux 3.19, these products211 Device Tree files and Device Tree bindings that apply to AT91 SoCs and boards are213 any time. So, be sure to use a Device Tree Binary and a Kernel Image generated from221 - SoCs Device Tree Source Include files are named after the official name of223 - Device Tree Source Include files (.dtsi) are used to collect common nodes that can be228 - board Device Tree Source files (.dts) are prefixed by the string "at91-" so
282 - Device node interface for the Digital TV frontend286 - Device node interface for the Digital TV demux290 - Device node interface for the Digital TV DVR294 - Device node interface for the Digital TV Conditional Access298 - Device node interface for the Digital TV network control302 - 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 subdevice318 - Device node interface for Software Defined Radio (V4L)[all …]
5 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.
5 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
