Searched full:described (Results 1 – 25 of 993) sorted by relevance
12345678910>>...40
| /Documentation/arch/arm64/ |
| 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
|
| D | elf_hwcaps.rst | 32 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/arch/arm64/cpu-feature-registers.rst.
165 ID_AA64ISAR1_EL1.API == 0b0001, as described by
170 ID_AA64ISAR1_EL1.GPI == 0b0001, as described by
238 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0010, as described
251 Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0011, as described
255 Functionality implied by ID_AA64PFR1_EL1.SME == 0b0001, as described
|
| /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
|
| /Documentation/admin-guide/device-mapper/ |
| 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 …]
|
| /Documentation/devicetree/bindings/i3c/ |
| 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.
|
| /Documentation/devicetree/bindings/mmc/ |
| D | pxa-mmc.txt | 12 In addition to the properties described in this document, the details
13 described in mmc.txt are supported.
|
| D | mmc-pwrseq-emmc.yaml | 14 procedure, as described by Jedec 4.4 specification. This procedure is
32 reset procedure as described in Jedec 4.4 specification, the
|
| D | sdhci-omap.txt | 22 - pinctrl-<n> : Pinctrl states as described in bindings/pinctrl/pinctrl-bindings.txt
25 - dmas: List of DMA specifiers with the controller specific format as described
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| 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
|
| /Documentation/userspace-api/media/dvb/ |
| 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
|
| D | fe-diseqc-send-burst.rst | 29 An integer enumered value described at :c:type:`fe_sec_mini_cmd`.
49 Generic error codes are described at the
|
| D | fe-get-info.rst | 48 The frontend capabilities are described at :c:type:`fe_caps`.
58 Generic error codes are described at the
|
| D | fe-set-tone.rst | 29 an integer enumered value described at :c:type:`fe_sec_tone_mode`
55 Generic error codes are described at the
|
| D | fe-set-voltage.rst | 29 an integer enumered value described at :c:type:`fe_sec_voltage`
59 Generic error codes are described at the
|
| /Documentation/devicetree/bindings/net/ |
| D | ipq806x-dwmac.txt | 4 described in the file net/stmmac.txt with the following changes.
10 described in net/stmmac.txt
|
| /Documentation/ABI/stable/ |
| 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
|
| /Documentation/devicetree/bindings/dma/ |
| 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.
|
| D | renesas,nbpfaxi.txt | 35 You can use dma-channels and dma-requests as described in dma.txt, although they
60 dmas and dma-names are required, as described in dma.txt.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-power-wilco | 32 Used when charge_type="Custom", as described above. Measured in
39 Used when charge_type="Custom", as described above. Measured in
|
| /Documentation/virt/hyperv/ |
| D | clocks.rst | 14 per-CPU timers as described in the TLFS, they are not used by the
25 and four synthetic per-CPU timers as described in the TLFS. Hyper-V
43 as described in the Hyper-V TLFS. The resulting value advances
69 vmbus_isr() as described in the Documentation/virt/hyperv/vmbus.rst
|
| /Documentation/userspace-api/media/v4l/ |
| 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
|
| D | vidioc-g-ext-ctrls.rst | 454 - The class containing user controls. These controls are described
462 described in :ref:`codec-controls`.
465 - The class containing camera controls. These controls are described
470 controls are described in :ref:`fm-tx-controls`.
474 described in :ref:`flash-controls`.
478 described in :ref:`jpeg-controls`.
482 described in :ref:`image-source-controls`.
486 described in :ref:`image-process-controls`.
490 are described in :ref:`fm-rx-controls`.
494 described in :ref:`rf-tuner-controls`.
[all …]
|
| /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
|
| /Documentation/usb/ |
| D | functionfs-desc.rst | 6 described below. Device and configuration descriptors are handled
35 The DFU functional descriptor is a described in the USB specification for
|
| /Documentation/devicetree/bindings/i2c/ |
| 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
|
12345678910>>...40