Searched full:described (Results 1 – 25 of 1800) sorted by relevance
12345678910>>...72
| /Linux-v5.4/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.
192 ID_AA64ISAR1_EL1.API == 0b0001, as described by
197 ID_AA64ISAR1_EL1.GPI == 0b0001, as described by
|
| D | booting.rst | 148 Any memory described to the kernel (even that below the start of the
248 The requirements described above for CPU mode, caches, MMUs, architected
258 enable-methods are described below.
279 the kernel (i.e. outside of the regions of memory described to the
280 kernel in the memory node, or in a reserved area of memory described
282 kernel will issue CPU_ON calls as described in ARM document number ARM
286 The device tree should contain a 'psci' node, as described in
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/regulator/ |
| D | qcom,smd-rpm-regulator.txt | 42 described in the data sheet
55 described in the data sheet
73 described in the data sheet
123 described in the data sheet
155 described in the data sheet
184 described in the data sheet
190 described in the data sheet
208 described in the data sheet
|
| D | qcom,spmi-regulator.txt | 40 described in the data sheet.
55 described in the data sheet.
73 described in the data sheet.
104 described in the data sheet.
113 described in the data sheet.
130 described in the data sheet.
166 see regulator.txt - with additional custom properties described below:
|
| /Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 335 - The class containing user controls. These controls are described
343 described in :ref:`mpeg-controls`.
346 - The class containing camera controls. These controls are described
351 controls are described in :ref:`fm-tx-controls`.
355 described in :ref:`flash-controls`.
359 described in :ref:`jpeg-controls`.
363 described in :ref:`image-source-controls`.
367 described in :ref:`image-process-controls`.
371 are described in :ref:`fm-rx-controls`.
375 described in :ref:`rf-tuner-controls`.
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/rc/ |
| D | rc-protos.rst | 185 described here https://www.sbprojects.net/knowledge/ir/jvc.php.
281 described here https://www.sbprojects.net/knowledge/ir/nec.php. Note
356 This is the rc-6 in mode 0. rc-6 is described here
364 This is the rc-6 in mode 6a, 20 bits. rc-6 is described here
372 This is the rc-6 in mode 6a, 24 bits. rc-6 is described here
380 This is the rc-6 in mode 6a, 32 bits. rc-6 is described here
399 This is a protocol used by Sharp VCRs, is described here
433 The rc-mm protocol is described here
440 The rc-mm protocol is described here
447 The rc-mm protocol is described here
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/pci/ |
| D | host-generic-pci.txt | 11 Such a controller can be described purely in terms of the standardized device
23 - ranges : As described in IEEE Std 1275-1994, but must provide
28 - bus-range : Optional property (also described in IEEE Std 1275-1994)
64 Interrupt mapping is exactly as described in `Open Firmware Recommended
|
| /Linux-v5.4/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-v5.4/include/uapi/drm/ |
| D | vmwgfx_drm.h | 236 * @rep: Output data as described above.
237 * @req: Input data as described above.
264 * @rep: Output data as described above.
265 * @req: Input data as described above.
422 * @req: Input data as described above.
423 * @rep: Output data as described above.
907 * @drm_surface_flags Flags as described above.
956 * @req: Input argument as described above.
957 * @rep: Output argument as described above.
983 * @creq: The data used as input when the surface was created, as described
[all …]
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu-v3.txt | 36 - #iommu-cells : See the generic IOMMU binding described in
40 IDs which a device may emit must be described.
51 - msi-parent : See the generic MSI binding described in
|
| /Linux-v5.4/Documentation/networking/ |
| D | cdc_mbim.txt | 59 The driver <-> userspace interfaces are described below. The MBIM
60 control channel protocol is described in [1].
98 configuration descriptor kernel interfaces described in [6] or [7].
106 fragmentation and defragmentaion, as described in section 9.5 of [1].
174 described in section 10.5.1 of [1].
198 structure described in section 10.5.29 of [1].
263 As described above, MBIM IP session 0 is treated as special by the
291 Summarizing the cdc_mbim driver mapping described above, we have this
|
| /Linux-v5.4/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-v5.4/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-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | rockchip,pinctrl.txt | 49 Use rockchip,grf and rockchip,pmu described above instead.
62 cells should use the standard two-cell scheme described in
68 rockchip,pmu described above instead
75 to use, as described in pinctrl-bindings.txt in this directory.
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/opp/ |
| D | qcom-opp.txt | 4 described in Documentation/devicetree/bindings/opp/opp.txt
5 Additional properties are described below.
|
12345678910>>...72
