| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-tmc | 15 The value is read directly from HW register RSZ, 0x004.
22 is read directly from HW register STS, 0x00C.
30 interface. The value is read directly from HW register RRP,
39 the CoreSight bus into the Trace RAM. The value is read directly
47 read directly from HW register TRG, 0x01C.
54 is read directly from HW register CTL, 0x020.
61 register. The value is read directly from HW register FFSR,
69 register. The value is read directly from HW register FFCR,
78 The value is read directly from the MODE register, 0x028.
85 The value is read directly from the DEVID register, 0xFC8,
|
| D | sysfs-bus-coresight-devices-etb10 | 27 2. The value is read directly from HW register RDP, 0x004.
34 is read directly from HW register STS, 0x00C.
42 interface. The value is read directly from HW register RRP,
51 the CoreSight bus into the Trace RAM. The value is read directly
59 read directly from HW register TRG, 0x01C.
66 is read directly from HW register CTL, 0x020.
73 register. The value is read directly from HW register FFSR,
81 register. The value is read directly from HW register FFCR,
|
| D | sysfs-bus-coresight-devices-etm4x | 337 The value it taken directly from the HW.
344 (0x310). The value is taken directly from the HW.
351 (0x314). The value is taken directly from the HW.
358 (0xFB4). The value is taken directly from the HW.
365 (0xFB8). The value is taken directly from the HW.
372 (0xFC8). The value is taken directly from the HW.
379 (offset 0xFBC). The value is taken directly read
387 (0xFCC). The value is taken directly from the HW.
394 (0xFE0). The value is taken directly from the HW.
401 (0xFE4). The value is taken directly from the HW.
[all …]
|
| D | sysfs-bus-coresight-devices-etm3x | 259 (0x004). The value is read directly from the HW.
266 register (0x1e8). The value is read directly from the HW.
273 register (0x014). The value is read directly from the HW.
280 value is read directly from the HW.
287 The value is read directly from the HW.
294 The value is read directly from the HW.
301 (0x020). The value is read directly from the HW.
308 register (0x018). The value is read directly from the HW.
315 register (0x024). The value is read directly from the HW.
322 register (0x01c). The value is read directly from the HW.
|
| /Linux-v6.6/tools/testing/selftests/rseq/ |
| D | rseq-bits-template.h | 16 # error "Never use <rseq-bits-template.h> directly; include <rseq.h> instead."
26 # error "Never use <rseq-bits-template.h> directly; include <rseq.h> instead."
34 # error "Never use <rseq-bits-template.h> directly; include <rseq.h> instead."
37 # error "Never use <rseq-bits-template.h> directly; include <rseq.h> instead."
|
| /Linux-v6.6/include/uapi/linux/ |
| D | acrn.h | 189 * @vm_flag: Flag of the VM creating. Pass to hypervisor directly.
191 * hypervisor directly.
192 * @cpu_affinity: CPU affinity of the VM. Pass to hypervisor directly.
315 * This structure will be passed to hypervisor directly.
345 * Pass to hypervisor directly.
347 * Pass to hypervisor directly.
349 * Pass to hypervisor directly.
351 * Pass to hypervisor directly.
352 * @vma_base: VMA address of Service VM. Pass to hypervisor directly.
354 * Pass to hypervisor directly.
[all …]
|
| D | patchkey.h | 10 * Do not include this file directly. Please use <sys/soundcard.h> instead.
15 #error "patchkey.h included directly"
|
| /Linux-v6.6/tools/testing/selftests/bpf/prog_tests/ |
| D | atomics.c | 12 /* No need to attach it, just run it directly */ in test_add()
37 /* No need to attach it, just run it directly */ in test_sub()
62 /* No need to attach it, just run it directly */ in test_and()
84 /* No need to attach it, just run it directly */ in test_or()
106 /* No need to attach it, just run it directly */ in test_xor()
128 /* No need to attach it, just run it directly */ in test_cmpxchg()
150 /* No need to attach it, just run it directly */ in test_xchg()
|
| /Linux-v6.6/Documentation/RCU/ |
| D | UP.rst | 25 Now, if call_rcu() were to directly invoke its arguments, then upon return
37 by having call_rcu() directly invoke its arguments only if it was called
61 call_rcu() were to directly invoke the callback, the result would
81 If call_rcu() directly invokes the callback, painful locking restrictions
90 permit call_rcu() to directly invoke callbacks, but only if a full
140 callbacks acquire locks directly. However, a great many RCU
|
| /Linux-v6.6/drivers/staging/media/atomisp/pci/runtime/queue/src/ |
| D | queue.c | 91 /* Directly de-ref the object and in ia_css_queue_enqueue()
148 /* Directly de-ref the object and in ia_css_queue_dequeue()
203 /* Directly de-ref the object and in ia_css_queue_is_full()
235 /* Directly de-ref the object and in ia_css_queue_get_free_space()
267 /* Directly de-ref the object and in ia_css_queue_get_used_space()
300 /* Directly de-ref the object and in ia_css_queue_peek()
348 /* Directly de-ref the object and in ia_css_queue_is_empty()
380 /* Directly de-ref the object and in ia_css_queue_get_size()
|
| /Linux-v6.6/Documentation/core-api/ |
| D | memory-allocation.rst | 10 or you can directly request pages from the page allocator with
61 will be directly accessible by the kernel and implies that the
65 but it is not required to be directly accessible by the kernel. An
66 example may be a hardware allocation that maps data directly into
70 must be directly accessible by the kernel.
154 For large allocations you can use vmalloc() and vzalloc(), or directly
|
| /Linux-v6.6/rust/bindings/ |
| D | lib.rs | 7 //! This crate may not be directly used. If you need a kernel C API that is
37 // When both a directly exposed symbol and a helper exists for the same function,
38 // the directly exposed symbol is preferred and the helper becomes dead code, so
|
| /Linux-v6.6/arch/arm64/kvm/ |
| D | stacktrace.c | 7 * 1) Non-protected nVHE mode - the host can directly access the
12 * 2) pKVM (protected nVHE) mode - the host cannot directly access
173 * The host can directly access HYP stack pages in non-protected
174 * mode, so the unwinding is done directly from EL1. This removes
210 * host cannot directly access hypervisor memory in protected
|
| /Linux-v6.6/drivers/net/ethernet/wiznet/ |
| D | Kconfig | 13 Note that the answer to this question doesn't directly affect the
54 In direct address mode host system can directly access all registers
62 which are directly mapped to Memory-Mapped I/O space.
|
| /Linux-v6.6/include/media/ |
| D | videobuf2-v4l2.h | 116 * The return values from this function are intended to be directly returned
142 * The return values from this function are intended to be directly returned
154 * The return values from this function are intended to be directly returned
180 * The return values from this function are intended to be directly returned
198 * The return values from this function are intended to be directly returned
217 * The return values from this function are intended to be directly returned
290 * The return values from this function are intended to be directly returned
313 * below. Drivers can also use this function directly when they need to
|
| /Linux-v6.6/Documentation/userspace-api/media/mediactl/ |
| D | media-request-ioc-queue.rst | 47 It is not allowed to mix queuing requests with queuing buffers directly
49 queued directly and you next try to queue a request, or vice versa.
63 buffer directly, but later attempted to use a request. It is not permitted
|
| /Linux-v6.6/Documentation/fault-injection/ |
| D | provoke-crashes.rst | 11 trigger location, but can also trigger the kernel directly without KPROBE
36 These are numerous, and best queried directly from debugfs. Some
52 The special file `DIRECT` will induce the action directly without KPROBE
|
| /Linux-v6.6/include/linux/ |
| D | gfp_types.h | 24 /* Plain integer GFP bitmasks. Do not use this directly. */
189 * directly trigger the OOM killer, their failure indicates that
281 * Please try to avoid using this flag directly and instead use
287 * Please try to avoid using this flag directly and instead use
292 * %GFP_USER is for userspace allocations that also need to be directly
310 * do not need to be directly accessible by the kernel but that cannot
312 * data directly into userspace but has no addressing limitations.
|
| D | tty_driver.h | 97 * call this function directly, call tty_put_char().
104 * Optional. Do not call this function directly, call
118 * function directly, call tty_write_room()
127 * device. Do not call this function directly, call tty_chars_in_buffer().
234 * device. Do not call this function directly, call
260 * ioctl. Do not call this function directly, call tty_tiocmget().
269 * ioctl. Do not call this function directly, call tty_tiocmset().
296 * Do not call this function directly, call tty_tiocgserial().
304 * Do not call this function directly, call tty_tiocsserial().
313 * Do not call this function directly, call tty_show_fdinfo().
|
| /Linux-v6.6/Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 69 Will not use hda_jack but use snd_jack in spec->pcm_rec[pcm_idx].jack directly.
88 Use directly snd_jack_report() on spec->pcm_rec[pcm_idx].jack for
96 Use directly snd_jack_report() on spec->pcm_rec[pcm_idx].jack for dyn_pcm_assign.
|
| /Linux-v6.6/arch/arm/mm/ |
| D | dma.h | 12 * These are private to the dma-mapping API. Do not use directly.
23 * These are private to the dma-mapping API. Do not use directly.
|
| /Linux-v6.6/drivers/gpu/drm/bridge/cadence/ |
| D | Kconfig | 11 bridge and is meant to be directly embedded in a SoC.
33 bridge and is meant to be directly embedded in a SoC.
|
| /Linux-v6.6/Documentation/power/ |
| D | freezing-of-tasks.rst | 39 __refrigerator() must not be called directly. Instead, use the
98 directly is not allowed). From this point it is regarded as freezable
153 a kernel thread that belongs to a device driver accesses the device directly, it
198 they are not directly related to it. For example, if request_firmware() is
225 deemed necessary, it is strongly discouraged to directly call
237 summarize, use [un]lock_system_sleep() instead of directly using
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | syscall-user-dispatch.rst | 24 syscalls directly (disabled) or send them to be emulated in userspace
61 from which syscalls are always executed directly, regardless of the
72 thread-wide, without the need to invoke the kernel directly. selector
|
| /Linux-v6.6/Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 6 into vmlinux directly, to enable avoiding having to look for firmware from
8 directly. You can enable built-in firmware using the kernel configuration
|
