Searched full:directly (Results 1 – 25 of 3113) sorted by relevance
12345678910>>...125
| /Linux-v5.4/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 | 24 2. The value is read directly from HW register RDP, 0x004.
31 is read directly from HW register STS, 0x00C.
39 interface. The value is read directly from HW register RRP,
48 the CoreSight bus into the Trace RAM. The value is read directly
56 read directly from HW register TRG, 0x01C.
63 is read directly from HW register CTL, 0x020.
70 register. The value is read directly from HW register FFSR,
78 register. The value is read directly from HW register FFCR,
|
| D | sysfs-bus-coresight-devices-etm4x | 290 The value it taken directly from the HW.
297 (0x310). The value is taken directly from the HW.
304 (0x314). The value is taken directly from the HW.
311 (0xFB4). The value is taken directly from the HW.
318 (0xFB8). The value is taken directly from the HW.
325 (0xFC8). The value is taken directly from the HW.
332 (0xFCC). The value is taken directly from the HW.
339 (0xFE0). The value is taken directly from the HW.
346 (0xFE4). The value is taken directly from the HW.
353 (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.
|
| /Linux-v5.4/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.
106 :c:func:`vzalloc`, or directly request pages from the page
|
| /Linux-v5.4/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
|
| /Linux-v5.4/include/media/ |
| D | videobuf2-v4l2.h | 115 * The return values from this function are intended to be directly returned
141 * The return values from this function are intended to be directly returned
153 * The return values from this function are intended to be directly returned
179 * The return values from this function are intended to be directly returned
197 * The return values from this function are intended to be directly returned
216 * The return values from this function are intended to be directly returned
260 * The return values from this function are intended to be directly returned
|
| /Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/Documentation/media/v4l-drivers/ |
| 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
|
| /Linux-v5.4/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"
|
| /Linux-v5.4/Documentation/media/uapi/mediactl/ |
| D | media-request-ioc-queue.rst | 72 It is not allowed to mix queuing requests with queuing buffers directly
74 queued directly and you next try to queue a request, or vice versa.
88 buffer directly, but later attempted to use a request. It is not permitted
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | pnfs-scsi-server.txt | 8 also hands out layouts to the clients so that they can directly access the
14 addition to the MDS. As of now the file system needs to sit directly on the
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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 it is strongly discouraged to directly call mutex_[un]lock(&system_transition_mutex) since
236 So, to summarize, use [un]lock_system_sleep() instead of directly using
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/Documentation/fault-injection/ |
| D | provoke-crashes.rst | 8 crashing points, but can also crash the kernel directly without KRPOBE
46 A special file is `DIRECT` which will induce the crash directly without
|
| /Linux-v5.4/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
|
| /Linux-v5.4/arch/c6x/include/asm/ |
| D | irq.h | 8 * Large parts taken directly from powerpc.
30 * can each route a single SoC interrupt directly.
|
| /Linux-v5.4/fs/nfsd/ |
| D | Kconfig | 99 clients to directly perform I/O to block devices accesible to both
113 clients to directly perform I/O to SCSI devices accesible to both
126 enables NFS clients to directly perform I/O to NFSv3 devices
|
| /Linux-v5.4/Documentation/scsi/ |
| D | FlashPoint.txt | 100 it was best that these issues be addressed directly. I sent an email
109 FlashPoint drivers have been written directly by BusLogic Engineering, and
146 being able to work directly with their firmware engineer in demonstrating
154 directly via email, or have appeared in the Linux newsgroups in which I
|
| /Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm7038-l1-intc.txt | 4 directly to one of the HW INT lines on each CPU. Every BCM7xxx set-top chip
11 - Most onchip peripherals are wired directly to an L1 input
|
| /Linux-v5.4/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
|
| /Linux-v5.4/drivers/net/ethernet/netronome/ |
| D | Kconfig | 12 Note that the answer to this question doesn't directly affect the
38 either directly, with Open vSwitch, or any other way. Note that
|
12345678910>>...125
