Searched full:shown (Results 1 – 25 of 228) sorted by relevance
12345678910
| /Documentation/devicetree/bindings/ata/ |
| D | ceva,ahci-1v84.yaml | 45 The fields for the above parameter must be as shown below:-
57 The fields for the above parameter must be as shown below:-
69 The fields for the above parameter must be as shown below:-
81 The fields for the above parameter must be as shown below:-
91 The fields for the above parameter must be as shown below:-
103 The fields for the above parameter must be as shown below:-
115 The fields for the above parameter must be as shown below:-
127 The fields for the above parameter must be as shown below:-
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-asus-wmi | 144 Shown on Intel+Nvidia or AMD+Nvidia based systems:
154 on AMD. Shown on Intel+Nvidia or AMD+Nvidia based systems:
171 Set the APU SPPT limit. Shown on full AMD systems only:
179 Set the platform SPPT limit. Shown on full AMD systems only:
|
| D | sysfs-bus-event_source-devices-caps | 21 maximum number of counters which can be shown in the u64 counters
|
| D | sysfs-class-rc | 28 Enabled protocols are shown in [] brackets.
89 The enabled wakeup protocol is shown in [] brackets.
|
| /Documentation/trace/ |
| D | hisi-ptt.rst | 171 8 bit. Current supported types and related values are shown below:
187 supported are shown below:
195 shown below:
212 Current supported formats and related values are shown below:
220 (Header DW0-3 shown below). For example, the TLP header for Memory
221 Reads with 64-bit addresses is shown in PCIe r5.0, Figure 2-17;
222 the header for Configuration Requests is shown in Figure 2.20, etc.
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti,da850-mstpri.txt | 15 Example for da850-lcdk is shown below.
|
| D | mvebu-mbus.txt | 139 In the shown example, the translation entry in the 'ranges' property is what
193 of 0xf0000000, or 0xd0000000 for the NOR device shown above, if such region is
214 See the example below, where a more complete device tree is shown:
|
| /Documentation/kbuild/ |
| D | gendwarfksyms.rst | 159 (as shown in **--dump-dies** output).
186 (as shown in **--dump-dies** output) and the name of the
211 (as shown in **--dump-dies** output) and the name of the
247 (as shown in **--dump-dies** output).
283 (as shown in **--dump-dies** output) or symbol.
284 - `value`: A valid type string (as shown in **--symtypes**) output)
|
| /Documentation/pcmcia/ |
| D | driver.rst | 9 runtime as shown below::
|
| /Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 8 March 2023, the original deprecation notice is shown below.
|
| D | sysfs-selinux-disable | 8 in March 2023, the original deprecation notice is shown below.
|
| /Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 197 shown below, which is one of several functions that enforce ordering of
275 portion of RCU's grace period guarantee is shown in the following
285 period until a later call to ``rcu_accelerate_cbs()``, as shown in the
288 One set of code paths shown on the left invokes ``rcu_accelerate_cbs()``
342 counter, as shown below:
370 to the newly advanced value from the ``rcu_state`` structure, as shown
410 non-idle CPUs report their own quiescent states, as shown in the
425 its leaf ``rcu_node`` lock. Therefore, all execution shown in this
462 traverses up the ``rcu_node`` tree as shown at the bottom of the
486 effects are as shown below:
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-intro.rst | 20 and the cropping target is a part of an image to be shown on a display.
|
| /Documentation/sound/designs/ |
| D | procfile.rst | 110 shown also when the invalid H/W pointer is detected at the
197 ports. The connection status and the running status are shown
224 - set-up of PCM, shown in hw_parms, sw_params, and status in the PCM
|
| /Documentation/accounting/ |
| D | cgroupstats.rst | 26 has been developed, the sample output of the utility is shown below::
|
| /Documentation/admin-guide/media/ |
| D | pci-cardlist.rst | 53 .. [#] some of the drivers have sub-drivers, not shown at this table
96 Some of those drivers support multiple devices, as shown at the card
|
| /Documentation/leds/ |
| D | ledtrig-oneshot.rst | 20 The trigger can be activated from user space on led class devices as shown
|
| D | ledtrig-usbport.rst | 32 This trigger can be activated from user space on led class devices as shown
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-sysfs-nodes.rst | 41 Enabled protocols are shown in [] brackets.
102 The enabled wakeup protocol is shown in [] brackets.
|
| /Documentation/devicetree/bindings/sound/ |
| D | rt5663.txt | 32 R channel accordingly. Example is shown as following.
|
| /Documentation/admin-guide/mm/ |
| D | ksm.rst | 193 The effectiveness of KSM and MADV_MERGEABLE is shown in ``/sys/kernel/mm/ksm/``:
260 ``ksm_zero_pages``, both of which are shown under the directory
261 ``/proc/<pid>/ksm_stat``, and ksm_rmap_items is also shown in
262 ``/proc/<pid>/ksm_stat``. The process profit is also shown in
|
| /Documentation/userspace-api/media/ |
| D | intro.rst | 12 A typical media device hardware is shown at :ref:`typical_media_device`.
|
| /Documentation/filesystems/ |
| D | hfsplus.rst | 18 Specifies the creator/type values as shown by the MacOS finder
|
| /Documentation/devicetree/bindings/media/ |
| D | renesas,drif.yaml | 15 representation of DRIF interfacing with a master device is shown below.
158 # When interfacing with a third party tuner device with two data pins as shown
215 # When interfacing with a third party tuner device with one data pin as shown
|
| /Documentation/admin-guide/ |
| D | svga.rst | 84 case your chipset has been detected, some chipset-specific modes are shown as
104 modes are not listed at all and the modes revealed by ``scan`` are shown before
113 by entering its mode directly if you know it even if it isn't shown on the menu.
125 0x0100. All VESA modes should be autodetected and shown on the menu.
|
12345678910