Searched refs:Device (Results 1 – 25 of 1513) sorted by relevance
12345678910>>...61
5 Device () scope per mux channel.16 Device (SMB1)19 Device (MUX0)28 Device (CH00)32 Device (CLIA)43 Device (CH01)47 Device (CLIB)
1 _DSD Device Properties Usage Rules7 The _DSD (Device Specific Data) configuration object, introduced in ACPI 5.1,20 generic Device Properties UUID in the _DSD return package as specified in the21 Device Properties UUID definition document [1].24 that can be returned by _DSD in the Device Properties UUID sub-package for a29 can be returned in the Device Properties UUID sub-package for the device in45 Valid property sets must follow the guidance given by the Device Properties UUID53 associated with the Device Properties UUID.75 Property Sets and Device Tree Bindings78 It often is useful to make _DSD return property sets that follow Device Tree
2 # SCSI Device Handler configuration6 bool "SCSI Device Handlers"10 SCSI Device Handlers provide device specific support for15 tristate "LSI RDAC Device Handler"21 tristate "HP/COMPAQ MSA Device Handler"29 tristate "EMC CLARiiON Device Handler"35 tristate "SPC-3 ALUA Device Handler"38 SCSI Device handler for generic SPC-3 Asymmetric Logical Unit
27 *) Creating EPF Device34 ... <EPF Device 11>/35 ... <EPF Device 21>/37 ... <EPF Device 12>/38 ... <EPF Device 22>/45 (These entries are created by the framework when any new <EPF Device> is49 ... <EPF Device 11>/61 *) EPC Device76 The <EPC Device> directory will have a list of symbolic links to77 <EPF Device>. These symbolic links should be created by the user to[all …]
8 1. Endpoint Device32 1.3 Creating pci-epf-test Device61 1.4 Configuring pci-epf-test Device72 1.5 Binding pci-epf-test Device to EP Controller90 2. RootComplex Device96 00:00.0 PCI bridge: Texas Instruments Device 8888 (rev 01)97 01:00.0 Unassigned class [ff00]: Texas Instruments Device b50099 2.2 Using Endpoint Test function Device
1 Device drivers infrastructure4 The Basic Device Driver-Model Structures10 Device Drivers Base49 Device Drivers DMA Management58 Device drivers PnP support
2 Device connections15 Device connections are generic descriptions of any type of connection between18 Device connections alone do not create a dependency between the two devices.27 Device connections should exist before device ``->probe`` callback is called for
1 * NXP LPC32xx SoC USB Device Controller (UDC)8 * USB Device Low Priority Interrupt9 * USB Device High Priority Interrupt10 * USB Device DMA Interrupt
7 tristate "Imagination I2S Input Device Driver"15 tristate "Imagination I2S Output Device Driver"23 tristate "Imagination Parallel Output Device Driver"31 tristate "Imagination SPDIF Input Device Driver"39 tristate "Imagination SPDIF Output Device Driver"
29 bool "SPEAr1310 Machine support with Device Tree"36 bool "SPEAr1340 Machine support with Device Tree"56 bool "SPEAr300 Machine support with Device Tree"62 bool "SPEAr310 Machine support with Device Tree"68 bool "SPEAr320 Machine support with Device Tree"
22 STiH418 family SoCs using the Device Tree for discovery. More34 and other digital audio/video applications using Flattned Device43 and other digital audio/video applications using Flattened Device53 and other digital audio/video applications using Flattened Device
2 Device Classes10 <Insert List of Device Classes Here>14 that devices of that class adhere to. Device drivers are the18 Device classes are agnostic with respect to what bus a device resides43 Device classes are registered and unregistered with the core using: 72 Device Drivers74 Device drivers are added to device classes when they are registered143 particular class type. Device interfaces describe these mechanisms.
145 Device Tree for AT91 SoCs and boards147 All AT91 SoCs are converted to Device Tree. Since Linux 3.19, these products151 Device Tree files and Device Tree bindings that apply to AT91 SoCs and boards are153 any time. So, be sure to use a Device Tree Binary and a Kernel Image generated from160 - SoCs Device Tree Source Include files are named after the official name of162 - Device Tree Source Include files (.dtsi) are used to collect common nodes that can be167 - board Device Tree Source files (.dts) are prefixed by the string "at91-" so
41 - Returns the current state of Audio Device.47 This ioctl call asks the Audio Device to return the current state of the48 Audio Device.
75 the Linux manual page for fcntl. Only one user can open the Audio Device77 fail, and an error code will be returned. If the Audio Device is opened96 - Device driver not loaded/available.102 - Device or resource busy.
76 user can open the Video Device in O_RDWR mode. All other attempts to78 returned. If the Video Device is opened in O_RDONLY mode, the only97 - Device driver not loaded/available.109 - Device or resource busy.
32 Device Name: KS0108 LCD Controller33 Device Code: ks010835 Device Webpage: -
32 HWM Base address can be obtained from Logical Device 8, registers 0x60 (MSB)99 a. Write the index of the Logical Device Number Configuration Register114 The following is an example of how to read the SIO Device ID located at 0x20132 The registers of interest for identifying the SIO on the dc7100 are Device ID133 (0x20) and Device Rev (0x21).135 The Device ID will read 0x6F (0x81 for SCH5307-NS, and 0x85 for SCH5317)136 The Device Rev currently reads 0x01140 Logical Device 8.153 OUT DX,AL;Point to Logical Device 8
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 the93 bool "Device Tree overlays"
275 - Device node interface for the Digital TV frontend279 - Device node interface for the Digital TV demux283 - Device node interface for the Digital TV DVR287 - Device node interface for the Digital TV Conditional Access291 - Device node interface for the Digital TV network control295 - Device node interface for video (V4L)299 - Device node interface for VBI (V4L)303 - Device node interface for radio (V4L)307 - Device node interface for a V4L subdevice311 - Device node interface for Software Defined Radio (V4L)[all …]
4 comment "USB Device Class drivers"11 Communication Device Class Abstract Control Model interface.31 tristate "USB Wireless Device Management support"33 This driver supports the WMC Device Management functionality
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.
6 Contact: Device Tree mailing list <devicetree@vger.kernel.org>14 Contact: Device Tree mailing list <devicetree@vger.kernel.org>21 Contact: Device Tree mailing list <devicetree@vger.kernel.org>
2 tristate "Goldfish AVD Audio Device"5 Emulated audio channel for the Goldfish Android Virtual Device
3 * Device Tree file for DB-XC3-24G4XG board9 * Note: this Device Tree assumes that the bootloader has remapped the16 * solution) or the below Device Tree should be adjusted.39 /* Device Bus parameters are required */
