Home
last modified time | relevance | path

Searched full:directly (Results 1 – 25 of 6264) sorted by relevance

12345678910>>...251

/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-tmc15 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,
Dsysfs-bus-coresight-devices-etb1027 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,
Dsysfs-bus-coresight-devices-etm4x337 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 (0xFCC). The value is taken directly from the HW.
386 (0xFE0). The value is taken directly from the HW.
393 (0xFE4). The value is taken directly from the HW.
400 (0xFE8). The value is taken directly from the HW.
[all …]
Dsysfs-bus-coresight-devices-etm3x259 (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.
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-tmc15 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,
Dsysfs-bus-coresight-devices-etb1027 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,
Dsysfs-bus-coresight-devices-etm4x337 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 …]
Dsysfs-bus-coresight-devices-etm3x259 (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.
/kernel/linux/linux-6.6/tools/testing/selftests/rseq/
Drseq-bits-template.h16 # 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."
/kernel/linux/linux-6.6/include/uapi/linux/
Dacrn.h189 * @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 …]
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/prog_tests/
Datomics.c12 /* 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()
/kernel/linux/linux-6.6/Documentation/RCU/
DUP.rst25 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
/kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/runtime/queue/src/
Dqueue.c91 /* 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()
/kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/runtime/queue/src/
Dqueue.c98 /* Directly de-ref the object and in ia_css_queue_enqueue()
157 /* Directly de-ref the object and in ia_css_queue_dequeue()
214 /* Directly de-ref the object and in ia_css_queue_is_full()
248 /* Directly de-ref the object and in ia_css_queue_get_free_space()
282 /* Directly de-ref the object and in ia_css_queue_get_used_space()
318 /* Directly de-ref the object and in ia_css_queue_peek()
368 /* Directly de-ref the object and in ia_css_queue_is_empty()
402 /* Directly de-ref the object and in ia_css_queue_get_size()
/kernel/linux/linux-5.10/Documentation/core-api/
Dmemory-allocation.rst10 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.
150 For large allocations you can use vmalloc() and vzalloc(), or directly
/kernel/linux/linux-6.6/Documentation/core-api/
Dmemory-allocation.rst10 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
/kernel/linux/linux-6.6/rust/bindings/
Dlib.rs7 //! 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
/kernel/linux/linux-5.10/Documentation/RCU/
DUP.rst25 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
80 If call_rcu() directly invokes the callback, painful locking restrictions
131 callbacks acquire locks directly. However, a great many RCU
/kernel/linux/linux-6.6/arch/arm64/kvm/
Dstacktrace.c7 * 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
/kernel/linux/linux-6.6/drivers/net/ethernet/wiznet/
DKconfig13 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.
/kernel/linux/linux-5.10/drivers/net/ethernet/wiznet/
DKconfig13 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.
/kernel/linux/linux-6.6/include/media/
Dvideobuf2-v4l2.h116 * 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
/kernel/linux/linux-5.10/drivers/thunderbolt/
Dnvm.c49 * @reg_read: Pointer to the function to read the NVM (passed directly to the
53 * directly from NVMem so it must handle possible concurrent access if
113 * @reg_write: Pointer to the function to write the NVM (passed directly
117 * directly from NVMem so it must handle possible concurrent access if
/kernel/linux/linux-6.6/Documentation/userspace-api/media/mediactl/
Dmedia-request-ioc-queue.rst47 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
/kernel/linux/linux-5.10/Documentation/fault-injection/
Dprovoke-crashes.rst11 trigger location, but can also trigger the kernel directly without KPROBE
37 These are numerous, and best queried directly from debugfs. Some
53 The special file `DIRECT` will induce the action directly without KPROBE

12345678910>>...251