Home
last modified time | relevance | path

Searched refs:side (Results 1 – 200 of 258) sorted by relevance

12

/linux-4.1.27/drivers/char/hw_random/
DKconfig29 This driver provides kernel-side support for a generic Random
44 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
83 This driver provides kernel-side support for the Random Number
96 This driver provides kernel-side support for the Random Number
109 This driver provides kernel-side support for the RNG200
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 Random Number
[all …]
/linux-4.1.27/Documentation/usb/
Dgadget_serial.txt54 side driver. It runs on a Linux system that has USB device side
81 On the device-side Linux system, the gadget serial driver looks
84 On the host-side system, the gadget serial device looks like a
89 The host side driver can potentially be any ACM compliant driver
95 With the gadget serial driver and the host side ACM or generic
97 the host and the gadget side systems as if they were connected by a
108 side kernel for "Support for USB Gadgets", for a "USB Peripheral
125 side Linux system. You can add this to the start up scripts, if
146 either the Windows or Linux ACM driver on the host side. If gadget
148 Linux generic serial driver on the host side. Follow the appropriate
[all …]
Dlinux-cdc-acm.inf82 ; When developing your USB device, the VID and PID used in the PC side
Dgadget_multi.txt22 To make use of the gadget one needs to make it work on host side --
30 side. All the functions are handled by respective drivers developed
Dbulk-streams.txt14 Device-side implications
Dgadget-testing.txt375 whatever is played at the gadget side with aplaymidi -l is audible
646 actually hear something at the device side, a command similar
647 to this must be used at the device side:
Dmass-storage.txt43 the host side, the contents are not well defined.
/linux-4.1.27/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.
86 1. An RCU read-side critical section (implicit), or
91 RCU read-side critical sections, in case (2) the ->file_lock prevents
102 complain if this was used in an RCU read-side critical section unless one
111 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.
45 2. Do the RCU read-side critical sections make proper use of
49 under your read-side code, which can greatly increase the
54 rcu_read_lock_sched(), or by the appropriate update-side lock.
131 perfectly legal (if redundant) for update-side code to
136 of an RCU read-side critical section. See lockdep.txt
167 be traversed by an RCU read-side critical section.
252 One way to stall the updates is to acquire the update-side
[all …]
DwhatisRCU.txt77 b. Wait for all previous readers to complete their RCU read-side
138 entering an RCU read-side critical section. It is illegal
139 to block while in an RCU read-side critical section, though
141 read-side critical sections. Any RCU-protected data structure
142 accessed during an RCU read-side critical section is guaranteed to
152 exiting an RCU read-side critical section. Note that RCU
153 read-side critical sections may be nested and/or overlapping.
161 read-side critical sections on all CPUs have completed.
163 any subsequent RCU read-side critical sections to complete.
176 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
Drcu.txt34 read-side critical sections. So, if we remove an item from a
42 RCU read-side critical sections. SRCU also uses CPU-local
43 counters, and permits general blocking within RCU read-side
86 boosting of preempted RCU read-side critical sections. This is
DUP.txt47 all RCU read-side critical sections currently executing have completed.
102 list, and is therefore within an RCU read-side critical section.
104 read-side critical section, and is not permitted to block.
132 of an RCU read-side critical section. If synchronize_rcu()
DlistRCU.txt14 used, the read-side lock would be dropped before taking any action
51 This means that RCU can be easily applied to the read side, as follows:
73 insert the read-side memory barriers that are required on DEC Alpha CPUs.
75 The changes to the update side are also straightforward. A reader-writer
DRTFP.txt36 this paper helped inspire the update-side batching used in the later
45 tracking imposes significant read-side overhead, which is undesirable
47 write-side contention and parallelize the other write-side overheads by
72 any write-side changes he might have made in this work using SGI's Irix
84 read-side-tracking to permit replugging of algorithms within a commercial
117 impose significant read-side overhead in the form of memory barriers.
156 RCU [PaulEMcKenney2006b], but priority-boosting of RCU read-side critical
158 blocking in read-side critical sections appeared [PaulEMcKenney2006c],
203 between memory barriers and read-side traversal order: If the updater
204 is making changes in the opposite direction from the read-side traveral
[all …]
Drcuref.txt74 overkill, since we hold the update-side spinlock. One might instead
DarrayRCU.txt29 this situation, which would also have minimal read-side overhead as long
Dtrace.txt368 read-side critical section blocks the current grace
370 at least one task blocked in an RCU read-side critical
373 least one task is blocked within an RCU read-side
462 in an RCU read-side critical section.
Dstallwarn.txt180 o A CPU looping in an RCU read-side critical section.
206 read-side critical section. This is especially damaging if
Dtorture.txt82 read-side critical sections.
274 o "nt": The number of times rcutorture ran RCU read-side code from
Drcubarrier.txt8 and unbounded latency. RCU read-side critical sections are delimited
/linux-4.1.27/include/uapi/linux/netfilter/
Dxt_recent.h32 __u8 side; member
41 __u8 side; member
/linux-4.1.27/Documentation/hwmon/
Dina2xx40 The INA219 is a high-side current shunt and power monitor with an I2C
44 The INA220 is a high or low side current shunt and power monitor with an I2C
50 INA230 and INA231 are high or low side current shunt and power monitors
Dmax1606535 accurately monitor (+/-2.5%) one current channel using a dedicated high-side
47 one current channel using a dedicated high-side current-sense amplifier. The
Dlm7046 Jean Delvare <jdelvare@suse.de> for mentoring the hwmon-side driver
Dina20919 The TI / Burr-Brown INA209 monitors voltage, current, and power on the high side
Dvt121136 Be aware that overriding BIOS defaults might cause some unwanted side effects!
/linux-4.1.27/drivers/tty/serial/
Dsb1250-duart.c785 int chip, side; in sbd_probe_duarts() local
809 for (side = 0; side < DUART_MAX_SIDE && line < max_lines; in sbd_probe_duarts()
810 side++, line++) { in sbd_probe_duarts()
811 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_probe_duarts()
847 int side = co->index % DUART_MAX_SIDE; in sbd_console_write() local
848 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_console_write()
875 int side = co->index % DUART_MAX_SIDE; in sbd_console_setup() local
876 struct sbd_port *sport = &sbd_duarts[chip].sport[side]; in sbd_console_setup()
Dzs.c1075 int chip, side, irq; in zs_probe_sccs() local
1101 for (side = 0; side < ZS_NUM_CHAN; side++) { in zs_probe_sccs()
1102 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_probe_sccs()
1114 uport->line = chip * ZS_NUM_CHAN + side; in zs_probe_sccs()
1117 (side ^ ZS_CHAN_B) * ZS_CHAN_IO_SIZE; in zs_probe_sccs()
1150 int chip = co->index / ZS_NUM_CHAN, side = co->index % ZS_NUM_CHAN; in zs_console_write() local
1151 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_console_write()
1196 int chip = co->index / ZS_NUM_CHAN, side = co->index % ZS_NUM_CHAN; in zs_console_setup() local
1197 struct zs_port *zport = &zs_sccs[chip].zport[side]; in zs_console_setup()
/linux-4.1.27/drivers/block/
Dswim.c34 unsigned char side; member
460 int side, int track, in swim_read_sector() argument
472 swim_head(base, side); in swim_read_sector()
473 swim_write(base, mode0, side); in swim_read_sector()
489 if ((header.side != side) || (header.track != track) || in swim_read_sector()
502 int side, track, sector; in floppy_read_sectors() local
511 side = x / fs->secpertrack; in floppy_read_sectors()
516 ret = swim_read_sector(fs, side, track, sector, in floppy_read_sectors()
Damiflop.c867 side, /* 0-1 */ member
1062 printk("(%3d,%d,%2d,%d) %x\n", hdr.track, hdr.side, in dos_read()
1078 if (hdr.side != unit[drive].track%unit[drive].type->heads) { in dos_read()
1080 hdr.side, in dos_read()
1106 hdr.track,hdr.side,hdr.sec,hdr.len_desc,scnt); in dos_read()
1117 "sc=%d, %x %x\n", hdr.track, hdr.side, in dos_read()
1172 hdr.side=unit[drive].track%unit[drive].type->heads; in ms_putsec()
Dataflop.c284 #define IS_BUFFERED(drive,side,track) \ argument
285 (BufferDrive == (drive) && BufferSide == (side) && BufferTrack == (track))
342 static void fd_select_side( int side );
410 static void fd_select_side( int side ) in fd_select_side() argument
418 sound_ym.wd_data = (side == 0) ? sound_ym.rd_data_reg_sel | 0x01 : in fd_select_side()
/linux-4.1.27/arch/arm/kernel/
Dhead-nommu.S181 .macro setup_region bar, acr, sr, side = MPU_DATA_SIDE
182 mcr p15, 0, \bar, c6, c1, (0 + \side) @ I/DRBAR
183 mcr p15, 0, \acr, c6, c1, (4 + \side) @ I/DRACR
184 mcr p15, 0, \sr, c6, c1, (2 + \side) @ I/DRSR
/linux-4.1.27/drivers/usb/
DKconfig42 tristate "Support for Host-side USB"
58 Say Y here if your computer has a host-side USB port and you want
66 If your system has a device-side USB port, used in the peripheral
67 side of the USB protocol, see the "USB Gadget" framework instead.
DREADME5 ("make pdfdocs", and then look at "usb.pdf" for host side and
6 "gadget.pdf" for peripheral side.) Also, Documentation/usb has
/linux-4.1.27/Documentation/video4linux/
Dsi476x.txt141 0x09 | injside | 0 - Low-side injection is being used
142 | | 1 - High-side injection is used
160 0x18 | lassi | Signed Low side adjacent Channel
163 0x19 | hassi | ditto fpr High side
Dsoc-camera.txt104 side, based on camera capabilities.
Duvcvideo.txt210 Data is copied directly from the device without any driver-side
Dvivid.txt912 sequence and field counting in struct v4l2_buffer on the capture side may not
920 - on the input side the "Standard Signal Mode" for the S-Video input or the
931 output must be configured for sliced VBI. The VBI capture side can be configured
946 faithfully on the receiver side. Note that when the driver is loaded the
1098 on the capture side. The use of the clipping, chromakeying or alpha processing
/linux-4.1.27/Documentation/devicetree/bindings/regulator/
Dmax8997-regulator.txt45 - max8997,pmic-ignore-gpiodvs-side-effect: When GPIO-DVS mode is used for
47 that of another buck, which is the side effect of the change (set_voltage).
48 Use this property to ignore such side effects and change the voltage.
102 max8997,pmic-ignore-gpiodvs-side-effect;
/linux-4.1.27/drivers/infiniband/
DKconfig20 is the kernel side of the userspace MAD support, which allows
29 kernel side of userspace verbs and the userspace
/linux-4.1.27/Documentation/isdn/
DREADME.x2516 other side first. Be prepared that bugs in the protocol implementation
119 To mimic an X.25 network switch (DCE side of the connection), use
125 x25d[tc]e uses fixed lap_b addresses. With x75i, the side which
127 called side used the DCE's lap_b address. Thus, l2_prot x75i might
131 trick. At the switch side, a terminal adapter X.21 was used to connect
DsyncPPP.FAQ37 If your remote side immediately starts to send
178 If your side doesn't know the IP address after negotiation, it
218 your remote side rejects. Next time configure your ipppd
219 to not negotiate these options. Another 'side effect' is, that
220 this increases redundancy. (e.g your remote side is buggy and
DREADME.audio102 hangup of the remote side) Emulator stops
/linux-4.1.27/Documentation/arm/
Dcluster-pm-race-avoidance.txt205 In this discussion, the "outbound side" is the view of the cluster state
206 as seen by a CPU tearing the cluster down. The "inbound side" is the
215 on the outbound side:
221 "inbound" state: The state of the cluster on the inbound side.
252 further transition possible on the outbound side (i.e., the
282 where the <transitioner> is the side on which the transition
283 can occur; either the inbound or the outbound side.
411 The CPU which performs cluster tear-down operations on the outbound side
414 The CPU which performs cluster setup on the inbound side is commonly
/linux-4.1.27/lib/
Dassoc_array.c497 struct assoc_array_node *node, *new_n0, *new_n1, *side; in assoc_array_insert_into_terminal_node() local
700 side = assoc_array_ptr_to_node(ptr); in assoc_array_insert_into_terminal_node()
701 edit->set_backpointers[i] = &side->back_pointer; in assoc_array_insert_into_terminal_node()
830 struct assoc_array_node *node, *new_n0, *side; in assoc_array_insert_mid_shortcut() local
911 side = assoc_array_ptr_to_node(shortcut->next_node); in assoc_array_insert_mid_shortcut()
912 new_n0->nr_leaves_on_branch = side->nr_leaves_on_branch; in assoc_array_insert_mid_shortcut()
950 edit->set[1].ptr = &side->back_pointer; in assoc_array_insert_mid_shortcut()
961 edit->set_parent_slot[0].p = &side->parent_slot; in assoc_array_insert_mid_shortcut()
963 edit->set[1].ptr = &side->back_pointer; in assoc_array_insert_mid_shortcut()
/linux-4.1.27/Documentation/input/
Dgamepad.txt39 4 buttons in diamonds-shape (on the right side). The buttons are
43 4 buttons (on the left side) that point up, down, left and right.
54 Triggers are located on the upper-side of the pad in vertical direction.
80 analog stick and two trigger buttons on the right side.
Dwalkera0701.txt15 At back side of transmitter S-video connector can be found. Modulation
23 (back side of TX)
Djoystick-parport.txt37 the computer's side (and thus timing insensitive). To allow up to 5 NES
99 This is everything you need on the PC's side of the connection, now on to
100 the gamepads side. The NES and SNES have different connectors. Also, there
256 On a side note, if you have already built a different adapter for use with
Dxpad.txt50 right side (A, B, X, Y, black, white) are said to be "analog" and
Djoystick.txt258 rear side of the joystick. However, moving it, you'll reset the joystick,
462 side of the orb, although reported as an ordinary button, causes internal
/linux-4.1.27/scripts/coccinelle/tests/
Ddoubletest.cocci2 //# A common source of false positives is when the argument performs a side
Ddoublebitand.cocci2 //# One source of false positives is when the argument performs a side
/linux-4.1.27/arch/arm/boot/dts/
Dberlin2-sony-nsz-gs7.dts33 /* Unpopulated SATA plug on solder side */
Darmada-xp-openblocks-ax3-4.dts211 /* Front side USB 0 */
216 /* Front side USB 1 */
Darmada-xp-gp.dts214 /* Front-side USB slot */
219 /* Back-side USB slot */
Dexynos4210-trats.dts198 max8997,pmic-ignore-gpiodvs-side-effect;
Dste-nomadik-stn8815.dtsi270 * IP AMBA bus clocks, driving the bus side of the
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dux500-mop500.txt9 - stericsson,cpu-dai : Phandle to the CPU-side DAI
Dux500-msp.txt1 * ux500 MSP (CPU-side Digital Audio Interface)
Dadi,adau1701.txt17 configured clock divider on ASoC side before the
/linux-4.1.27/net/ipv4/
DKconfig244 Kernel side support for Sparse Mode PIM (Protocol Independent
257 Kernel side support for Sparse Mode PIM version 2. In order to use
470 BIC-TCP is a sender-side only change that ensures a linear RTT
492 TCP Westwood+ is a sender-side only modification of the TCP Reno
506 H-TCP is a send-side only modifications of the TCP Reno
527 TCP-Hybla is a sender-side only change that eliminates penalization of
536 TCP Vegas is a sender-side only change to TCP that anticipates
546 Scalable TCP is a sender-side only change to TCP which uses a
564 TCP Veno is a sender-side only enhancement of TCP to obtain better
576 YeAH-TCP is a sender-side high-speed enabled TCP congestion control
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dimg-ir-rev1.txt17 2nd: System side (fast) clock.
/linux-4.1.27/lib/raid6/
Dint.uc119 z0 = stop; /* P/Q right side optimization */
135 /* P/Q left side optimization */
/linux-4.1.27/drivers/vhost/
DKconfig28 the host side of a virtio ring.
/linux-4.1.27/drivers/usb/usbip/
Dusbip_common.c646 if (ud->side == USBIP_STUB) in usbip_recv_iso()
668 if (ud->side == USBIP_STUB) in usbip_recv_iso()
726 if (ud->side == USBIP_STUB) { in usbip_recv_xbuff()
747 if (ud->side == USBIP_STUB) { in usbip_recv_xbuff()
Dusbip_common.h258 enum usbip_side side; member
Dstub_dev.c280 sdev->ud.side = USBIP_STUB; in stub_device_alloc()
Dusbip_protocol.txt263 | | | server-side host controller
Dvhci_hcd.c856 vdev->ud.side = USBIP_VHCI; in vhci_device_init()
/linux-4.1.27/scripts/coccinelle/misc/
Dbugon.cocci60 …d of if condition followed by BUG.\nPlease make sure the condition has no side effects (see condit…
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-cros-ec-tunnel.txt4 controller) but no direct connection to some devices on the other side of
Di2c-mux-gpio.txt22 - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side
Di2c-mux-pinctrl.txt23 - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side
Di2c-arb-gpio-challenge.txt28 sure that the other side doesn't want it also. A detailed explanation is best
/linux-4.1.27/drivers/staging/android/ion/
DKconfig18 kernel and device side ION functions.
/linux-4.1.27/Documentation/x86/
Dearlyprintk.txt70 right and side of the device (with the product logo facing up and
72 power supply is taken from only one side of the device and it
73 must be the side that does not get rebooted.
/linux-4.1.27/drivers/usb/wusbcore/
DKconfig13 Enable the host-side support for Wireless USB.
/linux-4.1.27/Documentation/extcon/
Dporting-android-switch-class20 @index: drop (not used in switch device driver side anyway)
83 At the side of other device drivers (the extcon device itself
/linux-4.1.27/drivers/usb/gadget/legacy/
DKconfig6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
25 it can work on top of most device-side usb controllers. It's
30 USB peripheral controller driver. Then you can use host-side
34 Gadget Zero also works with the host-side "usb-skeleton" driver,
35 and with many kinds of host-side test software. You may need
113 The Linux-USB host-side "usbnet" driver interoperates with this
/linux-4.1.27/Documentation/virtual/kvm/
Dcpuid.txt57 KVM_FEATURE_CLOCKSOURCE_STABLE_BIT || 24 || host will warn if no guest-side
/linux-4.1.27/drivers/staging/nvec/
DKconfig48 Say Y to enable control of the yellow side leds on Compal PAZ00 based
/linux-4.1.27/Documentation/misc-devices/
Dlis3lv02d74 * If the left side is elevated, X increases (becomes positive)
75 * If the front side (where the touchpad is) is elevated, Y decreases
Dapds990x.txt38 Proximity side is little bit simpler. There is no need for complex conversions.
Dbh1770glc.txt19 but ALS side results are used to estimate reliability of the proximity sensor.
/linux-4.1.27/Documentation/vm/
Dremap_file_pages.txt25 One side effect of emulation (apart from performance) is that user can hit
Dfrontswap.txt146 out to disk, there is a side effect that this may create more memory
223 Similarly, a KVM guest-side implementation could do in-guest compression
/linux-4.1.27/drivers/usb/gadget/udc/
DKconfig6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
386 side is the master; the gadget side is the slave. Gadget drivers
394 Since such a gadget side driver needs to interoperate with a host
395 side Linux-USB device driver, this may help to debug both sides
/linux-4.1.27/Documentation/arm/nwfpe/
DNOTES15 This is a side effect of the stfe instruction. The double in f4 had to be
/linux-4.1.27/Documentation/devicetree/bindings/arm/exynos/
Dpower_domain.txt52 of consumer-side bindings.
/linux-4.1.27/Documentation/fb/
Dcmap_xfbdev.txt52 hand side boundaries of a color range.
Dintel810.txt239 safe side, you can leave this unselected.
Dfbcon.txt107 One side effect that may be useful is using a map value that exceeds
Dframebuffer.txt167 After each scanline the electron beam has to move back to the left side of the
/linux-4.1.27/Documentation/infiniband/
Duser_mad.txt36 MADs are received using read(). The receive side now supports
82 filled into the lid field, and so on. The send side does support
/linux-4.1.27/tools/perf/Documentation/
Dperf-kvm.txt76 Collect host side performance profile.
78 Collect guest side performance profile.
Dperf-record.txt235 overrides that and uses per-thread mmaps. A side-effect of that is that
/linux-4.1.27/Documentation/sound/alsa/
DHD-Audio-Controls.txt69 side or a CLFE-channel DAC, the DAC is switched to the headphone
76 and speaker outputs. As a side-effect, when this mode is set, the
Dpowersave.txt39 the controller side. Setting this on may reduce a bit more power
DChannel-Mapping-API.txt89 SNDRV_CHMAP_SL, /* side left */
90 SNDRV_CHMAP_SR, /* side right */
DControlNames.txt24 Side (side left/right for 7.1 surround)
Dtimestamping.txt170 ahead of the actual playback time (as a side time this sort of
Dhda_codec.txt70 controller side, too.
/linux-4.1.27/Documentation/serial/
Dtty.txt40 TTY side interfaces:
199 TTY_OTHER_CLOSED Device is a pty and the other side has closed.
208 take line discipline locks. The same is true of calls from the driver side
289 from the host side. [Can sleep ??]
/linux-4.1.27/Documentation/networking/
Dipsec.txt38 will skip policy checking on receiver side.
Dvxge.txt57 Receive side steering for better scaling.
DPLIP.txt83 data transfer (the maximal time the PLIP driver would allow the other side
94 trigger timeout on the *other* side of a PLIP connection, to about
Dtuntap.txt210 the other side over TCP or UDP. The application on the other side decompresses
Ddccp.txt145 the behaviour of the other, passive side: this variable also sets
153 side considers its connecting peer dead. Analogue of tcp_retries1.
Dnfc.txt19 providing the device driver interface. On the other side, it is also
Dgeneric-hdlc.txt83 dce - Frame Relay DCE (network) side LMI instead of default DTE (user).
Dieee802154.txt39 Kernel side
Drxrpc.txt150 A hard-ACK indicates to the far side that all the data received to a point
190 (*) A client-side connection is only shared between calls if they have have
195 (*) A server-side connection is shared if the client says it is.
200 (*) SO_KEEPALIVE automatically pings the other side to keep the connection
884 Usually the other side won't stop sending packets until the advertised
Dphonet.txt162 two endpoints directly, using connect() on the active side. This is
Dde4x5.txt139 more than one DECchip based card. As a side effect, I don't mess with
Dudplite.txt72 This option is the receiver-side analogue. It is truly optional, i.e. not
Dnetlink_mmap.txt51 On kernel side, in order to make use of memory mapped I/O on receive, the
Deql.txt22 side.
Dip-sysctl.txt163 time-to-live on the reassembling side. This minimum time-to-live is
288 RTT fluctuates (e.g., wireless). F-RTO is sender-side only
306 causing each side to send an unterminating stream of duplicate
541 2: Enables TCP Fast Open on the server side, i.e., allowing data in
555 Note that the client & server side Fast Open flags (1 and 2
/linux-4.1.27/drivers/staging/iio/Documentation/
Dring.txt17 These are used to perform device specific steps on either side
/linux-4.1.27/drivers/block/drbd/
Ddrbd_worker.c1655 void drbd_start_resync(struct drbd_device *device, enum drbd_conns side) in drbd_start_resync() argument
1668 if (side == C_SYNC_TARGET) { in drbd_start_resync()
1729 ns.conn = side; in drbd_start_resync()
1731 if (side == C_SYNC_TARGET) in drbd_start_resync()
1780 if (side == C_SYNC_TARGET) { in drbd_start_resync()
1794 if (side == C_SYNC_SOURCE && connection->agreed_pro_version < 96) in drbd_start_resync()
1808 if (side == C_SYNC_SOURCE) { in drbd_start_resync()
DKconfig63 512 insert data corruption on receiving side
/linux-4.1.27/Documentation/cgroups/
Dcpuacct.txt43 system times. This has two side effects:
Dblkio-controller.txt100 enabled from cgroup side, which currently is a development option and
117 Throttling without "sane_behavior" enabled from cgroup side will
Dunified-hierarchy.txt270 - Events are filtered from the kernel side. A "notify_on_release"
366 side of a looser limit and end up wasting precious resources.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dcpm.txt47 CPM-side offsets with pointer subtraction. It is recommended that
/linux-4.1.27/tools/testing/selftests/ftrace/
DREADME31 * Take care with side effects as the tests are run with root privilege.
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DUSB-Host.txt20 <*> Support for Host-side USB
/linux-4.1.27/drivers/usb/gadget/
DKconfig6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
29 familiar host side controllers have names like "EHCI", "OHCI",
35 peripheral/device side bus controller, and a "gadget driver" for
358 USB peripheral controller driver. Then you can use host-side
/linux-4.1.27/arch/c6x/lib/
Dcsum_64plus.S31 ZERO .D1 A9 ; csum (a side)
32 || ZERO .D2 B9 ; csum (b side)
/linux-4.1.27/arch/frv/kernel/
Dcmode.S119 # devices set to cacheable on the external bus side in parallel
/linux-4.1.27/Documentation/filesystems/cifs/
DAUTHORS11 side of the original CIFS Unix extensions and reviewing and implementing
DTODO67 such as "CopyChunk" (fast server side file copy)
/linux-4.1.27/Documentation/blockdev/
Dcciss.txt104 entry which the "block" side of the driver creates as
165 side during the SCSI error recovery process, the cciss driver only
/linux-4.1.27/Documentation/spi/
Dspi-lm70llp77 o David Brownell for mentoring the SPI-side driver development.
Dbutterfly28 side this is like "sp12" programming cables.
Dspi-summary66 side of SPI interactions.
149 other side of an SPI link.
157 A "struct spi_device" encapsulates the master-side interface between
158 those two types of driver. At this writing, Linux has no slave side
/linux-4.1.27/Documentation/networking/mac80211_hwsim/
DREADME51 processing access point side of association.
/linux-4.1.27/Documentation/scsi/
Dmegaraid.txt11 interfaces with the applications on one side and all the low level drivers
Dlpfc.txt39 to reappear or link come back alive, with no inadvertent side effects
/linux-4.1.27/Documentation/sound/alsa/soc/
Djack.txt5 the kernel side of which can be seen in include/sound/jack.h. ASoC
/linux-4.1.27/arch/s390/
DKconfig719 i.e. enables or disables monitoring on the Linux side.
735 on the z/VM side.
752 on the z/VM side.
768 on the z/VM side.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-driver-wacom47 same side are always inactive.
Dsysfs-class-net-statistics88 due to lack of capacity in the receive side. See the network
Dsysfs-devices-power239 latency tolerance requirements from the kernel side.
/linux-4.1.27/Documentation/scheduler/
Dcompletion.txt37 wait_for_completion() and the signaling side through a call to complete()
119 to wait_for_completion() then the waiting side simply will continue
Dsched-nice-design.txt108 side-effect of the recalibrated dynamic range of nice levels.
Dsched-design-CFS.txt62 side of the tree as much as possible.
/linux-4.1.27/net/netfilter/
Dxt_recent.c252 if (info->side == XT_RECENT_DEST) in recent_mt()
261 if (info->side == XT_RECENT_DEST) in recent_mt()
/linux-4.1.27/Documentation/gpio/
Ddriver.txt97 other GPIO irqchip residing on the other side of a sleeping bus. Of course
150 competition inside the subsystem which side is using the resource (a certain
/linux-4.1.27/Documentation/
Dxillybus.txt92 communication to the user. At the host side, a character device file is used
93 just like any pipe file. On the FPGA side, hardware FIFOs are used to stream
176 FPGA side to the seekable stream. Reading or writing to a certain address in
374 FPGA side has sent data, but a select() call would still block, because the
Dcachetlb.txt8 describes its intended purpose, and what side effect is expected
11 The side effects described below are stated for a uniprocessor
14 definition such that the side effect for a particular interface occurs
Dvolatile-considered-harmful.txt79 visible side effects, risks being deleted by GCC. Adding the volatile
Dflexible-arrays.txt41 notably unpleasant side effects.
Ddma-buf-sharing.txt235 importers side are:
238 - full transparency for existing users on the importer side, i.e. userspace
352 rather similar to dma-buf from a userspace consumer side with using fds as
Dpi-futex.txt103 If the unlock side fastpath succeeds, [i.e. userspace manages to do a
Dmedia-framework.txt13 on the kernel-side implementation of the media framework.
312 Link configuration must not have any side effect on other links. If an enabled
Dvgaarbiter.txt182 implementation of the user space side [3]. Now (2009) Tiago Vignatti and Dave
Drobust-futex-ABI.txt106 other links between the locks, such as the reverse side of a double
Dstable_api_nonsense.txt167 The very good side effects of having your driver in the main kernel tree
DCodingStyle208 Use one space around (on each side of) most binary and ternary operators,
474 * Description: A column of asterisks on the left side,
869 removing it if GCC doesn't notice any side effects. You don't always need to
Dmemory-barriers.txt327 ordering over the memory operations on either side of the barrier.
1086 contained a load of A either side of the read barrier:
1328 compiler from moving the memory accesses either side of it to the other side:
2372 (smp_mb()) on each side of the actual operation (with the exception of
2684 accesses cross from the CPU side of things to the memory side of things, and
/linux-4.1.27/Documentation/filesystems/
Dfiles.txt52 The fdtable pointer must be read within the read-side
D9p.txt130 side for access validation
Dxfs-delayed-logging-design.txt636 the transaction commit side.
638 Because of the number of potential transaction commit side holders, the lock
645 transaction commit or CIL flush side sleeps with the lock held.
651 read side.
653 The second serialisation point is on the transaction commit side where items
/linux-4.1.27/arch/um/
DKconfig.char53 (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
/linux-4.1.27/Documentation/video4linux/bttv/
DREADME.quirks79 also has the side effect of not being able to take advantage of bus
/linux-4.1.27/drivers/gpu/drm/msm/
DNOTES14 And on gpu side of things:
/linux-4.1.27/Documentation/i2c/
Dinstantiating-devices195 undesirable side effects.
200 the aforementioned undesirable side effects.
/linux-4.1.27/fs/ncpfs/
DKconfig82 additional conversions on the client side. You can achieve similar
/linux-4.1.27/arch/sh/lib64/
Dmemcpy.S31 ! without side effects.
Dcopy_user_memcpy.S29 ! without side effects.
/linux-4.1.27/Documentation/arm/OMAP/
DDSS11 currently side by side, you can choose which one to use.
/linux-4.1.27/drivers/gpio/
DKconfig967 tristate "Freescale MC33880 high-side/low-side switch"
970 SPI driver for Freescale MC33880 high-side/low-side switch.
/linux-4.1.27/Documentation/laptops/
Dsony-laptop.txt87 you are not afraid of any side effects doing strange things with
Dsonypi.txt17 - jogdial events (the small wheel on the side of Vaios)
/linux-4.1.27/Documentation/zh_CN/
DCodingStyle401 * Description: A column of asterisks on the left side,
/linux-4.1.27/arch/sh/mm/
DKconfig107 From the kernel side this is used for the signal trampoline.
/linux-4.1.27/sound/core/
DKconfig186 other side, it makes the ALSA subsystem larger.
/linux-4.1.27/arch/
DKconfig358 can enable kernel-side support for the GCC feature.
399 - local variable's address used as part of the right hand side of an
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dinterlaken-lac.txt27 Interlaken control words and data words, which are sent on TX side to TCAM
/linux-4.1.27/Documentation/devicetree/bindings/bus/
Dmvebu-mbus.txt105 (S = 0x0), an address decoding window is allocated. On the other side,
/linux-4.1.27/Documentation/driver-model/
Ddevres.txt165 layer) where interface function shouldn't have side effect on failure.
/linux-4.1.27/drivers/s390/net/
Dctcm_mpc.c1666 static void mpc_action_side_xid(fsm_instance *fsm, void *arg, int side) in mpc_action_side_xid() argument
1720 if (side == XSIDE) { in mpc_action_side_xid()
1810 (side == XSIDE) ? "x-side XID" : "y-side XID"); in mpc_action_side_xid()
/linux-4.1.27/Documentation/powerpc/
Dtransactional_memory.txt83 side-effect, read soon-to-be-aborted transactional data that should not remain
/linux-4.1.27/drivers/tty/
DKconfig108 terminal. Typical programs for the master side are telnet servers
142 terminal. Typical programs for the master side are telnet servers
/linux-4.1.27/Documentation/power/
Duserland-swsusp.txt27 Even opening the device has side effects. Data structures are
Dpm_qos_interface.txt220 requirements from the kernel side in the device's list.
/linux-4.1.27/Documentation/frv/
Dkernel-ABI.txt175 Setting condition flags as a side effect of an arithmetic or logical
/linux-4.1.27/drivers/spi/
DKconfig5 # nobody's needed a slave side API yet. The master-role API is not
39 # MASTER side ... talking to discrete SPI slave chips including microcontrollers
/linux-4.1.27/Documentation/sysctl/
Dnet.txt150 Maximum number of packets, queued on the INPUT side, when the interface
/linux-4.1.27/arch/x86/
DKconfig.debug239 while not having any side-effect on the IO port space.
/linux-4.1.27/Documentation/kbuild/
Dmakefiles.txt1396 immediate evaluation of the right-hand side and stores an actual string
1397 into the left-hand side. "=" is like a formula definition; it stores the
1398 right-hand side in an unevaluated form and then evaluates this form each
1399 time the left-hand side is used.
/linux-4.1.27/drivers/pwm/
DKconfig14 within the Linux kernel. On the driver side it provides an API
/linux-4.1.27/Documentation/ia64/
Dmca.txt108 broken SAL symptoms, but some simply cannot be fixed from the OS side.
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-tape.1995-200224 * However, to be on the safe side, it is meanwhile
/linux-4.1.27/arch/powerpc/boot/dts/
Dvirtex440-ml510.dts345 * bar 0 on the plb side translates to 0.
/linux-4.1.27/drivers/usb/host/
DKconfig665 host side or peripheral side roles. Enable this option if your
/linux-4.1.27/Documentation/ioctl/
Dbotching-up-ioctls.txt42 * Pointers are __u64, cast from/to a uintprt_t on the userspace side and
/linux-4.1.27/fs/ext4/
Dmballoc.c1337 static inline int mb_buddy_adjust_border(int* bit, void* bitmap, int side) in mb_buddy_adjust_border() argument
1339 if (mb_test_bit(*bit + side, bitmap)) { in mb_buddy_adjust_border()
1341 (*bit) -= side; in mb_buddy_adjust_border()
1345 (*bit) += side; in mb_buddy_adjust_border()

12