Home
last modified time | relevance | path

Searched full:specification (Results 1 – 25 of 1748) sorted by relevance

12345678910>>...70

/linux-6.12.1/drivers/staging/greybus/
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-6.12.1/drivers/char/tpm/
DKconfig14 implements the Trusted Computing Group's specification,
18 userspace enablement piece of the specification, can be
62 tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface"
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
73 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)"
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
92 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (I2C - generic)"
98 (I2C interface) specification and connected to an I2C bus master,
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/riscv/
Dextensions.yaml41 Due to revisions of the ISA specification, some deviations
47 While the isa strings in ISA specification are case
57 version of the unprivileged ISA specification.
72 version of the unprivileged ISA specification.
76 20191213 version of the unprivileged specification.
82 specification.
87 20191213 version of the unprivileged ISA specification.
93 specification.
99 specification.
105 specification.
[all …]
/linux-6.12.1/drivers/acpi/acpica/
Dutstrtoul64.c24 * 2) Runtime "Explicit conversion" as defined in the ACPI specification.
25 * 3) Runtime "Implicit conversion" as defined in the ACPI specification.
50 * interface. According the ACPI specification, there is no ACPI runtime
162 * an "implicit conversion" by the ACPI specification. Used by
171 * Octal strings are not supported, as per the ACPI specification.
177 * Conversion rules as extracted from the ACPI specification:
182 * 1) According to the ACPI specification, a "0x" prefix is not allowed.
201 * interpreter - All runtime implicit conversions, as per ACPI specification
217 * Per the ACPI specification, only hexadecimal is supported for in acpi_ut_implicit_strtoul64()
228 * Ignore overflow as per the ACPI specification. This is implemented by in acpi_ut_implicit_strtoul64()
[all …]
/linux-6.12.1/tools/net/sunrpc/xdrgen/
Dxdrgen4 """Translate an XDR specification into executable code that
28 description="Convert an XDR specification to Linux kernel source code",
67 definitions_parser.add_argument("filename", help="File containing an XDR specification")
92 declarations_parser.add_argument("filename", help="File containing an XDR specification")
95 linter_parser = subcommands.add_parser("lint", help="Check an XDR specification")
96 linter_parser.add_argument("filename", help="File containing an XDR specification")
121 source_parser.add_argument("filename", help="File containing an XDR specification")
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
234 of other specification files
/linux-6.12.1/Documentation/security/tpm/
Dtpm_tis.rst7 TCG PTP Specification defines two interface types: FIFO and CRB. The former is
18 tpm_tis comes from the TPM Interface Specification, which is the hardware
19 interface specification for TPM 1.x chips.
40 in section 3.2 of the TCG PC Client Platform TPM Profile Specification.
45 TCG PC Client Platform TPM Profile (PTP) Specification
46 https://trustedcomputinggroup.org/resource/pc-client-platform-tpm-profile-ptp-specification/
/linux-6.12.1/include/uapi/linux/
Dv4l2-controls.h1382 * sequence parameter set syntax as specified by the H264 specification.
1384 * @profile_idc: see H264 specification.
1385 * @constraint_set_flags: see H264 specification.
1386 * @level_idc: see H264 specification.
1387 * @seq_parameter_set_id: see H264 specification.
1388 * @chroma_format_idc: see H264 specification.
1389 * @bit_depth_luma_minus8: see H264 specification.
1390 * @bit_depth_chroma_minus8: see H264 specification.
1391 * @log2_max_frame_num_minus4: see H264 specification.
1392 * @pic_order_cnt_type: see H264 specification.
[all …]
/linux-6.12.1/Documentation/RCU/Design/Requirements/
DReadersPartitionGP1.svg119 …00000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"><fl…
134 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
166 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
177 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
188 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
199 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
210 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
221 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
232 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
243 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
[all …]
DGPpartitionReaders1.svg91 …00000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"><fl…
106 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
138 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
149 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
160 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
171 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
182 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
193 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
204 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
215 …ll:#000000;fill-opacity:1;stroke:none;font-family:monospace;-inkscape-font-specification:monospace"
[all …]
/linux-6.12.1/Documentation/ABI/testing/
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
/linux-6.12.1/drivers/cxl/
DKconfig25 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/tools/net/sunrpc/xdrgen/generators/
D__init__.py8 from xdr_ast import _XdrAst, Specification, _RpcProgram, _XdrTypeSpecifier
37 def find_xdr_program_name(root: Specification) -> str: argument
50 """Extract the header guard infix from the specification filename"""
79 def emit_declaration(self, filename: str, root: Specification) -> None: argument
83 def emit_definition(self, filename: str, root: Specification) -> None: argument
87 def emit_source(self, filename: str, root: Specification) -> None: argument
Dheader_bottom.py11 from xdr_ast import Specification
22 def emit_declaration(self, filename: str, root: Specification) -> None: argument
27 def emit_definition(self, filename: str, root: Specification) -> None: argument
32 def emit_source(self, filename: str, root: Specification) -> None: argument
Dheader_top.py11 from xdr_ast import Specification
22 def emit_declaration(self, filename: str, root: Specification) -> None: argument
33 def emit_definition(self, filename: str, root: Specification) -> None: argument
44 def emit_source(self, filename: str, root: Specification) -> None: argument
/linux-6.12.1/Documentation/devicetree/bindings/tpm/
Dtcg,tpm-tis-i2c.yaml7 title: I²C-attached Trusted Platform Module conforming to TCG TIS specification
16 TCG PC Client Specific TPM Interface Specification (TIS)
17 …omputinggroup.org/resource/pc-client-work-group-pc-client-specific-tpm-interface-specification-tis/
21 TCG PC Client Platform TPM Profile Specification for TPM 2.0 (PTP)
22 https://trustedcomputinggroup.org/resource/pc-client-platform-tpm-profile-ptp-specification/
/linux-6.12.1/Documentation/nvme/
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-6.12.1/Documentation/dev-tools/
Dktap.rst8 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/drivers/infiniband/ulp/srpt/
Dib_dm_mad.h45 * InfiniBand Architecture Specification.
55 * Architecture Specification.
87 * Architecture Specification.
98 * the InfiniBand Architecture Specification.
133 * Specification. See also section B.7, table B.8 in the T10 SRP r16a document.
/linux-6.12.1/drivers/net/ethernet/sfc/
Dfilter.h53 * enum efx_filter_priority - priority of a hardware filter specification
117 * struct efx_filter_spec - specification for a hardware filter
201 * @spec: Specification to initialise
222 * @spec: Specification to initialise
243 * @spec: Specification to initialise
274 * @spec: Specification to initialise
297 * @spec: Specification to initialise
307 * @spec: Specification to initialise
318 * @spec: Specification to initialise
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dmetafmt-generic.rst61 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 …]
Dmetafmt-pisp-be.rst21 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>`_.
/linux-6.12.1/Documentation/devicetree/bindings/i2c/
Di2c-rk3x.yaml87 (t(r) in I2C specification). If not specified this is assumed to be
88 the maximum the specification allows(1000 ns for Standard-mode,
95 (t(f) in the I2C specification). If not specified this is assumed to
96 be the maximum the specification allows (300 ns) which might cause
103 (t(f) in the I2C specification). If not specified we will use the SCL
/linux-6.12.1/Documentation/gpu/amdgpu/display/
Dmulti-display-hdcp-mpo-less-pipe-ex.svg115 …h:normal;font-size:2.02432632px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
120 …h:normal;font-size:2.02432632px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
146 …h:normal;font-size:3.52777767px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
157 …h:normal;font-size:3.52777767px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
168 …h:normal;font-size:2.02432632px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
179 …h:normal;font-size:2.02432632px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
190 …h:normal;font-size:3.52777767px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
201 …h:normal;font-size:2.02432632px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
206 …h:normal;font-size:2.02432632px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
217 …h:normal;font-size:2.02432632px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo…
/linux-6.12.1/Documentation/crypto/
Dintro.rst1 Kernel Crypto API Interface Specification
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,

12345678910>>...70