Home
last modified time | relevance | path

Searched full:described (Results 1 – 25 of 1875) sorted by relevance

12345678910>>...75

/Linux-v5.15/Documentation/admin-guide/device-mapper/
Ddm-ima.rst180 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 …]
/Linux-v5.15/Documentation/arm64/
Delf_hwcaps.rst32 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/arm64/cpu-feature-registers.rst.
165 ID_AA64ISAR1_EL1.API == 0b0001, as described by
170 ID_AA64ISAR1_EL1.GPI == 0b0001, as described by
247 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0010, as described
/Linux-v5.15/Documentation/devicetree/bindings/i3c/
Di3c.yaml14 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
174 * resources described in the DT.
/Linux-v5.15/Documentation/devicetree/bindings/regulator/
Dqcom,spmi-regulator.txt44 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-v5.15/fs/ntfs/
Dbitmap.h28 * 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.
Dindex.h22 * @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.15/Documentation/userspace-api/media/v4l/
Dvidioc-g-ext-ctrls.rst376 - The class containing user controls. These controls are described
384 described in :ref:`codec-controls`.
387 - The class containing camera controls. These controls are described
392 controls are described in :ref:`fm-tx-controls`.
396 described in :ref:`flash-controls`.
400 described in :ref:`jpeg-controls`.
404 described in :ref:`image-source-controls`.
408 described in :ref:`image-process-controls`.
412 are described in :ref:`fm-rx-controls`.
416 described in :ref:`rf-tuner-controls`.
[all …]
Dpixfmt-meta-intel-ipu3.rst18 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-v5.15/drivers/mfd/
Datmel-smc.c35 * 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.15/Documentation/devicetree/bindings/display/armada/
Dmarvell,dove-lcd.txt7 - 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.15/Documentation/userspace-api/media/rc/
Drc-protos.rst183 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-v5.15/Documentation/devicetree/bindings/mmc/
Dhi3798cv200-dw-mshc.txt8 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.
Dpxa-mmc.txt12 In addition to the properties described in this docuent, the details
13 described in mmc.txt are supported.
/Linux-v5.15/include/uapi/drm/
Dvmwgfx_drm.h244 * @rep: Output data as described above.
245 * @req: Input data as described above.
272 * @rep: Output data as described above.
273 * @req: Input data as described above.
430 * @req: Input data as described above.
431 * @rep: Output data as described above.
917 * @drm_surface_flags Flags as described above.
966 * @req: Input argument as described above.
967 * @rep: Output argument as described above.
993 * @creq: The data used as input when the surface was created, as described
[all …]
/Linux-v5.15/Documentation/devicetree/bindings/crypto/
Datmel-crypto.txt11 - 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.15/Documentation/admin-guide/pm/
Dsuspend-flows.rst93 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-v5.15/Documentation/networking/
Dcdc_mbim.rst64 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-v5.15/Documentation/devicetree/bindings/mtd/
Dmarvell-nand.txt11 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.15/Documentation/hwmon/
Dabituguru-datasheet.rst25 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.15/Documentation/devicetree/bindings/mfd/
Dqcom-rpm.txt89 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:
/Linux-v5.15/Documentation/devicetree/bindings/opp/
Dqcom-opp.txt4 described in Documentation/devicetree/bindings/opp/opp-v2-base.yaml
5 Additional properties are described below.
/Linux-v5.15/Documentation/devicetree/bindings/i2c/
Di2c-pxa-pci-ce4100.txt4 CE4100 has one PCI device which is described as the I2C-Controller. This
25 ranges allows the address mapping to be described
42 /* as described by Grant, the first number in the group of
/Linux-v5.15/Documentation/devicetree/bindings/powerpc/fsl/
Dmpc512x_lpbfifo.txt7 interrupt client node is described in interrupt-controller/interrupts.txt;
8 - dmas: should contain the DMA specifier for SCLPC as described at
/Linux-v5.15/Documentation/userspace-api/media/dvb/
Dlegacy_dvb_apis.rst9 The APIs described here **should not** be used on new drivers or applications.
16 The APIs described here doesn't necessarily reflect the current
/Linux-v5.15/Documentation/devicetree/bindings/pps/
Dpps-gpio.txt8 - gpios: one PPS GPIO in the format described by ../gpio/gpio.txt
11 - echo-gpios: one PPS ECHO GPIO in the format described by ../gpio/gpio.txt

12345678910>>...75