| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| A D | fsl,mu-msi.yaml | 16 for one processor (A side) to signal the other processor (B side) using 23 registers (Processor A-side, Processor B-side). 45 - const: processor-a-side 46 - const: processor-b-side 49 description: a side interrupt number. 57 - description: a side power domain 58 - description: b side power domain 62 - const: processor-a-side 63 - const: processor-b-side 94 reg-names = "processor-a-side", "processor-b-side"; [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/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/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 57 This driver provides kernel-side support for the Random Number 70 This driver provides kernel-side support for the Random Number 82 This driver provides kernel-side support for the Random Number 94 This driver provides kernel-side support for the Random Number 107 This driver provides kernel-side support for the RNG200 121 This driver provides kernel-side support for the Random Number 134 This driver provides kernel-side support for the Random Number 147 This driver provides kernel-side support for the Random Number [all …]
|
| /linux/Documentation/devicetree/bindings/memory-controllers/ |
| A D | rockchip,rk3399-dmc.yaml | 132 the ODT on the DRAM side and controller side are both disabled. 138 When the DRAM type is DDR3, this parameter defines the DRAM side drive 146 When the DRAM type is DDR3, this parameter defines the DRAM side ODT 154 When the DRAM type is DDR3, this parameter defines the phy side CA line 162 When the DRAM type is DDR3, this parameter defines the PHY side DQ line 170 When the DRAM type is DDR3, this parameter defines the PHY side ODT 180 ODT on the DRAM side and controller side are both disabled. 194 When the DRAM type is LPDDR3, this parameter defines the DRAM side ODT 218 When dram type is LPDDR3, this parameter define the phy side odt 227 the ODT on the DRAM side and controller side are both disabled. [all …]
|
| /linux/Documentation/RCU/ |
| A D | lockdep.rst | 8 aware of when each task enters and leaves any flavor of RCU read-side 33 Check for RCU read-side critical section. 35 Check for RCU-bh read-side critical section. 37 Check for RCU-sched read-side critical section. 39 Check for SRCU read-side critical section. 83 1. An RCU read-side critical section (implicit), or 88 RCU read-side critical sections, in case (2) the ->file_lock prevents 99 complain even if this was used in an RCU read-side critical section unless 107 traversal primitives check for being called from within an RCU read-side 111 false and they are called from outside any RCU read-side critical section. [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. 63 under your read-side code, which can greatly increase the 72 spinlock also enters an RCU read-side critical section. 159 perfectly legal (if redundant) for update-side code to 164 of an RCU read-side critical section. See lockdep.rst 195 be traversed by an RCU read-side critical section. 343 locks. RCU read-side critical sections are delimited by 437 requiring SRCU's read-side deadlock immunity or low read-side 471 RCU update-side primitives to deal with this. [all …]
|
| A D | whatisRCU.rst | 500 read-side critical sections. 766 RCU read-side critical sections will have completed. 776 Give an example where Classic RCU's read-side 784 If it is illegal to block in an RCU read-side 850 Or, for those who prefer a side-by-side listing:: 906 However, there is one potential catch: the read-side and update-side 1241 read_acquire rcu_gp_mutex. Task A's RCU read-side 1252 Give an example where Classic RCU's read-side 1281 If it is illegal to block in an RCU read-side 1288 read-side critical sections. It also permits [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/ABI/testing/ |
| A D | sysfs-bus-iio-frequency-admv1013 | 18 side. 24 Read/write value for the Local Oscillatior Feedthrough Offset Calibration Q Positive side. 31 side. 38 side.
|
| /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/drivers/nvme/target/ |
| A D | Kconfig | 11 This enabled target side support for the NVMe protocol, that is 34 This enables target side NVMe passthru controller support for the 37 side, including executing Vendor Unique Commands. 48 to test NVMe host and target side features. 110 bool "NVMe over Fabrics In-band Authentication in target side" 115 target side.
|
| /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/tools/include/uapi/ |
| A D | README | 47 was pushed back on from the kernel side, when tooling modified the 52 notification mechanism to look at new kernel side changes. 57 tooling, driven by non-fatal warnings on the tooling side build when 66 The tooling policy is to always pick up the kernel side headers as-is, 69 side.
|
| /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/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 171 implements the BMC side of the BT interface. 178 management (BMC) side. 180 The driver implements the BMC side of the SMBus system
|
| /linux/include/uapi/linux/netfilter/ |
| A D | xt_recent.h | 34 __u8 side; member 43 __u8 side; member
|
| /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 88 5 - Tx doorbell channel. With S/W ACK from the other side. 94 fsl,mu-side-b: 95 description: boolean, if present, means it is for side B MU.
|
| /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/Documentation/devicetree/bindings/soc/qcom/ |
| A D | qcom,aoss-qmp.yaml | 7 title: Qualcomm Always-On Subsystem side channel 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 81 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/networking/ |
| A D | tc-queue-filters.rst | 8 to a single queue on both the transmit and receive side. 10 On the transmit side: 22 Likewise, on the receive side, the two filters for selecting set of
|
| /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/sound/pci/hda/ |
| A D | Kconfig | 104 This builds KUnit tests for the cirrus side-codec library. 123 tristate "Build CS35L41 HD-audio side codec support for I2C Bus" 133 Say Y or M here to include CS35L41 I2C HD-audio side codec support 136 comment "Set to Y if you want auto-loading the side codec driver" 150 Say Y or M here to include CS35L41 SPI HD-audio side codec support 153 comment "Set to Y if you want auto-loading the side codec driver" 160 tristate "Build CS35L56 HD-audio side codec support for I2C Bus" 177 tristate "Build CS35L56 HD-audio side codec support for SPI Bus" 194 tristate "Build TAS2781 HD-audio side codec support for I2C Bus" 203 Say Y or M here to include TAS2781 I2C HD-audio side codec support [all …]
|