Searched full:described (Results 1 – 25 of 3579) sorted by relevance
12345678910>>...144
| /kernel/linux/linux-6.6/Documentation/admin-guide/device-mapper/ |
| D | dm-ima.rst | 180 dm_version_str := As described in the 'Table load' section above.
181 device_metadata := As described in the 'Table load' section above.
187 as described in the 'dm_table_load' above.
219 dm_version_str := As described in the 'Table load' section above.
221 … The format is same as 'device_metadata' described in the 'Table load' section above.
223 … The format is same as 'device_metadata' described in the 'Table load' section above.
225 … The format is same as 'active_table_hash' described in the 'Device resume' section above.
227 … The format is same as 'active_table_hash' described in the 'Device resume' section above.
259 dm_version_str := As described in the 'Table load' section above.
261 … The format is same as 'device_metadata' described in the 'Table load' section above.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | elf_hwcaps.rst | 30 Where software relies on a feature described by a hwcap, it should check
44 which are described by architected ID registers inaccessible to
49 Such hwcaps are described below in the form::
60 described by ID registers alone. These may be described without
103 described by Documentation/arm64/cpu-feature-registers.rst.
163 ID_AA64ISAR1_EL1.API == 0b0001, as described by
168 ID_AA64ISAR1_EL1.GPI == 0b0001, as described by
245 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0010, as described
|
| /kernel/linux/linux-6.6/Documentation/arch/arm64/ |
| D | elf_hwcaps.rst | 32 Where software relies on a feature described by a hwcap, it should check
46 which are described by architected ID registers inaccessible to
51 Such hwcaps are described below in the form::
62 described by ID registers alone. These may be described without
105 described by Documentation/arch/arm64/cpu-feature-registers.rst.
165 ID_AA64ISAR1_EL1.API == 0b0001, as described by
170 ID_AA64ISAR1_EL1.GPI == 0b0001, as described by
238 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0010, as described
251 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0011, as described
255 Functionality implied by ID_AA64PFR1_EL1.SME == 0b0001, as described
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | qcom,spmi-regulator.txt | 44 described in the data sheet.
59 described in the data sheet.
77 described in the data sheet.
97 described in the data sheet
128 described in the data sheet.
137 described in the data sheet.
152 described in the data sheet.
166 described in the data sheet.
183 described in the data sheet.
222 see regulator.txt - with additional custom properties described below:
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/s390/cf_z16/ |
| D | pai_ext.json | 141 "PublicDescription": "NNPA function with conditions as described in Common Operation"
148 "PublicDescription": "NNPA function with conditions as described in Common Operation"
155 "PublicDescription": "NNPA function with conditions as described in Common Operation"
162 "PublicDescription": "NNPA function with conditions as described in Common Operation"
169 "PublicDescription": "NNPA function with conditions as described in Common Operation"
176 "PublicDescription": "NNPA function with conditions as described in Common Operation"
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/i3c/ |
| D | i3c.yaml | 14 I3C busses can be described with a node for the primary I3C controller device
25 Each I2C device connected to the bus should be described in a subnode.
29 described in the device tree. This being said, one might want to attach
31 described in the device tree, which in turn means we have to describe
53 I2C devices described in the device tree to determine the maximum I2C
68 All properties described in Documentation/devicetree/bindings/i2c/i2c.txt
181 * resources described in the DT.
|
| /kernel/linux/linux-6.6/fs/ntfs/ |
| D | bitmap.h | 28 * Set @count bits starting at bit @start_bit in the bitmap described by the
46 * Set @count bits starting at bit @start_bit in the bitmap described by the
63 * Clear @count bits starting at bit @start_bit in the bitmap described by the
79 * Set bit @bit in the bitmap described by the vfs inode @vi.
93 * Clear bit @bit in the bitmap described by the vfs inode @vi.
|
| /kernel/linux/linux-5.10/fs/ntfs/ |
| D | bitmap.h | 28 * Set @count bits starting at bit @start_bit in the bitmap described by the
46 * Set @count bits starting at bit @start_bit in the bitmap described by the
63 * Clear @count bits starting at bit @start_bit in the bitmap described by the
79 * Set bit @bit in the bitmap described by the vfs inode @vi.
93 * Clear bit @bit in the bitmap described by the vfs inode @vi.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i3c/ |
| D | i3c.txt | 29 values of I2C devices described in the device tree to determine
35 Each I2C device connected to the bus should be described in a subnode. All
36 properties described in Documentation/devicetree/bindings/i2c/i2c.txt are
72 are thus discoverable. So, by default, I3C devices do not have to be described
75 and those resources may have to be described in the device tree, which in turn
134 * resources described in the DT.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/armada/ |
| D | marvell,dove-lcd.txt | 7 - port: video output port with endpoints, as described by graph.txt
11 - clocks: as described by clock-bindings.txt
12 - clock-names: as described by clock-bindings.txt
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/armada/ |
| D | marvell,dove-lcd.txt | 7 - port: video output port with endpoints, as described by graph.txt
11 - clocks: as described by clock-bindings.txt
12 - clock-names: as described by clock-bindings.txt
|
| /kernel/linux/linux-5.10/drivers/mfd/ |
| D | atmel-smc.c | 35 * This function encodes the @ncycles value as described in the datasheet
86 * This function encodes the @ncycles value as described in the datasheet
107 * The formula described in atmel datasheets (section "HSMC Timings in atmel_smc_cs_conf_set_timing()
128 * This function encodes the @ncycles value as described in the datasheet
146 * The formula described in atmel datasheets (section "SMC Setup in atmel_smc_cs_conf_set_setup()
167 * This function encodes the @ncycles value as described in the datasheet
185 * The formula described in atmel datasheets (section "SMC Pulse in atmel_smc_cs_conf_set_pulse()
206 * This function encodes the @ncycles value as described in the datasheet
223 * The formula described in atmel datasheets (section "SMC Cycle in atmel_smc_cs_conf_set_cycle()
|
| /kernel/linux/linux-6.6/drivers/mfd/ |
| D | atmel-smc.c | 35 * This function encodes the @ncycles value as described in the datasheet
86 * This function encodes the @ncycles value as described in the datasheet
107 * The formula described in atmel datasheets (section "HSMC Timings in atmel_smc_cs_conf_set_timing()
128 * This function encodes the @ncycles value as described in the datasheet
146 * The formula described in atmel datasheets (section "SMC Setup in atmel_smc_cs_conf_set_setup()
167 * This function encodes the @ncycles value as described in the datasheet
185 * The formula described in atmel datasheets (section "SMC Pulse in atmel_smc_cs_conf_set_pulse()
206 * This function encodes the @ncycles value as described in the datasheet
223 * The formula described in atmel datasheets (section "SMC Cycle in atmel_smc_cs_conf_set_cycle()
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 430 - The class containing user controls. These controls are described
438 described in :ref:`codec-controls`.
441 - The class containing camera controls. These controls are described
446 controls are described in :ref:`fm-tx-controls`.
450 described in :ref:`flash-controls`.
454 described in :ref:`jpeg-controls`.
458 described in :ref:`image-source-controls`.
462 described in :ref:`image-process-controls`.
466 are described in :ref:`fm-rx-controls`.
470 described in :ref:`rf-tuner-controls`.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 320 - The class containing user controls. These controls are described
328 described in :ref:`mpeg-controls`.
331 - The class containing camera controls. These controls are described
336 controls are described in :ref:`fm-tx-controls`.
340 described in :ref:`flash-controls`.
344 described in :ref:`jpeg-controls`.
348 described in :ref:`image-source-controls`.
352 described in :ref:`image-process-controls`.
356 are described in :ref:`fm-rx-controls`.
360 described in :ref:`rf-tuner-controls`.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/rc/ |
| D | rc-protos.rst | 183 described here https://www.sbprojects.net/knowledge/ir/jvc.php.
279 described here https://www.sbprojects.net/knowledge/ir/nec.php. Note
354 This is the rc-6 in mode 0. rc-6 is described here
362 This is the rc-6 in mode 6a, 20 bits. rc-6 is described here
370 This is the rc-6 in mode 6a, 24 bits. rc-6 is described here
378 This is the rc-6 in mode 6a, 32 bits. rc-6 is described here
397 This is a protocol used by Sharp VCRs, is described here
431 The rc-mm protocol is described here
438 The rc-mm protocol is described here
445 The rc-mm protocol is described here
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/rc/ |
| D | rc-protos.rst | 183 described here https://www.sbprojects.net/knowledge/ir/jvc.php.
279 described here https://www.sbprojects.net/knowledge/ir/nec.php. Note
354 This is the rc-6 in mode 0. rc-6 is described here
362 This is the rc-6 in mode 6a, 20 bits. rc-6 is described here
370 This is the rc-6 in mode 6a, 24 bits. rc-6 is described here
378 This is the rc-6 in mode 6a, 32 bits. rc-6 is described here
397 This is a protocol used by Sharp VCRs, is described here
431 The rc-mm protocol is described here
438 The rc-mm protocol is described here
445 The rc-mm protocol is described here
|
| /kernel/linux/linux-6.6/Documentation/arch/loongarch/ |
| D | irq-chip-model.rst | 149 - CPUINTC is CSR.ECFG/CSR.ESTAT and its interrupt controller described
151 - LIOINTC is "Legacy I/OInterrupts" described in Section 11.1 of
153 - EIOINTC is "Extended I/O Interrupts" described in Section 11.2 of
155 - HTVECINTC is "HyperTransport Interrupts" described in Section 14.3 of
157 - PCH-PIC/PCH-MSI is "Interrupt Controller" described in Section 5 of
159 - PCH-LPC is "LPC Interrupts" described in Section 24.3 of
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/ |
| D | hi3798cv200-dw-mshc.txt | 8 differences between the core Synopsys dw mshc controller properties described
17 "ciu" - The ciu clock described in synopsys-dw-mshc.txt.
18 "biu" - The biu clock described in synopsys-dw-mshc.txt.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mmc/ |
| D | hi3798cv200-dw-mshc.txt | 8 differences between the core Synopsys dw mshc controller properties described
17 "ciu" - The ciu clock described in synopsys-dw-mshc.txt.
18 "biu" - The biu clock described in synopsys-dw-mshc.txt.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/media/ |
| D | video-mux.txt | 5 on the active input port is passed through to the output port. Muxes described
6 by this binding are controlled by a multiplexer controller that is described by
19 ports node as described in Documentation/devicetree/bindings/graph.txt.
|
| /kernel/linux/linux-5.10/include/uapi/drm/ |
| D | vmwgfx_drm.h | 241 * @rep: Output data as described above.
242 * @req: Input data as described above.
269 * @rep: Output data as described above.
270 * @req: Input data as described above.
427 * @req: Input data as described above.
428 * @rep: Output data as described above.
914 * @drm_surface_flags Flags as described above.
963 * @req: Input argument as described above.
964 * @rep: Output argument as described above.
990 * @creq: The data used as input when the surface was created, as described
[all …]
|
| /kernel/linux/linux-6.6/include/uapi/drm/ |
| D | vmwgfx_drm.h | 252 * @rep: Output data as described above.
253 * @req: Input data as described above.
280 * @rep: Output data as described above.
281 * @req: Input data as described above.
438 * @req: Input data as described above.
439 * @rep: Output data as described above.
925 * @drm_surface_flags Flags as described above.
974 * @req: Input argument as described above.
975 * @rep: Output argument as described above.
1001 * @creq: The data used as input when the surface was created, as described
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/crypto/ |
| D | atmel-crypto.txt | 11 - dmas: List of two DMA specifiers as described in
33 - dmas: List of two DMA specifiers as described in
56 - dmas: One DMA specifiers as described in
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 93 deferred till the subsequent system resume transition as described
173 described `above <s2idle_suspend_>`_.
178 described `above <s2idle_suspend_>`_.
183 described `above <s2idle_suspend_>`_, but the arming of IRQs for system
260 described `above <s2idle_resume_>`_.
265 described `above <s2idle_resume_>`_.
270 described `above <s2idle_resume_>`_.
|
12345678910>>...144