| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-pisp-fe.rst | 18 The `Raspberry Pi PiSP technical specification 19 <https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf>`_ 37 The `Raspberry Pi PiSP technical specification 38 <https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf>`_
|
| H A D | metafmt-generic.rst | 62 The packing of the data follows the MIPI CSI-2 specification and the padding of 63 the data is defined in the MIPI CCS specification. 106 The packing of the data follows the MIPI CSI-2 specification and the padding of 107 the data is defined in the MIPI CCS specification. 152 The packing of the data follows the MIPI CSI-2 specification and the padding of 153 the data is defined in the MIPI CCS specification. 195 The packing of the data follows the MIPI CSI-2 specification and the padding of 196 the data is defined in the MIPI CCS specification. 244 The packing of the data follows the MIPI CSI-2 specification and the padding of 245 the data is defined in the MIPI CCS specification. [all …]
|
| H A D | metafmt-pisp-be.rst | 22 The `Raspberry Pi PiSP technical specification 23 <https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf>`_ 54 each field refer to the `Raspberry Pi PiSP technical specification 55 <https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf>`_.
|
| H A D | querycap.rst | 12 the same type have different capabilities and this specification permits 16 check if the kernel device is compatible with this specification, and to
|
| /linux/Documentation/trace/rv/ |
| H A D | linear_temporal_logic.rst | 8 kernel follows a specification. It does so by using tracepoints to monitor the 10 specification. 12 Initially, the specification can only be written in the form of deterministic 15 the specification language. The automaton is complicated, hard to understand, 19 of monitor uses LTL as specification instead of DA. For some cases, writing the 20 specification as LTL is more concise and intuitive. 92 `tools/verification/rvgen`. The specification needs to be provided as a file, 107 From this specification, `rvgen` generates the C implementation of a Buchi
|
| /linux/drivers/net/mctp/ |
| H A 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. 55 defined by DMTF specification DSP0283.
|
| /linux/drivers/char/tpm/ |
| H A D | Kconfig | 14 implements the Trusted Computing Group's specification, 18 userspace enablement piece of the specification, can be 68 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO 69 specification (TPM2.0) say Yes and it will be accessible from 80 TCG TIS 1.3 TPM specification (TPM1.2) or the TCG PTP FIFO 81 specification (TPM2.0) say Yes and it will be accessible from 99 (I2C interface) specification and connected to an I2C bus master, 110 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO 111 specification (TPM2.0) say Yes and it will be accessible from 139 TCG TIS 1.2 TPM specification and Infineon's I2C Protocol Stack [all …]
|
| /linux/tools/net/sunrpc/xdrgen/templates/C/source_top/ |
| H A D | server.j2 | 3 // XDR specification file: {{ filename }} 4 // XDR specification modification time: {{ mtime }}
|
| /linux/Documentation/nvme/ |
| H A 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/tools/net/sunrpc/xdrgen/templates/C/header_top/definition/ |
| H A D | header.j2 | 3 /* XDR specification file: {{ filename }} */ 4 /* XDR specification modification time: {{ mtime }} */
|
| /linux/tools/net/sunrpc/xdrgen/templates/C/header_top/declaration/ |
| H A D | header.j2 | 3 /* XDR specification file: {{ filename }} */ 4 /* XDR specification modification time: {{ mtime }} */
|
| /linux/Documentation/virt/coco/ |
| H A 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.
|
| H A 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/Documentation/ABI/testing/ |
| H A D | sysfs-bus-pci-devices-pvpanic | 12 from pvpanic device specification: 26 Also refer to pvpanic device specification.
|
| H A D | sysfs-bus-platform-devices-ampere-smpro | 17 …| 04 | Error status | 4 | See ARM RAS specification for details … 19 …| 08 | Error Address | 8 | See ARM RAS specification for details … 21 …| 16 | Error Misc 0 | 8 | See ARM RAS specification for details … 23 …| 24 | Error Misc 1 | 8 | See ARM RAS specification for details … 25 …| 32 | Error Misc 2 | 8 | See ARM RAS specification for details … 27 …| 40 | Error Misc 3 | 8 | See ARM RAS specification for details …
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | lpc32xx-mlc.txt | 6 - interrupts: The NAND interrupt specification 7 - gpios: GPIO specification for NAND write protect
|
| /linux/drivers/cxl/ |
| H A D | Kconfig | 27 The CXL specification defines a "CXL memory device" sub-class in the 36 Type 3 CXL Device in the CXL 2.0 specification for more details. 47 number for each specification defined opcode. At any given point in 48 time the number of opcodes that the specification defines and a device 50 numbers. The mismatch is either by omission, specification is too new, 71 specification, and CXL Fixed Memory Window Structures (CEDT.CFMWS) 103 specification for a detailed description of HDM.
|
| /linux/Documentation/devicetree/bindings/leds/ |
| H A 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/Documentation/driver-api/nfc/ |
| H A D | nfc-pn544.rst | 23 HCI specification. The firmware is updated using a specific protocol, 33 For the ETSI HCI specification see
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A 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/Documentation/crypto/ |
| H A 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/drivers/usb/class/ |
| H A 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/drivers/usb/typec/ucsi/ |
| H A 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:
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-intro.rst | 12 Channel) of the HDMI 1.4a (:ref:`hdmi`) specification and the 14 HDMI 2.0 (:ref:`hdmi2`) specification.
|
| /linux/drivers/usb/common/ |
| H A 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
|