Searched full:identification (Results 1 – 25 of 89) sorted by relevance
1234
| /Documentation/ABI/testing/ |
| D | sysfs-driver-input-exc3000 | 13 Description: Reports the model identification provided by the touchscreen, for example "Orion_13…
22 Description: Reports the type identification provided by the touchscreen, for example "PCAP82H80 Se…
|
| D | configfs-acpi | 40 - ASCII OEM identification
43 - ASCII OEM table identification
|
| D | sysfs-devices-soc | 30 this will contain the JEDEC JEP106 manufacturer’s identification
34 This manufacturer’s identification code is defined by one
38 the maximum number of identification codes, a continuation
|
| D | sysfs-platform-dell-wmi-ddv | 6 Reports the Dell ePPID (electronic Piece Part Identification)
|
| D | sysfs-class-net-janz-ican3 | 18 Read-only: 32 byte string identification of the ICAN3 module
|
| D | sysfs-ibft | 31 identification of the creator of the table which is useful in
|
| D | sysfs-bus-typec | 35 assigned, and can not be therefore used for identification. When
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | 30 Sets the RDS Programme Identification field for transmission.
39 listeners in programme service identification and selection. In
64 Sets the Mono/Stereo bit of the Decoder Identification code. If set,
70 bit of the Decoder Identification code. If set, then the audio was
74 Sets the Compressed bit of the Decoder Identification code. If set,
78 Sets the Dynamic PTY bit of the Decoder Identification code. If set,
|
| D | vidioc-g-dv-timings.rst | 165 - The Video Identification Code according to the CEA-861 standard.
169 - The Video Identification Code according to the HDMI standard.
307 Identification Code as per the CEA-861 standard.
310 Identification Code as per the HDMI standard (HDMI Vendor Specific
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | imx-iim.yaml | 7 title: Freescale i.MX IC Identification Module (IIM)
15 This binding represents the IC Identification Module (IIM) found on
|
| D | brcm,nvram.yaml | 34 description: Board identification name
|
| /Documentation/driver-api/media/drivers/ |
| D | tuners.rst | 21 - Samsung Tuner identification: (e.g. TCPM9091PD27)
51 Philips Tuner identification: (e.g. FM1216MF)
77 Temic Tuner identification: (.e.g 4006FH5)
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,versatile-sysreg.yaml | 14 platform functions like board detection and identification, software
|
| D | vexpress-sysreg.yaml | 14 platform functions like board detection and identification, software
|
| /Documentation/devicetree/bindings/soc/xilinx/ |
| D | xlnx,vcu.txt | 17 - clock-names: The identification string, "aclk", is always required for
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | nokia,n900-battery.yaml | 23 - description: ADC channel for battery size identification
|
| /Documentation/devicetree/bindings/leds/ |
| D | rohm,bd71828-leds.yaml | 32 description: LED identification string
|
| /Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 496 The Device Tree protocol uses device identification based on the "compatible"
499 regarded as a device identification namespace analogous to the ACPI/PNP device
502 identification string in the Device Tree (DT) namespace, especially if that ID
506 In ACPI, the device identification object called _CID (Compatible ID) is used to
510 Moreover, the specification mandates that either a _HID or an _ADR identification
516 existing DT-compatible device identification in ACPI and to satisfy the above
521 device identification algorithm. If the "compatible" property is not present
526 driver) and the identification strings from the "compatible" property value will
531 the identification strings listed by the "compatible" property value (if present
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,trx.txt | 9 identification fields, CRC32 checksum and the locations of embedded partitions.
|
| /Documentation/hwmon/ |
| D | ds1621.rst | 95 Since there is no version or vendor identification register, there is
96 no unique identification for these devices. Therefore, explicit device
97 instantiation is required for correct device identification and functionality
|
| D | sht21.rst | 56 - Electronic Identification Code
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | olimex,lcd-olinuxino.yaml | 21 - AT24C16C EEPROM holding panel identification and timing requirements
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,glink-edge.yaml | 43 Name of the edge, used for debugging and identification purposes. The
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-setup-link.rst | 35 :c:type:`media_link_desc` with link identification
|
| /Documentation/filesystems/ext4/ |
| D | attributes.rst | 43 - Magic number for identification, 0xEA020000. This value is set by the
60 - Magic number for identification, 0xEA020000.
|
1234