Home
last modified time | relevance | path

Searched refs:side (Results 1 – 25 of 393) sorted by relevance

12345678910>>...16

/Linux-v5.4/Documentation/devicetree/bindings/devfreq/
Drk3399_dmc.txt73 the ODT on the DRAM side and controller side are
77 the DRAM side driver strength in ohms. Default
81 the DRAM side ODT strength in ohms. Default value
85 the phy side CA line (incluing command line,
90 the PHY side DQ line (including DQS/DQ/DM line)
94 the PHY side ODT strength. Default value is
100 the ODT on the DRAM side and controller side are
104 the DRAM side driver strength in ohms. Default
108 the DRAM side ODT strength in ohms. Default value
112 the PHY side CA line (including command line,
[all …]
/Linux-v5.4/drivers/char/hw_random/
DKconfig28 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
83 This driver provides kernel-side support for the Random Number
96 This driver provides kernel-side support for the RNG200
109 This driver provides kernel-side support for the Random Number
122 This driver provides kernel-side support for the Random Number
135 This driver provides kernel-side support for the Random Number
148 This driver provides kernel-side support for the Pseudo-Random
[all …]
/Linux-v5.4/Documentation/usb/
Dgadget_serial.rst57 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.4/Documentation/RCU/
Dlockdep.txt4 aware of when each task enters and leaves any flavor of RCU read-side
27 Check for RCU read-side critical section.
29 Check for RCU-bh read-side critical section.
31 Check for RCU-sched read-side critical section.
33 Check for SRCU read-side critical section.
76 1. An RCU read-side critical section (implicit), or
81 RCU read-side critical sections, in case (2) the ->file_lock prevents
92 complain if this was used in an RCU read-side critical section unless one
101 being in an RCU read-side critical section. In the future, separate
Dchecklist.txt14 tool for the job. Yes, RCU does reduce read-side overhead by
15 increasing write-side overhead, which is exactly why normal uses
24 read-side primitives is critically important.
55 2. Do the RCU read-side critical sections make proper use of
59 under your read-side code, which can greatly increase the
64 rcu_read_lock_sched(), or by the appropriate update-side lock.
68 Letting RCU-protected pointers "leak" out of an RCU read-side
72 -before- letting them out of the RCU read-side critical section.
147 perfectly legal (if redundant) for update-side code to
152 of an RCU read-side critical section. See lockdep.txt
[all …]
DwhatisRCU.txt82 b. Wait for all previous readers to complete their RCU read-side
143 entering an RCU read-side critical section. It is illegal
144 to block while in an RCU read-side critical section, though
146 read-side critical sections. Any RCU-protected data structure
147 accessed during an RCU read-side critical section is guaranteed to
157 exiting an RCU read-side critical section. Note that RCU
158 read-side critical sections may be nested and/or overlapping.
166 read-side critical sections on all CPUs have completed.
168 any subsequent RCU read-side critical sections to complete.
181 read-side critical sections to complete, not necessarily for
[all …]
Dlockdep-splat.txt9 RCU read-side critical section or (2) holding the right update-side lock.
67 This form says that it must be in a plain vanilla RCU read-side critical
79 code was invoked either from within an RCU read-side critical section
84 On the other hand, perhaps we really do need an RCU read-side critical
99 read-side critical section, which again would have suppressed the
/Linux-v5.4/Documentation/devicetree/bindings/soc/qcom/
Dqcom,aoss-qmp.txt1 Qualcomm Always-On Subsystem side channel binding
3 This binding describes the hardware component responsible for side channel
10 The AOSS side channel exposes control over a set of resources, used to control
55 The AOSS side channel also provides the controls for three cooling devices,
66 The following example represents the AOSS side-channel message RAM and the
/Linux-v5.4/Documentation/devicetree/bindings/mailbox/
Dfsl,mu.txt10 different clocks (from each side of the different peripheral buses).
11 Therefore, the MU must synchronize the accesses from one side to the
45 - fsl,mu-side-b : Should be set for side B MU.
/Linux-v5.4/include/uapi/linux/netfilter/
Dxt_recent.h34 __u8 side; member
43 __u8 side; member
/Linux-v5.4/Documentation/
Dspeculation.txt15 absence of data in caches. Such state may form side-channels which can be
65 Mitigating speculation side-channels
70 speculation-based side-channels are expected to implement these
74 prevent information from being leaked via side-channels.
/Linux-v5.4/Documentation/ABI/stable/
Dsysfs-driver-aspeed-vuart4 Description: Configures which IO port the host side of the UART
12 Description: Configures which interrupt number the host side of
/Linux-v5.4/drivers/usb/usbip/
Dusbip_common.c606 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_iso()
628 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_iso()
690 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) { in usbip_recv_xbuff()
744 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_xbuff()
/Linux-v5.4/drivers/char/ipmi/
DKconfig109 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.
134 implements the BMC side of the BT interface.
/Linux-v5.4/drivers/block/
Dswim.c30 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.4/drivers/tty/serial/
Dsb1250-duart.c777 int chip, side; in sbd_probe_duarts() local
801 for (side = 0; side < DUART_MAX_SIDE && line < max_lines; in sbd_probe_duarts()
802 side++, line++) { in sbd_probe_duarts()
803 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_probe_duarts()
839 int side = co->index % DUART_MAX_SIDE; in sbd_console_write() local
840 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_console_write()
867 int side = co->index % DUART_MAX_SIDE; in sbd_console_setup() local
868 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_console_setup()
Dzs.c1076 int chip, side, irq; in zs_probe_sccs() local
1102 for (side = 0; side < ZS_NUM_CHAN; side++) { in zs_probe_sccs()
1103 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_probe_sccs()
1115 uport->line = chip * ZS_NUM_CHAN + side; in zs_probe_sccs()
1118 (side ^ ZS_CHAN_B) * ZS_CHAN_IO_SIZE; in zs_probe_sccs()
1151 int chip = co->index / ZS_NUM_CHAN, side = co->index % ZS_NUM_CHAN; in zs_console_write() local
1152 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_console_write()
1201 int chip = co->index / ZS_NUM_CHAN, side = co->index % ZS_NUM_CHAN; in zs_console_setup() local
1202 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_console_setup()
/Linux-v5.4/Documentation/hwmon/
Dina2xx.rst61 The INA219 is a high-side current shunt and power monitor with an I2C
65 The INA220 is a high or low side current shunt and power monitor with an I2C
71 INA230 and INA231 are high or low side current shunt and power monitors
Dina3221.rst22 side of up to three D.C. power supplies. The INA3221 monitors both shunt drop
24 and power are calculated host-side from these.
/Linux-v5.4/Documentation/driver-api/
Dspi.rst18 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.4/Documentation/hid/
Dintel-ish-hid.rst132 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
141 Bit 31: doorbell trigger (signal H/W interrupt to the other side)
180 Either side can send disconnect request bus message to end communication. Also
190 Each side (host and FW) manages its DMA transfer memory independently. When an
191 ISHTP client from either host or FW side wants to send something, it decides
193 independent. The sending side sends DMA_XFER message when the message is in
211 the receiving side, DMA_XFER_ACK returns ownership to the sender. A sender
228 to send. Same thing holds true on receive side and flow control is required.
/Linux-v5.4/Documentation/media/v4l-drivers/
Dsi476x.rst132 0x09 injside 0 - Low-side injection is being used
133 1 - High-side injection is used
143 0x18 lassi Signed Low side adjacent Channel
145 0x19 hassi ditto fpr High side
Dmax2175.rst26 The high-side/low-side (HSLS) control of the tuner for a given band.
/Linux-v5.4/Documentation/devicetree/bindings/regulator/
Dmax8997-regulator.txt43 - max8997,pmic-ignore-gpiodvs-side-effect: When GPIO-DVS mode is used for
45 that of another buck, which is the side effect of the change (set_voltage).
46 Use this property to ignore such side effects and change the voltage.
100 max8997,pmic-ignore-gpiodvs-side-effect;
/Linux-v5.4/Documentation/driver-api/usb/
Dgadget.rst29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
34 side drivers).
44 Linux "USB device drivers", which are host side proxies for the real USB
50 The gadget API resembles the host side Linux-USB API in that both use
55 host side's current URB framework exposes a number of implementation
58 necessarily different (one side is a hardware-neutral master, the other
60 be usable for an overhead-reduced host side API.
152 side stack, with ``usbcore``, one or more *Host Controller Drivers*
156 That helps the host and device side USB controllers implement the two
[all …]

12345678910>>...16