Searched refs:specification (Results 1 – 25 of 413) sorted by relevance
12345678910>>...17
/linux-6.12.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-6.12.1/Documentation/userspace-api/media/v4l/ |
D | metafmt-generic.rst | 61 The packing of the data follows the MIPI CSI-2 specification and the padding of 62 the data is defined in the MIPI CCS specification. 105 The packing of the data follows the MIPI CSI-2 specification and the padding of 106 the data is defined in the MIPI CCS specification. 151 The packing of the data follows the MIPI CSI-2 specification and the padding of 152 the data is defined in the MIPI CCS specification. 194 The packing of the data follows the MIPI CSI-2 specification and the padding of 195 the data is defined in the MIPI CCS specification. 243 The packing of the data follows the MIPI CSI-2 specification and the padding of 244 the data is defined in the MIPI CCS specification. [all …]
|
D | metafmt-pisp-be.rst | 21 The `Raspberry Pi PiSP technical specification 22 <https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf>`_ 53 each field refer to the `Raspberry Pi PiSP technical specification 54 <https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf>`_.
|
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-6.12.1/drivers/char/tpm/ |
D | Kconfig | 14 implements the Trusted Computing Group's specification, 18 userspace enablement piece of the specification, can be 67 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO 68 specification (TPM2.0) say Yes and it will be accessible from 79 TCG TIS 1.3 TPM specification (TPM1.2) or the TCG PTP FIFO 80 specification (TPM2.0) say Yes and it will be accessible from 98 (I2C interface) specification and connected to an I2C bus master, 109 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO 110 specification (TPM2.0) say Yes and it will be accessible from 138 TCG TIS 1.2 TPM specification and Infineon's I2C Protocol Stack [all …]
|
/linux-6.12.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 127 length, etc. See the I3C specification for more details. 135 specification for more details. 145 See the I3C specification for more details. 155 See the I3C specification for more details about these HDR
|
D | sysfs-bus-pci-devices-pvpanic | 12 from pvpanic device specification: 26 Also refer to pvpanic device specification.
|
/linux-6.12.1/tools/net/sunrpc/xdrgen/templates/C/source_top/ |
D | server.j2 | 3 // XDR specification file: {{ filename }} 4 // XDR specification modification time: {{ mtime }}
|
D | client.j2 | 3 // XDR specification file: {{ filename }} 4 // XDR specification modification time: {{ mtime }}
|
/linux-6.12.1/tools/net/sunrpc/xdrgen/templates/C/header_top/definition/ |
D | header.j2 | 3 /* XDR specification file: {{ filename }} */ 4 /* XDR specification modification time: {{ mtime }} */
|
/linux-6.12.1/Documentation/nvme/ |
D | feature-and-quirk-policy.rst | 20 - the NVMe Base specification 23 - the NVMe Management Interface specification 33 does not aim to implement every feature in the specification. Every additional 42 specification, or in a ratified Technical Proposal (TP) that is 54 maintainers and get feedback on specification changes that are intended
|
/linux-6.12.1/tools/net/sunrpc/xdrgen/templates/C/header_top/declaration/ |
D | header.j2 | 3 /* XDR specification file: {{ filename }} */ 4 /* XDR specification modification time: {{ mtime }} */
|
/linux-6.12.1/drivers/cxl/ |
D | Kconfig | 25 The CXL specification defines a "CXL memory device" sub-class in the 34 Type 3 CXL Device in the CXL 2.0 specification for more details. 45 number for each specification defined opcode. At any given point in 46 time the number of opcodes that the specification defines and a device 48 numbers. The mismatch is either by omission, specification is too new, 68 specification, and CXL Fixed Memory Window Structures (CEDT.CFMWS) 101 specification for a detailed description of HDM.
|
/linux-6.12.1/Documentation/ABI/removed/ |
D | sysfs-firmware-efi-vars | 6 see 'Variable Services' in the UEFI specification 7 (section 7.2 in specification version 2.3 Errata D).
|
/linux-6.12.1/tools/net/sunrpc/xdrgen/ |
D | README | 42 the protocol specification. 69 specification can be derived by feeding a .txt copy of the RFC to 96 generated code to specific parts of the XDR specification. 102 an XDR specification: 113 RFC 4506 Section 6 contains a BNF grammar of the XDR specification 119 in xdr.ebnf. Lark parses the target XDR specification using this 130 in the specification to ensure the generated code compiles. This 234 of other specification files
|
/linux-6.12.1/drivers/net/mctp/ |
D | Kconfig | 12 serial line-discipline, as defined by DMTF specification "DSP0253 - 38 from DMTF specification DSP0237. A MCTP protocol network device is 46 from DMTF specification DSP0233.
|
/linux-6.12.1/Documentation/virt/coco/ |
D | tdx-guest.rst | 38 the TDX Module v1.0 specification, section titled "TDG.MR.REPORT", it is not 52 The driver is based on TDX module specification v1.0 and TDX GHCI specification v1.0.
|
D | sev-guest.rst | 100 contain the format described in the SEV-SNP specification. See the SEV-SNP 101 specification for further details. 115 SEV-SNP firmware to derive the key. See SEV-SNP specification for further details 119 the SEV-SNP specification for further details. 142 See GHCB specification for further detail on how to parse the certificate blob. 153 specification for further details. 241 SEV-SNP and GHCB specification: developer.amd.com/sev
|
/linux-6.12.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-6.12.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-6.12.1/Documentation/devicetree/bindings/mtd/ |
D | lpc32xx-mlc.txt | 6 - interrupts: The NAND interrupt specification 7 - gpios: GPIO specification for NAND write protect
|
/linux-6.12.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-6.12.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-6.12.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-6.12.1/drivers/usb/typec/ucsi/ |
D | Kconfig | 10 specification for an interface that allows the operating system to 17 UCSI specification does not define the interface method, so depending 22 The UCSI specification can be downloaded from:
|
12345678910>>...17