Searched full:described (Results 1 – 25 of 1874) sorted by relevance
12345678910>>...75
| /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
|
| D | booting.rst | 148 Any memory described to the kernel (even that below the start of the
273 The requirements described above for CPU mode, caches, MMUs, architected
283 enable-methods are described below.
304 the kernel (i.e. outside of the regions of memory described to the
305 kernel in the memory node, or in a reserved area of memory described
307 kernel will issue CPU_ON calls as described in ARM document number ARM
311 The device tree should contain a 'psci' node, as described in
|
| /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:
|
| /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.
|
| D | index.h | 22 * @idx_ni: index inode containing the @entry described by this context
35 * @entry is the index entry described by this context. @data and @data_len
39 * If @is_in_root is 'true', @entry is in the index root attribute @ir described
109 * Mark the index entry described by the index entry context @ictx dirty.
|
| /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.
|
| /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
|
| /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()
|
| /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 …]
|
| D | pixfmt-meta-intel-ipu3.rst | 18 interface. They are formatted as described by the :c:type:`ipu3_uapi_stats_3a`
48 formatted as described by the :c:type:`ipu3_uapi_params` structure.
50 Both 3A statistics and pipeline parameters described here are closely tied to
|
| /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
|
| /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.
|
| D | pxa-mmc.txt | 12 In addition to the properties described in this docuent, the details
13 described in mmc.txt are supported.
|
| /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.
|
| /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 …]
|
| /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
|
| /linux-5.10/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_>`_.
|
| /linux-5.10/Documentation/networking/ |
| D | cdc_mbim.rst | 64 The driver <-> userspace interfaces are described below. The MBIM
65 control channel protocol is described in [1].
103 configuration descriptor kernel interfaces described in [6] or [7].
111 fragmentation and defragmentaion, as described in section 9.5 of [1].
181 described in section 10.5.1 of [1].
205 structure described in section 10.5.29 of [1].
271 As described above, MBIM IP session 0 is treated as special by the
300 Summarizing the cdc_mbim driver mapping described above, we have this
|
| /linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | exynos4-clock.txt | 4 within the Exynos4 SoC. The clock binding described here is applicable to all
65 as described in clock-bindings.txt, should be "aclk200" and
68 - power-domains: a phandle to ISP power domain node as described by
|
| D | renesas,emev2-smu.txt | 6 System Management Unit described in user's manual R19UH0037EJ1000_SMU.
23 - clocks: Parent clocks. Input clocks as described in clock-bindings.txt
34 - clocks: Input clock as described in clock-bindings.txt
|
| /linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | marvell-nand.txt | 11 Compatibles marked deprecated support only the old bindings described
59 patterns described in AN-379, "Marvell SoC NFC ECC".
99 bindings slightly different than described above with other properties
100 described below as well as the partitions node at the root of a so
|
| /linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | rockchip,pinctrl.txt | 50 Use rockchip,grf and rockchip,pmu described above instead.
63 cells should use the standard two-cell scheme described in
69 rockchip,pmu described above instead
76 to use, as described in pinctrl-bindings.txt in this directory.
|
| /linux-5.10/Documentation/hwmon/ |
| D | abituguru-datasheet.rst | 25 described here and not the CPU / RAM / etc voltage & frequency control.
103 First the uGuru must be in "ready" mode as described above, DATA should hold
116 First send the bank and sensor addresses as described above.
128 algorithm described above will still work.
135 First send the bank and sensor addresses as described above.
148 algorithm described above will still work.
220 Alarm behaviour for the selected sensor. A 1 enables the described
311 Alarm behaviour for the selected sensor. A 1 enables the described behaviour.
|
| /linux-5.10/Documentation/devicetree/bindings/opp/ |
| D | qcom-opp.txt | 4 described in Documentation/devicetree/bindings/opp/opp.txt
5 Additional properties are described below.
|
| /linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | qcom-rpm.txt | 89 described in the data sheet
111 described in the data sheet
141 described in the data sheet
150 described in the data sheet
179 see regulator.txt - with additional custom properties described below:
|
12345678910>>...75