Searched refs:specification (Results 1 – 25 of 391) sorted by relevance
12345678910>>...16
| /Linux-v6.1/drivers/staging/greybus/ |
| D | Kconfig | 9 Greybus Audio Class specification.
30 Greybus Bootrom Class specification.
40 Greybus Camera Class specification.
50 Greybus Firmware Download Class specification.
60 Greybus HID Class specification.
70 Greybus LED Class specification.
79 Greybus Debug Log Class specification.
88 Greybus Debug Log Class specification.
98 Greybus Powersupply Class specification.
107 Greybus Raw Class specification.
[all …]
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-bus-i3c | 22 the I3C specification for a detailed description of what each
52 length, etc. See the I3C specification for more details.
62 specification for more details.
74 See the I3C specification for more details.
85 See the I3C specification for more details about these HDR
112 length, etc. See the I3C specification for more details.
120 specification for more details.
130 See the I3C specification for more details.
140 See the I3C specification for more details about these HDR
|
| D | sysfs-bus-umc | 7 specification describes a PCI-based device with
27 The specification version this capability's hardware
|
| D | sysfs-bus-pci-devices-pvpanic | 12 from pvpanic device specification:
26 Also refer to pvpanic device specification.
|
| /Linux-v6.1/drivers/cxl/ |
| D | Kconfig | 21 The CXL specification defines a "CXL memory device" sub-class in the
30 Type 3 CXL Device in the CXL 2.0 specification for more details.
41 number for each specification defined opcode. At any given point in
42 time the number of opcodes that the specification defines and a device
44 numbers. The mismatch is either by omission, specification is too new,
61 specification, and CXL Fixed Memory Window Structures (CEDT.CFMWS)
94 specification for a detailed description of HDM.
|
| /Linux-v6.1/drivers/char/tpm/ |
| D | Kconfig | 14 implements the Trusted Computing Group's specification,
18 userspace enablement piece of the specification, can be
53 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO
54 specification (TPM2.0) say Yes and it will be accessible from
65 TCG TIS 1.3 TPM specification (TPM1.2) or the TCG PTP FIFO
66 specification (TPM2.0) say Yes and it will be accessible from
84 (I2C interface) specification and connected to an I2C bus master,
95 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO
96 specification (TPM2.0) say Yes and it will be accessible from
124 TCG TIS 1.2 TPM specification and Infineon's I2C Protocol Stack
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/input/touchscreen/ |
| D | ektf2127.txt | 6 - interrupts : interrupt specification for the ektf2127 interrupt
7 - power-gpios : GPIO specification for the pin connected to the
|
| /Linux-v6.1/Documentation/devicetree/bindings/display/bridge/ |
| D | ps8622.txt | 6 - sleep-gpios: OF device-tree gpio specification for PD_ pin.
7 - reset-gpios: OF device-tree gpio specification for RST_ pin.
|
| /Linux-v6.1/Documentation/dev-tools/ |
| D | ktap.rst | 8 by a number of projects. It's website and specification are found at this `link
11 which don't align with the original TAP specification. Thus, a "Kernel TAP"
13 This specification describes the generally accepted format of KTAP as it is
30 there is a stagnant draft specification for TAP14, KTAP diverges from this in
245 The TAP14 specification does permit nested tests, but instead of using another
304 - The TAP specification:
305 https://testanything.org/tap-version-13-specification.html
306 - The (stagnant) TAP version 14 specification:
307 https://github.com/TestAnything/Specification/blob/tap-14-specification/specification.md
|
| /Linux-v6.1/drivers/usb/typec/ucsi/ |
| D | Kconfig | 9 specification for an interface that allows the operating system to
16 UCSI specification does not define the interface method, so depending
21 The UCSI specification can be downloaded from:
|
| /Linux-v6.1/Documentation/virt/coco/ |
| D | sev-guest.rst | 77 contain the format described in the SEV-SNP specification. See the SEV-SNP
78 specification for further details.
92 SEV-SNP firmware to derive the key. See SEV-SNP specification for further details
96 the SEV-SNP specification for further details.
119 See GHCB specification for further detail on how to parse the certificate blob.
153 SEV-SNP and GHCB specification: developer.amd.com/sev
|
| /Linux-v6.1/Documentation/driver-api/soundwire/ |
| D | summary.rst | 31 direction is enabled by the specification). Bandwidth restrictions to
58 The MIPI SoundWire specification uses the term 'device' to refer to a Master
133 MIPI specification, so Bus calls the "sdw_master_port_ops" callback
141 The MIPI specification requires each Slave interface to expose a unique
154 board-file, ACPI or DT. The MIPI Software specification defines additional
198 SoundWire MIPI specification 1.1 is available at:
201 SoundWire MIPI DisCo (Discovery and Configuration) specification is
|
| /Linux-v6.1/Documentation/devicetree/bindings/mtd/ |
| D | lpc32xx-mlc.txt | 6 - interrupts: The NAND interrupt specification
7 - gpios: GPIO specification for NAND write protect
|
| /Linux-v6.1/Documentation/devicetree/bindings/leds/ |
| D | leds-ns2.txt | 9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.
|
| /Linux-v6.1/Documentation/driver-api/nfc/ |
| D | nfc-pn544.rst | 23 HCI specification. The firmware is updated using a specific protocol,
33 For the ETSI HCI specification see
|
| /Linux-v6.1/drivers/net/mctp/ |
| D | Kconfig | 12 serial line-discipline, as defined by DMTF specification "DSP0253 -
33 from DMTF specification DSP0237. A MCTP protocol network device is
|
| /Linux-v6.1/Documentation/userspace-api/media/dvb/ |
| D | fe-get-info.rst | 36 used to identify kernel devices compatible with this specification and to
39 When the driver is not compatible with this specification the ioctl
|
| /Linux-v6.1/Documentation/userspace-api/media/v4l/ |
| D | querycap.rst | 11 the same type have different capabilities and this specification permits
15 check if the kernel device is compatible with this specification, and to
|
| /Linux-v6.1/Documentation/crypto/ |
| D | intro.rst | 15 specification, hints to developers of ciphers are provided. Pointers to
30 This specification is intended for consumers of the kernel crypto API as
31 well as for developers implementing ciphers. This API specification,
|
| /Linux-v6.1/Documentation/i2c/ |
| D | summary.rst | 14 The latest official I2C specification is the `"I2C-bus specification and user
17 access the PDF. An older version of the specification (revision 6) is archived
|
| /Linux-v6.1/drivers/usb/class/ |
| D | Kconfig | 35 of cell phones compliant to the CDC WMC specification. You can use
45 the USB.org specification for USB Test and Measurement devices
|
| /Linux-v6.1/Documentation/userspace-api/media/cec/ |
| D | cec-intro.rst | 12 Channel) of the HDMI 1.4a (:ref:`hdmi`) specification and the
14 HDMI 2.0 (:ref:`hdmi2`) specification.
|
| /Linux-v6.1/drivers/usb/common/ |
| D | Kconfig | 21 UTMI+ Low Pin Interface (ULPI) is specification for a commonly used
22 USB 2.0 PHY interface. The ULPI specification defines a standard set
|
| /Linux-v6.1/Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 7 see 'Variable Services' in the UEFI specification
8 (section 7.2 in specification version 2.3 Errata D).
|
| /Linux-v6.1/Documentation/cdrom/ |
| D | packet-writing.rst | 48 According to the DVD+RW specification, a drive supporting DVD+RW discs
58 However, some drives don't follow the specification and expect the
60 follow the specification, but suffer bad performance problems if the
|
12345678910>>...16
