| /linux/sound/hda/codecs/side-codecs/ |
| H A D | Kconfig | 5 tristate "KUnit test for Cirrus side-codec library" if !KUNIT_ALL_TESTS
9 This builds KUnit tests for the cirrus side-codec library.
25 tristate "Build CS35L41 HD-audio side codec support for I2C Bus"
34 Say Y or M here to include CS35L41 I2C HD-audio side codec support
37 comment "Set to Y if you want auto-loading the side codec driver"
50 Say Y or M here to include CS35L41 SPI HD-audio side codec support
53 comment "Set to Y if you want auto-loading the side codec driver"
60 tristate "Build CS35L56 HD-audio side codec support for I2C Bus"
76 tristate "Build CS35L56 HD-audio side codec support for SPI Bus"
111 tristate "Build TAS2781 HD-audio side code
[all...] |
| /linux/Documentation/usb/ |
| H 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
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/drivers/block/rnbd/ |
| H 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/ |
| H 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/RCU/ |
| H A 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 raw spinlock also enters an RCU read-side critical section.
76 respectively, as the RCU read-side critical section. Use of
84 Letting RCU-protected pointers "leak" out of an RCU read-side
88 *before* letting them out of the RCU read-side critical section.
[all …]
|
| H A D | whatisRCU.rst | 106 b. Wait for all previous readers to complete their RCU read-side
169 reclaimer that the reader is entering an RCU read-side critical
170 section. It is illegal to block while in an RCU read-side
172 can preempt RCU read-side critical sections. Any RCU-protected
173 data structure accessed during an RCU read-side critical section
179 or interrupts also enters an RCU read-side critical section.
180 Acquiring a spinlock also enters an RCU read-side critical
183 Sleeplocks do *not* enter RCU read-side critical sections.
190 reclaimer that the reader is exiting an RCU read-side critical
192 or interrupts also exits an RCU read-side critical section.
[all …]
|
| H 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/Documentation/litmus-tests/rcu/ |
| H 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/ |
| H 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.
111 bool "NVMe over Fabrics In-band Authentication in target side"
116 target side.
|
| /linux/tools/include/uapi/ |
| H 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/ |
| H 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/include/uapi/linux/netfilter/ |
| H A D | xt_recent.h | 34 __u8 side; member
43 __u8 side; member
|
| /linux/Documentation/staging/ |
| H A D | speculation.rst | 17 absence of data in caches. Such state may form side-channels which can be
66 Mitigating speculation side-channels
71 speculation-based side-channels are expected to implement these
75 prevent information from being leaked via side-channels.
|
| /linux/Documentation/networking/ |
| H 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
|
| H A D | snmp_counter.rst | 465 connection. So TCP layer sends a RST to the other side, indicate the
476 wait for the in-flight data are acked by the other side, the max wait
485 kernel will send a RST to the other side of the TCP connection.
492 side of the connection, then the app has no relationship with the
494 becomes an orphan socket, kernel waits for the reply of the other side,
497 the other side, and delete the socket, in such situation, kernel will
517 for the fin packet from the other side, kernel could send a RST and
599 know what happened on the receiver side. The sender just waits until
666 counts these two kinds of duplications on both receiver side and
667 sender side.
[all …]
|
| /linux/drivers/infiniband/ulp/rtrs/ |
| H 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/Documentation/hwmon/ |
| H A D | ina2xx.rst | 82 The INA219 is a high-side current shunt and power monitor with an I2C
86 The INA220 is a high or low side current shunt and power monitor with an I2C
92 INA230 and INA231 are high or low side current shunt and power monitors
96 INA260 is a high or low side current and power monitor with integrated shunt
99 The SY24655 is a high- and low-side current shunt and power monitor with an I2C
|
| /linux/drivers/usb/usbip/ |
| H A D | usbip_common.c | 687 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_iso()
709 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_iso()
771 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) { in usbip_recv_xbuff()
828 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_xbuff()
|
| /linux/drivers/block/ |
| H 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/Documentation/rust/ |
| H A D | general-information.rst | 70 Abstractions are Rust code wrapping kernel functionality from the C side.
72 In order to use functions and types from the C side, bindings are created.
74 the C side.
77 a ``struct mutex`` from the C side and calls its functions through the bindings.
124 wrapper function to ``rust/helpers/`` to make it available for the Rust side as
|
| /linux/Documentation/gpu/rfc/ |
| H A D | gpusvm.rst | 34 * GPU fault side
41 should not be handled on the fault side by trying to hold locks;
51 core-MM side rather than through a driver-side lock.
117 * Driver side madvise implementation and migration policies
|
| /linux/drivers/crypto/allwinner/ |
| H 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
|
| /linux/Documentation/ABI/stable/ |
| H A 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/drivers/usb/ |
| H A D | Kconfig | 45 tristate "Support for Host-side USB"
63 Say Y here if your computer has a host-side USB port and you want
71 If your system has a device-side USB port, used in the peripheral
72 side of the USB protocol, see the "USB Gadget" framework instead.
|
| /linux/Documentation/security/ |
| H A D | snp-tdx-threat-model.rst | 56 that acts as a security manager. The host-side virtual machine monitor
154 | CoCo security |<--->| Host/Host-side VMM |
172 While it is true that the host (and host-side VMM) requires some level of
192 side-channels, as well as transient execution side channels. Examples of
193 explicit (not side-channel) interfaces include accesses to port I/O, MMIO
195 hypercalls (towards Host-side VMM), access to shared memory pages,
240 side-channel and/or transient execution attack vectors.
|