Home
last modified time | relevance | path

Searched refs:specification (Results 1 – 25 of 429) sorted by relevance

12345678910>>...18

/linux/drivers/staging/greybus/
H A DKconfig9 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/Documentation/userspace-api/media/v4l/
H A Dmetafmt-pisp-fe.rst18 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 Dmetafmt-generic.rst62 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 Dmetafmt-pisp-be.rst22 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>`_.
/linux/Documentation/trace/rv/
H A Dlinear_temporal_logic.rst8 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
H A Dmonitor_synthesis.rst5 is the *specification* or *modeling* of the desired (or undesired) behavior
11 the events from the *system* to the events of the *specification*.
26 | (instrumentation) | | (verification) | | (specification) |
42 The synthesis of a specification into the Linux *RV monitor* abstraction is
52 The rvgen utility converts a specification into the C presentation and creating
76 verify the specification)
166 verifies the LTL specification. While `rv/ltl_monitor.h` includes the common
177 which is the list of atomic propositions present in the LTL specification
189 `value`. The Buchi automaton checks whether the LTL specification is still
203 specification, it is not important when `RT` changes, as long as it has the
[all …]
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-i3c22 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
H A Dsysfs-bus-pci-devices-pvpanic12 from pvpanic device specification:
26 Also refer to pvpanic device specification.
/linux/drivers/net/mctp/
H A DKconfig12 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 DKconfig14 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/Documentation/nvme/
H A Dfeature-and-quirk-policy.rst20 - 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/source_top/
H A Dserver.j23 // XDR specification file: {{ filename }}
4 // XDR specification modification time: {{ mtime }}
H A Dclient.j23 // XDR specification file: {{ filename }}
4 // XDR specification modification time: {{ mtime }}
/linux/tools/net/sunrpc/xdrgen/templates/C/header_top/definition/
H A Dheader.j23 /* XDR specification file: {{ filename }} */
4 /* XDR specification modification time: {{ mtime }} */
/linux/tools/net/sunrpc/xdrgen/templates/C/header_top/declaration/
H A Dheader.j23 /* XDR specification file: {{ filename }} */
4 /* XDR specification modification time: {{ mtime }} */
/linux/Documentation/ABI/removed/
H A Dsysfs-firmware-efi-vars6 see 'Variable Services' in the UEFI specification
7 (section 7.2 in specification version 2.3 Errata D).
/linux/tools/net/sunrpc/xdrgen/
H A DREADME42 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
251 of other specification files
/linux/Documentation/dev-tools/
H A Dktap.rst8 by a number of projects. Its 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
31 there is a stagnant draft specification for TAP14, KTAP diverges from this in
247 The TAP14 specification does permit nested tests, but instead of using another
307 - The TAP specification:
308 https://testanything.org/tap-version-13-specification.html
309 - The (stagnant) TAP version 14 specification:
310 https://github.com/TestAnything/Specification/blob/tap-14-specification/specification.md
/linux/Documentation/virt/coco/
H A Dtdx-guest.rst38 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 Dsev-guest.rst100 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/security/tpm/
H A Dtpm_ffa_crb.rst18 The Firmware Framework for Arm A-profile (FF-A) [2]_ is a specification
35 specification defines FF-A messages that can be used by a client to signal
59 https://trustedcomputinggroup.org/resource/pc-client-platform-tpm-profile-ptp-specification/
65 https://trustedcomputinggroup.org/resource/tcg-acpi-specification/
/linux/Documentation/driver-api/soundwire/
H A Dsummary.rst31 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
190 SoundWire MIPI specification 1.1 is available at:
193 SoundWire MIPI DisCo (Discovery and Configuration) specification is
/linux/drivers/cxl/
H A DKconfig27 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/mtd/
H A Dlpc32xx-mlc.txt6 - interrupts: The NAND interrupt specification
7 - gpios: GPIO specification for NAND write protect
/linux/Documentation/devicetree/bindings/leds/
H A Dleds-ns2.txt9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.

12345678910>>...18