Searched full:shown (Results 1 – 25 of 971) sorted by relevance
12345678910>>...39
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/ata/ |
| D | ceva,ahci-1v84.yaml | 44 The fields for the above parameter must be as shown below:-
56 The fields for the above parameter must be as shown below:-
68 The fields for the above parameter must be as shown below:-
80 The fields for the above parameter must be as shown below:-
90 The fields for the above parameter must be as shown below:-
102 The fields for the above parameter must be as shown below:-
114 The fields for the above parameter must be as shown below:-
126 The fields for the above parameter must be as shown below:-
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ata/ |
| D | ahci-ceva.txt | 10 The fields for the above parameter must be as shown below:
18 The fields for the above parameter must be as shown below:
26 The fields for the above parameter must be as shown below:
34 The fields for the above parameter must be as shown below:
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-platform-asus-wmi | 136 Shown on Intel+Nvidia or AMD+Nvidia based systems:
146 on AMD. Shown on Intel+Nvidia or AMD+Nvidia based systems:
163 Set the APU SPPT limit. Shown on full AMD systems only:
171 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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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).
|
| /kernel/linux/linux-5.10/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).
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 168 shown below, which is one of several functions that enforce ordering of
251 portion of RCU's grace period guarantee is shown in the following
261 period until a later call to ``rcu_accelerate_cbs()``, as shown in the
264 One set of code paths shown on the left invokes ``rcu_accelerate_cbs()``
318 counter, as shown below:
346 to the newly advanced value from the ``rcu_state`` structure, as shown
386 non-idle CPUs report their own quiescent states, as shown in the
401 its leaf ``rcu_node`` lock. Therefore, all execution shown in this
438 traverses up the ``rcu_node`` tree as shown at the bottom of the
462 effects are as shown below:
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/mm/ |
| D | ksm.rst | 158 The effectiveness of KSM and MADV_MERGEABLE is shown in ``/sys/kernel/mm/ksm/``:
223 ``ksm_zero_pages``, both of which are shown under the directory
224 ``/proc/<pid>/ksm_stat``, and ksm_rmap_items is also shown in
225 ``/proc/<pid>/ksm_stat``. The process profit is also shown in
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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:
|
| /kernel/linux/linux-6.6/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:
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-rc | 28 Enabled protocols are shown in [] brackets.
89 The enabled wakeup protocol is shown in [] brackets.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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>>...39