| /linux/drivers/staging/greybus/ |
| H A 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/drivers/char/tpm/ |
| H A D | Kconfig | 14 implements the Trusted Computing Group's specification, 18 userspace enablement piece of the specification, can be 63 tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface" 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 74 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)" 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 93 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (I2C - generic)" 99 (I2C interface) specification and connected to an I2C bus master, [all …]
|
| /linux/Documentation/devicetree/bindings/riscv/ |
| H A D | extensions.yaml | 35 Due to revisions of the ISA specification, some deviations 41 While the isa strings in ISA specification are case 51 version of the unprivileged ISA specification. 66 version of the unprivileged ISA specification. 70 20191213 version of the unprivileged specification. 76 specification. 81 20191213 version of the unprivileged ISA specification. 87 specification. 93 specification. 99 specification. [all …]
|
| /linux/drivers/acpi/acpica/ |
| H A D | utstrtoul64.c | 24 * 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/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 132 M. (eds) Protocol Specification, Testing and Verification XV. PSTV 1995. IFIP
|
| H A D | monitor_synthesis.rst | 5 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/security/tpm/ |
| H A D | tpm_ffa_crb.rst | 8 defined in the TCG PC Client Platform TPM Profile (PTP) Specification [1]_. 18 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 58 .. [1] **TCG PC Client Platform TPM Profile (PTP) Specification** 59 https://trustedcomputinggroup.org/resource/pc-client-platform-tpm-profile-ptp-specification/ 64 .. [4] **TCG ACPI Specification** 65 https://trustedcomputinggroup.org/resource/tcg-acpi-specification/
|
| H A D | tpm_tis.rst | 7 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/include/sound/ |
| H A D | sdca_function.h | 3 * The MIPI SDCA specification is available for public downloads at 65 * SDCA Function Types from SDCA specification v1.0a Section 5.1.2 164 * Control Selectors for Input Terminal from SDCA specification v1.0 184 * Control Selectors for Output Terminal from SDCA specification v1.0 224 * Control Selectors for Mixer Unit from SDCA specification v1.0 235 * Control Selectors for Selector Unit from SDCA specification v1.0 246 * Control Selectors for Feature Unit from SDCA specification v1.0 272 * Control Selectors for Extension Unit from SDCA specification v1.0 312 * Control Selectors for Clock Source from SDCA specification v1.0 332 * Control Selectors for Clock Selector from SDCA specification v1.0 [all …]
|
| /linux/include/uapi/linux/ |
| H A D | v4l2-controls.h | 1403 * sequence parameter set syntax as specified by the H264 specification. 1405 * @profile_idc: see H264 specification. 1406 * @constraint_set_flags: see H264 specification. 1407 * @level_idc: see H264 specification. 1408 * @seq_parameter_set_id: see H264 specification. 1409 * @chroma_format_idc: see H264 specification. 1410 * @bit_depth_luma_minus8: see H264 specification. 1411 * @bit_depth_chroma_minus8: see H264 specification. 1412 * @log2_max_frame_num_minus4: see H264 specification. 1413 * @pic_order_cnt_type: see H264 specification [all...] |
| /linux/tools/net/sunrpc/xdrgen/ |
| H A D | xdrgen | 4 """Translate an XDR specification into executable code that 33 description="Convert an XDR specification to Linux kernel source code", 72 definitions_parser.add_argument("filename", help="File containing an XDR specification") 97 declarations_parser.add_argument("filename", help="File containing an XDR specification") 100 linter_parser = subcommands.add_parser("lint", help="Check an XDR specification") 101 linter_parser.add_argument("filename", help="File containing an XDR specification") 132 source_parser.add_argument("filename", help="File containing an XDR specification")
|
| H A 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 251 of other specification files
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | ReadersPartitionGP1.svg | 119 …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 …]
|
| H A D | GPpartitionReaders1.svg | 91 …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/Documentation/ABI/testing/ |
| H A 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
|
| /linux/tools/net/sunrpc/xdrgen/generators/ |
| H A D | __init__.py | 8 from xdr_ast import _XdrAst, Specification, _RpcProgram, _XdrTypeSpecifier 41 def find_xdr_program_name(root: Specification) -> str: argument 54 """Extract the header guard infix from the specification filename""" 83 def emit_declaration(self, filename: str, root: Specification) -> None: argument 87 def emit_definition(self, filename: str, root: Specification) -> None: argument 91 def emit_source(self, filename: str, root: Specification) -> None: argument
|
| H A D | header_bottom.py | 11 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
|
| H A D | header_top.py | 11 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/Documentation/gpu/amdgpu/ |
| H A D | pipe_and_queue_abstraction.svg | 315 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 326 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 337 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 348 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 359 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 535 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 546 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 557 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 568 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… 725 …etch:normal;font-size:7.05556px;font-family:sans-serif;-inkscape-font-specification:'sans-serif Bo… [all …]
|
| /linux/Documentation/devicetree/bindings/tpm/ |
| H A D | tcg,tpm-tis-i2c.yaml | 7 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/Documentation/dev-tools/ |
| H A D | ktap.rst | 8 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/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/Documentation/userspace-api/media/v4l/ |
| 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 …]
|
| /linux/drivers/net/ethernet/sfc/ |
| H A D | filter.h | 53 * 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/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.
|