Searched full:specification (Results 1 – 25 of 2975) sorted by relevance
12345678910>>...119
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/drivers/char/tpm/ |
| D | Kconfig | 14 implements the Trusted Computing Group's specification,
18 userspace enablement piece of the specification, can be
48 tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface"
53 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO
54 specification (TPM2.0) say Yes and it will be accessible from
59 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)"
65 TCG TIS 1.3 TPM specification (TPM1.2) or the TCG PTP FIFO
66 specification (TPM2.0) say Yes and it will be accessible from
78 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (I2C - generic)"
84 (I2C interface) specification and connected to an I2C bus master,
[all …]
|
| /kernel/linux/linux-5.10/drivers/char/tpm/ |
| D | Kconfig | 14 implements the Trusted Computing Group's specification,
18 userspace enablement piece of the specification, can be
48 tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface"
53 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO
54 specification (TPM2.0) say Yes and it will be accessible from
59 tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)"
65 TCG TIS 1.3 TPM specification (TPM1.2) or the TCG PTP FIFO
66 specification (TPM2.0) say Yes and it will be accessible from
78 tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface (MMIO - SynQuacer)"
83 TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 41 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 …]
|
| /kernel/linux/linux-6.6/drivers/acpi/acpica/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/acpi/acpica/ |
| 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 …]
|
| /kernel/linux/linux-5.10/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
112 length, etc. See the I3C specification for more details.
120 specification for more details.
130 See the I3C specification for more details.
140 See the I3C specification for more details about these HDR
|
| /kernel/linux/linux-6.6/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
112 length, etc. See the I3C specification for more details.
120 specification for more details.
130 See the I3C specification for more details.
140 See the I3C specification for more details about these HDR
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Requirements/ |
| D | ReadersPartitionGP1.svg | 119 …:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"><flowR…
134 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
166 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
177 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
188 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
199 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
210 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
221 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
232 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
243 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
[all …]
|
| D | GPpartitionReaders1.svg | 91 …:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"><flowR…
106 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
138 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
149 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
160 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
171 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
182 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
193 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
204 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
215 …dle;fill:#000000;fill-opacity:1;stroke:none;font-family:Symbol;-inkscape-font-specification:Symbol"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/RCU/Design/Requirements/ |
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | v4l2-controls.h | 1368 * sequence parameter set syntax as specified by the H264 specification.
1370 * @profile_idc: see H264 specification.
1371 * @constraint_set_flags: see H264 specification.
1372 * @level_idc: see H264 specification.
1373 * @seq_parameter_set_id: see H264 specification.
1374 * @chroma_format_idc: see H264 specification.
1375 * @bit_depth_luma_minus8: see H264 specification.
1376 * @bit_depth_chroma_minus8: see H264 specification.
1377 * @log2_max_frame_num_minus4: see H264 specification.
1378 * @pic_order_cnt_type: see H264 specification.
[all …]
|
| /kernel/linux/linux-6.6/drivers/cxl/ |
| D | Kconfig | 23 The CXL specification defines a "CXL memory device" sub-class in the
32 Type 3 CXL Device in the CXL 2.0 specification for more details.
43 number for each specification defined opcode. At any given point in
44 time the number of opcodes that the specification defines and a device
46 numbers. The mismatch is either by omission, specification is too new,
63 specification, and CXL Fixed Memory Window Structures (CEDT.CFMWS)
96 specification for a detailed description of HDM.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/include/media/ |
| D | v4l2-jpeg.h | 34 * struct v4l2_jpeg_frame_component_spec - frame component-specification
53 * @component: component-specification, see v4l2_jpeg_frame_component_spec
54 * @subsampling: decoded subsampling from component-specification
68 * struct v4l2_jpeg_scan_component_spec - scan component-specification
82 * @component: component-specification, see v4l2_jpeg_scan_component_spec
|
| /kernel/linux/linux-5.10/drivers/infiniband/ulp/srpt/ |
| D | ib_dm_mad.h | 45 * 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.
|
| /kernel/linux/linux-6.6/drivers/infiniband/ulp/srpt/ |
| D | ib_dm_mad.h | 45 * 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.
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/sfc/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/ |
| D | i2c-rk3x.yaml | 86 (t(r) in I2C specification). If not specified this is assumed to be
87 the maximum the specification allows(1000 ns for Standard-mode,
94 (t(f) in the I2C specification). If not specified this is assumed to
95 be the maximum the specification allows (300 ns) which might cause
102 (t(f) in the I2C specification). If not specified we will use the SCL
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-rk3x.yaml | 82 (t(r) in I2C specification). If not specified this is assumed to be
83 the maximum the specification allows(1000 ns for Standard-mode,
90 (t(f) in the I2C specification). If not specified this is assumed to
91 be the maximum the specification allows (300 ns) which might cause
98 (t(f) in the I2C specification). If not specified we will use the SCL
|
| /kernel/linux/linux-6.6/Documentation/gpu/amdgpu/display/ |
| D | multi-display-hdcp-mpo-less-pipe-ex.svg | 115 …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…
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/ |
| D | zet6223.txt | 6 - interrupts : interrupt specification for the zet6223 interrupt
10 - vio-supply : Specification for VIO supply (1.8V or 3.3V,
12 - vcc-supply : Specification for 3.3V VCC supply.
|
12345678910>>...119
![[all …]](/OpenHarmony-v6.0-Release/more/kernel/linux/linux-5.10/Documentation/RCU/Design/Requirements/ReadersPartitionGP1.svg?full=Specification){kind=link}
![[all …]](/OpenHarmony-v6.0-Release/more/kernel/linux/linux-5.10/Documentation/RCU/Design/Requirements/GPpartitionReaders1.svg?full=Specification){kind=link}
![[all …]](/OpenHarmony-v6.0-Release/more/kernel/linux/linux-6.6/Documentation/RCU/Design/Requirements/ReadersPartitionGP1.svg?full=Specification){kind=link}
![[all …]](/OpenHarmony-v6.0-Release/more/kernel/linux/linux-6.6/Documentation/RCU/Design/Requirements/GPpartitionReaders1.svg?full=Specification){kind=link}
