| /linux/Documentation/admin-guide/device-mapper/ |
| H A 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 …]
|
| /linux/Documentation/arch/arm64/ |
| H A D | cpu-hotplug.rst | 30 described in a static table, the PPTT. How caches are shared between CPUs is
31 not discoverable, and must be described by firmware.
39 arm64's ACPI tables assume that everything described is ``present``.
46 ever have can be described at boot. There are no power-domain considerations
50 CPU Hotplug as all resources are described as ``present``, but CPUs may be
69 CPUs described as ``online capable`` but not ``enabled`` can be set to enabled
74 CPUs described as ``enabled`` in the static table, should not have their _STA
|
| H A D | booting.rst | 152 Any memory described to the kernel (even that below the start of the
414 must handle MOPS exceptions as described in :ref:`arm64_mops_hyp`.
486 The requirements described above for CPU mode, caches, MMUs, architected
499 enable-methods are described below.
520 the kernel (i.e. outside of the regions of memory described to the
521 kernel in the memory node, or in a reserved area of memory described
523 kernel will issue CPU_ON calls as described in ARM document number ARM
527 The device tree should contain a 'psci' node, as described in
|
| /linux/Documentation/devicetree/bindings/i3c/ |
| H A 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
74 All properties described in dtschema schemas/i2c/i2c-controller.yaml
190 * resources described in the DT.
|
| /linux/tools/perf/pmu-events/arch/s390/cf_z16/ |
| H A 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"
|
| /linux/drivers/mfd/ |
| H A 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/Documentation/userspace-api/media/rc/ |
| H A 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/Documentation/devicetree/bindings/display/armada/ |
| H A 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/include/uapi/drm/ |
| H A D | vmwgfx_drm.h | 253 * @rep: Output data as described above.
254 * @req: Input data as described above.
281 * @rep: Output data as described above.
282 * @req: Input data as described above.
439 * @req: Input data as described above.
440 * @rep: Output data as described above.
927 * @drm_surface_flags Flags as described above.
976 * @req: Input argument as described above.
977 * @rep: Output argument as described above.
1003 * @creq: The data used as input when the surface was created, as described
[all …]
|
| H A D | exynos_drm.h | 249 /* buffer described by struct drm_exynos_ipp_task_buffer */
251 /* rectangle described by struct drm_exynos_ipp_task_rect */
253 /* transformation described by struct drm_exynos_ipp_task_transform */
255 /* alpha configuration described by struct drm_exynos_ipp_task_alpha */
332 * Perform image processing described by array of drm_exynos_ipp_task_*
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | legacy_dvb_audio.rst | 501 appropriately. The generic error codes are described at the
552 appropriately. The generic error codes are described at the
605 appropriately. The generic error codes are described at the
657 appropriately. The generic error codes are described at the
720 appropriately. The generic error codes are described at the
794 appropriately. The generic error codes are described at the
865 appropriately. The generic error codes are described at the
938 appropriately. The generic error codes are described at the
1000 appropriately. The generic error codes are described at the
1059 appropriately. The generic error codes are described at the
[all …]
|
| H A D | legacy_dvb_video.rst | 875 appropriately. The generic error codes are described at the
930 appropriately. The generic error codes are described at the
990 appropriately. The generic error codes are described at the
1045 appropriately. The generic error codes are described at the
1114 appropriately. The generic error codes are described at the
1183 appropriately. The generic error codes are described at the
1242 appropriately. The generic error codes are described at the
1314 appropriately. The generic error codes are described at the
1390 appropriately. The generic error codes are described at the
1457 appropriately. The generic error codes are described at the
[all …]
|
| H A D | legacy_dvb_apis.rst | 9 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/Documentation/admin-guide/pm/ |
| H A 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/Documentation/networking/ |
| H A 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/tools/testing/selftests/kvm/lib/ |
| H A D | sparsebit.c | 86 * The idx member contains the bit index of the first bit described by this
91 * Nodes are sorted by idx and the bits described by two nodes will never
114 * + The setting of at least one bit is always described in a nodes
118 * described by the previous node is not equal to this nodes
139 * + The range of bits described by any two nodes do not overlap. The
140 * range of bits described by a single node is:
194 /* Returns the number of set bits described by the settings
307 * index is within the bits described by the mask bits or the number of
406 /* Clears all bits described by the node pointed to by nodep, then
523 * bits described by num_after. in node_split()
[all …]
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | mediatek,mt8365-pinctrl.yaml | 82 resistance. Valid arguments are described as below:
96 different resistance. Valid arguments are described as below:
135 Valid arguments are described as below:
153 configure those special pins. Valid arguments are described as
167 configure those special pins. Valid arguments are described as
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-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/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-pxa-pci-ce4100.txt | 4 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/Documentation/userspace-api/ |
| H A D | dma-buf-alloc-exchange.rst | 98 These tokens are described in the ``drm_fourcc.h`` file, which is a part of
103 its memory buffers. The number and type of color channels are described:
113 always as described in the format definition, which is usually little-endian.
154 still described as having dimensions of 1920x1080.
160 Each plane must therefore be described with an ``offset`` in bytes, which will be
172 be described with a width of 1000, however the stride will be ``1024 * bpp``,
180 described as having a height of 1080, with the memory allocation for each buffer
188 and modifiers, described together. Within KMS, this is achieved with the
|
| /linux/Documentation/devicetree/bindings/mmc/ |
| H A D | pxa-mmc.txt | 12 In addition to the properties described in this document, the details
13 described in mmc.txt are supported.
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | mpc512x_lpbfifo.txt | 7 interrupt client node is described in interrupt-controller/interrupts.txt;
8 - dmas: should contain the DMA specifier for SCLPC as described at
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | ipq806x-dwmac.txt | 4 described in the file net/stmmac.txt with the following changes.
10 described in net/stmmac.txt
|
| /linux/Documentation/devicetree/bindings/dma/ |
| H A D | mpc512x-dma.txt | 14 is described in interrupt-controller/interrupts.txt file.
29 DMA clients must use the format described in dma/dma.txt file.
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-usb-usbtmc | 6 These files show the various USB TMC capabilities as described
20 These files show the various USB TMC capabilities as described
|