| /Linux-v5.15/Documentation/devicetree/bindings/devfreq/ |
| D | rk3399_dmc.txt | 77 the ODT on the DRAM side and controller side are
81 the DRAM side driver strength in ohms. Default
85 the DRAM side ODT strength in ohms. Default value
89 the phy side CA line (incluing command line,
94 the PHY side DQ line (including DQS/DQ/DM line)
98 the PHY side ODT strength. Default value is 240.
103 the ODT on the DRAM side and controller side are
107 the DRAM side driver strength in ohms. Default
111 the DRAM side ODT strength in ohms. Default value
115 the PHY side CA line (including command line,
[all …]
|
| /Linux-v5.15/Documentation/locking/ |
| D | seqlock.rst | 15 read side critical section is even and the same sequence count value is
17 be copied out inside the read side critical section. If the sequence
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
28 or interrupted by read side sections. Otherwise the reader will spin for
43 multiple writers. Write side critical sections must thus be serialized
48 write side section. If the read section can be invoked from hardirq or
76 /* ... [[write-side critical section]] ... */
85 /* ... [[read-side critical section]] ... */
95 As discussed at :ref:`seqcount_t`, sequence count write side critical
[all …]
|
| /Linux-v5.15/drivers/char/hw_random/ |
| D | Kconfig | 28 This driver provides kernel-side support for a generic Random
43 This driver provides kernel-side support for the Random Number
56 This driver provides kernel-side support for the Random Number
69 This driver provides kernel-side support for the Random Number
81 This driver provides kernel-side support for the Random Number
93 This driver provides kernel-side support for the Random Number
106 This driver provides kernel-side support for the RNG200
119 This driver provides kernel-side support for the Random Number
132 This driver provides kernel-side support for the Random Number
145 This driver provides kernel-side support for the Random Number
[all …]
|
| /Linux-v5.15/Documentation/usb/ |
| D | gadget_serial.rst | 57 side driver. It runs on a Linux system that has USB device side
84 On the device-side Linux system, the gadget serial driver looks
87 On the host-side system, the gadget serial device looks like a
92 The host side driver can potentially be any ACM compliant driver
98 With the gadget serial driver and the host side ACM or generic
100 the host and the gadget side systems as if they were connected by a
111 side kernel for "Support for USB Gadgets", for a "USB Peripheral
128 side Linux system. You can add this to the start up scripts, if
149 either the Windows or Linux ACM driver on the host side. If gadget
151 Linux generic serial driver on the host side. Follow the appropriate
[all …]
|
| /Linux-v5.15/Documentation/RCU/ |
| D | lockdep.rst | 8 aware of when each task enters and leaves any flavor of RCU read-side
31 Check for RCU read-side critical section.
33 Check for RCU-bh read-side critical section.
35 Check for RCU-sched read-side critical section.
37 Check for SRCU read-side critical section.
80 1. An RCU read-side critical section (implicit), or
85 RCU read-side critical sections, in case (2) the ->file_lock prevents
96 complain if this was used in an RCU read-side critical section unless one
104 traversal primitives check for being called from within an RCU read-side
108 false and they are called from outside any RCU read-side critical section.
[all …]
|
| D | whatisRCU.rst | 94 b. Wait for all previous readers to complete their RCU read-side
157 entering an RCU read-side critical section. It is illegal
158 to block while in an RCU read-side critical section, though
160 read-side critical sections. Any RCU-protected data structure
161 accessed during an RCU read-side critical section is guaranteed to
171 exiting an RCU read-side critical section. Note that RCU
172 read-side critical sections may be nested and/or overlapping.
180 read-side critical sections on all CPUs have completed.
182 any subsequent RCU read-side critical sections to complete.
195 read-side critical sections to complete, not necessarily for
[all …]
|
| D | checklist.rst | 18 tool for the job. Yes, RCU does reduce read-side overhead by
19 increasing write-side overhead, which is exactly why normal uses
28 read-side primitives is critically important.
59 2. Do the RCU read-side critical sections make proper use of
63 under your read-side code, which can greatly increase the
68 rcu_read_lock_sched(), or by the appropriate update-side lock.
72 Letting RCU-protected pointers "leak" out of an RCU read-side
76 *before* letting them out of the RCU read-side critical section.
149 perfectly legal (if redundant) for update-side code to
154 of an RCU read-side critical section. See lockdep.txt
[all …]
|
| D | lockdep-splat.rst | 15 RCU read-side critical section or (2) holding the right update-side lock.
72 This form says that it must be in a plain vanilla RCU read-side critical
84 code was invoked either from within an RCU read-side critical section
89 On the other hand, perhaps we really do need an RCU read-side critical
104 read-side critical section, which again would have suppressed the
|
| /Linux-v5.15/drivers/block/rnbd/ |
| D | README | 12 on the client side as local block devices.
26 Server side:
29 Client side:
39 mapped from the server side. After the session to the server machine is
40 established, the mapped device will appear on the client side under
51 to the block device on the server side by concatenating dev_search_path
73 information: side, max_hw_sectors, etc.
|
| /Linux-v5.15/Documentation/litmus-tests/rcu/ |
| D | RCU+sync+read.litmus | 7 * sees all stores done in prior RCU read-side critical sections. Such
8 * read-side critical sections would have ended before the grace period ended.
11 * other things) that an RCU read-side critical section cannot span a grace period.
|
| /Linux-v5.15/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 20 updaters do not block readers, which means that RCU's read-side
74 of all pre-existing RCU read-side critical sections. An RCU read-side
77 RCU treats a nested set as one big RCU read-side critical section.
131 | Second, even when using synchronize_rcu(), the other update-side |
173 The RCU read-side critical section in do_something_dlm() works with
190 In order to avoid fatal problems such as deadlocks, an RCU read-side
192 Similarly, an RCU read-side critical section must not contain anything
198 be good to be able to use RCU to coordinate read-side access to linked
370 outermost RCU read-side critical section containing that
387 #. Wait for all pre-existing RCU read-side critical sections to complete
[all …]
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | io-mapping.rst | 49 io_mapping_map_local_wc() has a side effect on X86 32bit as it disables
50 migration to make the mapping code work. No caller can rely on this side
53 io_mapping_map_atomic_wc() has the side effect of disabling preemption and
72 undoes the side effects of the mapping functions.
80 This works like io_mapping_map_atomic/local_wc() except it has no side
|
| D | spi.rst | 18 only "master" side interfaces are supported, where Linux talks to SPI
25 a pair of FIFOs connected to dual DMA engines on the other side of the
28 the SPI side of their device as a :c:type:`struct spi_master
|
| /Linux-v5.15/drivers/nvme/target/ |
| D | Kconfig | 10 This enabled target side support for the NVMe protocol, that is
24 This enables target side NVMe passthru controller support for the
27 side, including executing Vendor Unique Commands.
38 to test NVMe host and target side features.
|
| /Linux-v5.15/include/uapi/linux/netfilter/ |
| D | xt_recent.h | 34 __u8 side; member
43 __u8 side; member
|
| /Linux-v5.15/Documentation/staging/ |
| D | speculation.rst | 17 absence of data in caches. Such state may form side-channels which can be
67 Mitigating speculation side-channels
72 speculation-based side-channels are expected to implement these
76 prevent information from being leaked via side-channels.
|
| /Linux-v5.15/drivers/char/ipmi/ |
| D | Kconfig | 109 The driver implements the BMC side of the KCS contorller, it
110 provides the access of KCS IO space for BMC side.
121 The driver implements the BMC side of the KCS contorller, it
122 provides the access of KCS IO space for BMC side.
131 Provides a BMC-side character device implementing IPMI
161 implements the BMC side of the BT interface.
|
| /Linux-v5.15/drivers/infiniband/ulp/rtrs/ |
| D | README | 11 possibility to either write data from an sg list to the remote side
12 or to request ("read") data transfer from the remote side into a given
29 server side for a given client for rdma transfer. A session
36 chunks reserved for him on the server side. Their number, size and addresses
49 discussed in LPC RDMA MC 2019. When always_invalidate=Y, on the server side we
97 side or network outage in an absence of IO.
123 on the server side and rdma writes there the user data, user header and the
140 on the server side and rdma writes there the user data, user header and the
163 on the server side and rdma writes there the user header and the
182 on the server side and rdma writes there the user header and the
|
| /Linux-v5.15/drivers/usb/usbip/ |
| D | usbip_common.c | 601 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_iso()
623 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_iso()
685 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) { in usbip_recv_xbuff()
742 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_xbuff()
|
| /Linux-v5.15/Documentation/ABI/stable/ |
| D | sysfs-driver-aspeed-vuart | 4 Description: Configures which IO port the host side of the UART
12 Description: Configures which interrupt number the host side of
|
| /Linux-v5.15/drivers/block/ |
| D | swim.c | 30 unsigned char side; member
456 int side, int track, in swim_read_sector() argument
468 swim_head(base, side); in swim_read_sector()
469 swim_write(base, mode0, side); in swim_read_sector()
485 if ((header.side != side) || (header.track != track) || in swim_read_sector()
498 int side, track, sector; in floppy_read_sectors() local
507 side = x / fs->secpertrack; in floppy_read_sectors()
512 ret = swim_read_sector(fs, side, track, sector, in floppy_read_sectors()
|
| /Linux-v5.15/drivers/tty/serial/ |
| D | sb1250-duart.c | 772 int chip, side; in sbd_probe_duarts() local
796 for (side = 0; side < DUART_MAX_SIDE && line < max_lines; in sbd_probe_duarts()
797 side++, line++) { in sbd_probe_duarts()
798 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_probe_duarts()
835 int side = co->index % DUART_MAX_SIDE; in sbd_console_write() local
836 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_console_write()
863 int side = co->index % DUART_MAX_SIDE; in sbd_console_setup() local
864 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_console_setup()
|
| D | zs.c | 1072 int chip, side, irq; in zs_probe_sccs() local
1098 for (side = 0; side < ZS_NUM_CHAN; side++) { in zs_probe_sccs()
1099 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_probe_sccs()
1112 uport->line = chip * ZS_NUM_CHAN + side; in zs_probe_sccs()
1115 (side ^ ZS_CHAN_B) * ZS_CHAN_IO_SIZE; in zs_probe_sccs()
1148 int chip = co->index / ZS_NUM_CHAN, side = co->index % ZS_NUM_CHAN; in zs_console_write() local
1149 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_console_write()
1198 int chip = co->index / ZS_NUM_CHAN, side = co->index % ZS_NUM_CHAN; in zs_console_setup() local
1199 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_console_setup()
|
| /Linux-v5.15/drivers/crypto/allwinner/ |
| D | Kconfig | 32 Select this option if you want to provide kernel-side support for
86 Select this option if you want to provide kernel-side support for
94 Select this option if you want to provide kernel-side support for
129 Select this option if you want to provide kernel-side support for
|
| /Linux-v5.15/Documentation/hid/ |
| D | intel-ish-hid.rst | 132 client firmware side. When ISH interrupt handler is called, the ISH2HOST
136 Each side has 32 32-bit message registers and a 32-bit doorbell. Doorbell
142 Bit 31: doorbell trigger (signal H/W interrupt to the other side)
181 Either side can send disconnect request bus message to end communication. Also
191 Each side (host and FW) manages its DMA transfer memory independently. When an
192 ISHTP client from either host or FW side wants to send something, it decides
194 independent. The sending side sends DMA_XFER message when the message is in
212 the receiving side, DMA_XFER_ACK returns ownership to the sender. A sender
229 to send. Same thing holds true on receive side and flow control is required.
|
