/linux/Documentation/devicetree/bindings/devfreq/ |
A D | rk3399_dmc.txt | 77 the ODT on the DRAM side and controller side are 81 the DRAM side driver strength in ohms. Default 89 the phy side CA line (incluing command line, 94 the PHY side DQ line (including DQS/DQ/DM line) 103 the ODT on the DRAM side and controller side are 107 the DRAM side driver strength in ohms. Default 115 the PHY side CA line (including command line, 130 controller side are both disabled. 133 the DRAM side driver strength in ohms. Default 141 the DRAM side ODT on CA line strength in ohms. [all …]
|
/linux/Documentation/locking/ |
A 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 76 /* ... [[write-side critical section]] ... */ 85 /* ... [[read-side critical section]] ... */ 99 side critical sections are properly serialized. 108 protection is enforced in the write side function. 154 side can be invoked from NMI handlers. 189 /* ... [[write-side critical section]] ... */ 202 /* ... [[read-side critical section]] ... */ 213 /* ... [[read-side critical section]] ... */ [all …]
|
/linux/drivers/char/hw_random/ |
A 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/Documentation/usb/ |
A 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 111 side kernel for "Support for USB Gadgets", for a "USB Peripheral 152 instructions below to install the host side driver. 220 Linux host side kernel for "Support for Host-side USB", for "USB 263 On the gadget side run "minicom -s" to configure a new minicom 287 side and host side systems. Anything you type on the terminal [all …]
|
/linux/Documentation/RCU/ |
A 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 …]
|
A D | whatisRCU.rst | 463 read-side critical sections. 722 RCU read-side critical sections will have completed. 732 Give an example where Classic RCU's read-side 740 If it is illegal to block in an RCU read-side 806 Or, for those who prefer a side-by-side listing:: 862 However, there is one potential catch: the read-side and update-side 1081 read_acquire rcu_gp_mutex. Task A's RCU read-side 1092 Give an example where Classic RCU's read-side 1121 If it is illegal to block in an RCU read-side 1128 read-side critical sections. It also permits [all …]
|
A D | checklist.rst | 18 tool for the job. Yes, RCU does reduce read-side overhead by 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 149 perfectly legal (if redundant) for update-side code to 154 of an RCU read-side critical section. See lockdep.txt 185 be traversed by an RCU read-side critical section. 316 locks. RCU read-side critical sections are delimited by 399 requiring SRCU's read-side deadlock immunity or low read-side 427 RCU update-side primitives to deal with this. [all …]
|
A 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/drivers/block/rnbd/ |
A 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/Documentation/RCU/Design/Requirements/ |
A 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 370 outermost RCU read-side critical section containing that 429 update-side lock. 698 Reader-side markers such as rcu_read_lock() and 1077 b. Wait-free read-side primitives for real-time use. 1194 unsurprising. For example, in keeping with RCU's read-side 1564 small read-side delays can occur when using 1590 critical section. Update-side code can use 1749 set up. The read-side primitives (rcu_read_lock(), [all …]
|
/linux/Documentation/litmus-tests/rcu/ |
A 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/Documentation/driver-api/ |
A 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
|
/linux/drivers/nvme/target/ |
A 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/Documentation/devicetree/bindings/mailbox/ |
A D | fsl,mu.yaml | 19 different clocks (from each side of the different peripheral buses). 20 Therefore, the MU must synchronize the accesses from one side to the 76 fsl,mu-side-b: 77 description: boolean, if present, means it is for side B MU.
|
/linux/Documentation/devicetree/bindings/soc/qcom/ |
A D | qcom,aoss-qmp.yaml | 7 title: Qualcomm Always-On Subsystem side channel binding 13 This binding describes the hardware component responsible for side channel 20 The AOSS side channel exposes control over a set of resources, used to control 73 The AOSS side channel also provides the controls for three cooling devices,
|
/linux/Documentation/devicetree/bindings/media/ |
A D | video-interface-devices.yaml | 316 A camera installed on the back side of a mobile device facing away from 321 The camera sensor is typically mounted with its pixel array longer side 322 aligned to the device longer side, upside-down mounted to compensate for 393 # Front. The device is mounted on the front facing side of the system. For 394 # mobile devices such as smartphones, tablets and laptops the front side 395 # is the user facing side. 397 # Back. The device is mounted on the back side of the system, which is 398 # defined as the opposite side of the front facing one.
|
/linux/Documentation/staging/ |
A 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/include/uapi/linux/netfilter/ |
A D | xt_recent.h | 34 __u8 side; member 43 __u8 side; member
|
/linux/drivers/infiniband/ulp/rtrs/ |
A 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/drivers/char/ipmi/ |
A D | Kconfig | 118 The driver implements the BMC side of the KCS contorller, it 119 provides the access of KCS IO space for BMC side. 130 The driver implements the BMC side of the KCS contorller, it 131 provides the access of KCS IO space for BMC side. 140 Provides a BMC-side character device implementing IPMI 170 implements the BMC side of the BT interface.
|
/linux/drivers/usb/usbip/ |
A 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/drivers/tty/serial/ |
A 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()
|
A 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/drivers/block/ |
A D | swim.c | 31 unsigned char side; member 458 int side, int track, in swim_read_sector() argument 470 swim_head(base, side); in swim_read_sector() 471 swim_write(base, mode0, side); in swim_read_sector() 487 if ((header.side != side) || (header.track != track) || in swim_read_sector() 500 int side, track, sector; in floppy_read_sectors() local 509 side = x / fs->secpertrack; in floppy_read_sectors() 514 ret = swim_read_sector(fs, side, track, sector, in floppy_read_sectors()
|
/linux/drivers/crypto/allwinner/ |
A 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
|