Searched full:shown (Results 1 – 25 of 562) sorted by relevance
12345678910>>...23
| /linux-6.14.4/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:-
|
| /linux-6.14.4/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.
|
| /linux-6.14.4/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-class-rc | 28 Enabled protocols are shown in [] brackets.
89 The enabled wakeup protocol is shown in [] brackets.
|
| D | sysfs-bus-event_source-devices-caps | 21 maximum number of counters which can be shown in the u64 counters
|
| /linux-6.14.4/tools/perf/Documentation/ |
| D | callchain-overhead-calculation.txt | 3 The overhead can be shown in two columns as 'Children' and 'Self' when
100 So '\_\_libc_start_main' and 'main' are shown first since they have
104 Since v3.16 the 'children' overhead is shown by default and the output
|
| /linux-6.14.4/include/linux/sched/ |
| D | debug.h | 30 * task), SP is the stack pointer of the first frame that should be shown in the back
31 * trace (or NULL if the entire call-chain of the task should be shown).
|
| /linux-6.14.4/include/linux/ |
| D | coda.h | 16 shown in the file LICENSE, or under the license shown below. The
|
| D | crc8.h | 47 * represented as shown below.
65 * represented as shown below.
|
| /linux-6.14.4/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 …]
|
| /linux-6.14.4/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
|
| /linux-6.14.4/tools/memory-model/Documentation/ |
| D | recipes.txt | 217 the desired MP ordering. The general approach is shown below:
248 pointers. The general approach is shown below:
276 (address dependency, as shown above), the value written by a later store
293 to understand their use cases. The general approach is shown below:
381 The A/D pairing from the ring-buffer use case shown earlier also
495 values of 0, but providing both full barriers as shown above prevents
|
| /linux-6.14.4/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
|
| /linux-6.14.4/Documentation/devicetree/bindings/bus/ |
| 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:
|
| D | ti,da850-mstpri.txt | 15 Example for da850-lcdk is shown below.
|
| /linux-6.14.4/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.
|
| /linux-6.14.4/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
|
| /linux-6.14.4/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
|
| D | usb-cardlist.rst | 35 some of the drivers have sub-drivers, not shown at this table.
38 as shown at :doc:`gspca card list <gspca-cardlist>`.
|
| /linux-6.14.4/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.
|
| /linux-6.14.4/tools/power/cpupower/man/ |
| D | cpupower-monitor.1 | 32 are shown:
94 a state residency of 0 percent is shown while it was 100.
|
| /linux-6.14.4/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 43 expedited grace period is shown in the following diagram:
117 shown in the following diagram:
301 An empty ``rcu_node`` tree is shown in the following diagram, with the
318 number and resulting in the state shown below:
347 ``->exp_wq[1]`` fields, as shown below:
354 number of 4 and will record this value as shown below:
361 resulting state is as shown below:
|
| /linux-6.14.4/Documentation/kbuild/ |
| D | gendwarfksyms.rst | 156 (as shown in **--dump-dies** output).
183 (as shown in **--dump-dies** output) and the name of the
208 (as shown in **--dump-dies** output) and the name of the
|
| /linux-6.14.4/drivers/interconnect/mediatek/ |
| D | icc-emi.h | 13 * @name: The interconnect node name which is shown in debugfs
|
| /linux-6.14.4/Documentation/pcmcia/ |
| D | driver.rst | 9 runtime as shown below::
|
12345678910>>...23