Searched full:directly (Results 1 – 25 of 3427) sorted by relevance
12345678910>>...138
| /kernel/linux/linux-5.10/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 (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 …]
|
| 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.
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/runtime/queue/src/ |
| D | queue.c | 98 /* 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/ |
| 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.
150 For large allocations you can use vmalloc() and vzalloc(), or directly
|
| /kernel/linux/linux-5.10/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
80 If call_rcu() directly invokes the callback, painful locking restrictions
131 callbacks acquire locks directly. However, a great many RCU
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/drivers/thunderbolt/ |
| D | nvm.c | 49 * @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-5.10/Documentation/fault-injection/ |
| D | provoke-crashes.rst | 11 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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/include/media/ |
| D | videobuf2-v4l2.h | 122 * The return values from this function are intended to be directly returned
148 * The return values from this function are intended to be directly returned
160 * The return values from this function are intended to be directly returned
186 * The return values from this function are intended to be directly returned
204 * The return values from this function are intended to be directly returned
223 * The return values from this function are intended to be directly returned
280 * The return values from this function are intended to be directly returned
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | patchkey.h | 10 * Do not include this file directly. Please use <sys/soundcard.h> instead.
15 #error "patchkey.h included directly"
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | imx7.rst | 54 The CSI enables the chip to connect directly to external CMOS image sensor. CSI
55 can interface directly with Parallel and MIPI CSI-2 buses. It has 256 x 64 FIFO
60 source pad that routes video frames directly to memory buffers. This pad is
69 can be accessed either directly from the subdev or from the active capture
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/nfs/ |
| D | pnfs-scsi-server.rst | 9 also hands out layouts to the clients so that they can directly access the
15 addition to the MDS. As of now the file system needs to sit directly on the
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/adc/ |
| D | mt6577_auxadc.txt | 6 in the SoC. It can be used directly with register accesses, but it is also
8 directly via its own bus interface. See
|
| /kernel/linux/linux-5.10/arch/c6x/include/asm/ |
| D | irq.h | 8 * Large parts taken directly from powerpc.
30 * can each route a single SoC interrupt directly.
|
| /kernel/linux/linux-5.10/drivers/pnp/pnpbios/ |
| D | Kconfig | 31 able to directly access the PNPBIOS. This includes resource
34 not be notified of any resource changes made by writing directly.
|
| /kernel/linux/linux-5.10/fs/nfsd/ |
| D | Kconfig | 101 clients to directly perform I/O to block devices accesible to both
115 clients to directly perform I/O to SCSI devices accesible to both
128 enables NFS clients to directly perform I/O to NFSv3 devices
|
| /kernel/linux/linux-5.10/fs/romfs/ |
| D | Kconfig | 43 This permits ROMFS to use MTD based devices directly, without the
46 NOMMU conditions if the underlying device is directly addressable by
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | iopoll.h | 34 * macros defined below rather than this macro directly.
77 * macros defined below rather than this macro directly.
118 * macros defined below rather than this macro directly.
138 * macros defined below rather than this macro directly.
|
12345678910>>...138