Home
last modified time | relevance | path

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

123

/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
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 …]
/drivers/block/rnbd/
DREADME12 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.
DKconfig24 RNBD server is the server side of RNBD using rdma transport.
/drivers/nvme/target/
DKconfig10 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.
/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.
131 Provides a BMC-side character device implementing IPMI
162 implements the BMC side of the BT interface.
/drivers/infiniband/ulp/rtrs/
DREADME11 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
/drivers/usb/usbip/
Dusbip_common.c601 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()
/drivers/block/
Dswim.c31 unsigned char side; member
457 int side, int track, in swim_read_sector() argument
469 swim_head(base, side); in swim_read_sector()
470 swim_write(base, mode0, side); in swim_read_sector()
486 if ((header.side != side) || (header.track != track) || in swim_read_sector()
499 int side, track, sector; in floppy_read_sectors() local
508 side = x / fs->secpertrack; in floppy_read_sectors()
513 ret = swim_read_sector(fs, side, track, sector, in floppy_read_sectors()
Damiflop.c985 side, /* 0-1 */ member
1180 printk("(%3d,%d,%2d,%d) %x\n", hdr.track, hdr.side, in dos_read()
1196 if (hdr.side != unit[drive].track%unit[drive].type->heads) { in dos_read()
1198 hdr.side, in dos_read()
1224 hdr.track,hdr.side,hdr.sec,hdr.len_desc,scnt); in dos_read()
1235 "sc=%d, %x %x\n", hdr.track, hdr.side, in dos_read()
1290 hdr.side=unit[drive].track%unit[drive].type->heads; in ms_putsec()
Dataflop.c366 #define IS_BUFFERED(drive,side,track) \ argument
367 (BufferDrive == (drive) && BufferSide == (side) && BufferTrack == (track))
421 static void fd_select_side( int side );
501 static void fd_select_side( int side ) in fd_select_side() argument
509 sound_ym.wd_data = (side == 0) ? sound_ym.rd_data_reg_sel | 0x01 : in fd_select_side()
/drivers/tty/serial/
Dsb1250-duart.c772 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()
Dzs.c1072 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()
/drivers/crypto/allwinner/
DKconfig32 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
/drivers/usb/
DKconfig45 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.
/drivers/gpu/drm/i915/
DTODO.txt20 This is the matching task on the vm side compared to ttm/dma_resv on the
21 backing storage side.
/drivers/hwtracing/stm/
DKconfig24 The receiving side only needs to be able to decode the MIPI
39 The receiving side must be able to decode this protocol in
/drivers/infiniband/
DKconfig23 is the kernel side of the userspace MAD support, which allows
33 kernel side of userspace verbs and the userspace
/drivers/firmware/imx/
DKconfig11 exchange information with DSP side.
/drivers/usb/gadget/legacy/
DKconfig7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
48 it can work on top of most device-side usb controllers. It's
53 USB peripheral controller driver. Then you can use host-side
57 Gadget Zero also works with the host-side "usb-skeleton" driver,
58 and with many kinds of host-side test software. You may need
144 The Linux-USB host-side "usbnet" driver interoperates with this
/drivers/block/drbd/
Ddrbd_worker.c1737 void drbd_start_resync(struct drbd_device *device, enum drbd_conns side) in drbd_start_resync() argument
1755 if (side == C_SYNC_TARGET) { in drbd_start_resync()
1811 ns.conn = side; in drbd_start_resync()
1813 if (side == C_SYNC_TARGET) in drbd_start_resync()
1861 if (side == C_SYNC_TARGET) { in drbd_start_resync()
1875 if (side == C_SYNC_SOURCE && connection->agreed_pro_version < 96) in drbd_start_resync()
1889 if (side == C_SYNC_SOURCE) { in drbd_start_resync()
DKconfig63 512 insert data corruption on receiving side
/drivers/usb/gadget/udc/
DKconfig7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
478 side is the controller; the gadget side is the device. Gadget drivers
486 Since such a gadget side driver needs to interoperate with a host
487 side Linux-USB device driver, this may help to debug both sides
/drivers/staging/nvec/
DKconfig49 Say Y to enable control of the yellow side leds on Compal PAZ00 based
/drivers/net/ethernet/freescale/enetc/
DKconfig65 side, it can be loaded by Qos driver. Currently, it is only support
/drivers/usb/gadget/
DKconfig7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
31 familiar host side controllers have names like "EHCI", "OHCI",
37 peripheral/device side bus controller, and a "gadget driver" for
372 USB peripheral controller driver. Then you can use host-side

123