Home
last modified time | relevance | path

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

12345678910>>...118

/kernel/linux/linux-5.10/Documentation/arm64/
Delf_hwcaps.rst30 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-5.10/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:
/kernel/linux/linux-4.19/Documentation/arm64/
Delf_hwcaps.txt29 Where software relies on a feature described by a hwcap, it should check
43 which are described by architected ID registers inaccessible to
48 Such hwcaps are described below in the form:
59 described by ID registers alone. These may be described without
114 described by Documentation/arm64/cpu-feature-registers.txt.
Dbooting.txt139 Any memory described to the kernel (even that below the start of the
208 The requirements described above for CPU mode, caches, MMUs, architected
218 enable-methods are described below.
239 the kernel (i.e. outside of the regions of memory described to the
240 kernel in the memory node, or in a reserved area of memory described
242 kernel will issue CPU_ON calls as described in ARM document number ARM
246 The device tree should contain a 'psci' node, as described in
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-4.19/Documentation/media/uapi/v4l/
Dvidioc-g-ext-ctrls.rst298 - The class containing user controls. These controls are described
306 described in :ref:`mpeg-controls`.
309 - The class containing camera controls. These controls are described
314 controls are described in :ref:`fm-tx-controls`.
318 described in :ref:`flash-controls`.
322 described in :ref:`jpeg-controls`.
326 described in :ref:`image-source-controls`.
330 described in :ref:`image-process-controls`.
334 are described in :ref:`fm-rx-controls`.
338 described in :ref:`rf-tuner-controls`.
[all …]
/kernel/linux/linux-4.19/fs/ntfs/
Dbitmap.h42 * Set @count bits starting at bit @start_bit in the bitmap described by the
60 * Set @count bits starting at bit @start_bit in the bitmap described by the
77 * Clear @count bits starting at bit @start_bit in the bitmap described by the
93 * Set bit @bit in the bitmap described by the vfs inode @vi.
107 * Clear bit @bit in the bitmap described by the vfs inode @vi.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/i3c/
Di3c.txt29 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-4.19/Documentation/devicetree/bindings/regulator/
Dqcom,smd-rpm-regulator.txt41 described in the data sheet
54 described in the data sheet
72 described in the data sheet
122 described in the data sheet
154 described in the data sheet
183 described in the data sheet
189 described in the data sheet
Dqcom,spmi-regulator.txt38 described in the data sheet.
53 described in the data sheet.
71 described in the data sheet.
102 described in the data sheet.
111 described in the data sheet.
144 see regulator.txt - with additional custom properties described below:
/kernel/linux/linux-5.10/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
/kernel/linux/linux-4.19/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
/kernel/linux/linux-4.19/drivers/mfd/
Datmel-smc.c38 * This function encodes the @ncycles value as described in the datasheet
89 * This function encodes the @ncycles value as described in the datasheet
110 * The formula described in atmel datasheets (section "HSMC Timings in atmel_smc_cs_conf_set_timing()
131 * This function encodes the @ncycles value as described in the datasheet
149 * The formula described in atmel datasheets (section "SMC Setup in atmel_smc_cs_conf_set_setup()
170 * This function encodes the @ncycles value as described in the datasheet
188 * The formula described in atmel datasheets (section "SMC Pulse in atmel_smc_cs_conf_set_pulse()
209 * This function encodes the @ncycles value as described in the datasheet
226 * The formula described in atmel datasheets (section "SMC Cycle in atmel_smc_cs_conf_set_cycle()
/kernel/linux/linux-5.10/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()
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dvidioc-g-ext-ctrls.rst320 - 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/
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
/kernel/linux/linux-4.19/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.
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/pci/
Dhost-generic-pci.txt11 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
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/media/
Dvideo-mux.txt5 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/Documentation/devicetree/bindings/media/
Dvideo-mux.txt5 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-4.19/include/uapi/drm/
Dvmwgfx_drm.h236 * @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 …]
/kernel/linux/linux-5.10/include/uapi/drm/
Dvmwgfx_drm.h241 * @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-5.10/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
/kernel/linux/linux-4.19/Documentation/ABI/stable/
Dsysfs-driver-usb-usbtmc6 These files show the various USB TMC capabilities as described
20 These files show the various USB TMC capabilities as described
35 device as described by the document, "Universal Serial Bus Test

12345678910>>...118