Home
last modified time | relevance | path

Searched refs:receive (Results 1 – 200 of 319) sorted by relevance

12

/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic-msgr.txt25 - mpic-msgr-receive-mask: Specifies what registers in the containing block
26 are allowed to receive interrupts. The value is a bit mask where a set
27 bit at bit 'n' indicates that message register 'n' can receive interrupts.
50 // Message registers 0 and 2 in this block can receive interrupts on
53 mpic-msgr-receive-mask = <0x5>;
59 // Message registers 0 and 2 in this block can receive interrupts on
62 mpic-msgr-receive-mask = <0x5>;
Dsrio-rmu.txt66 second element is associated with the receive (RX) interrupt.
96 second element is associated with the receive (RX) interrupt.
Dmpic.txt55 program will not receive interrupts for sources not belonging
/linux-4.4.14/drivers/input/serio/
Dlibps2.c187 int receive = (command >> 8) & 0xf; in __ps2_command() local
191 if (receive > sizeof(ps2dev->cmdbuf)) { in __ps2_command()
203 ps2dev->cmdcnt = receive; in __ps2_command()
204 if (receive && param) in __ps2_command()
205 for (i = 0; i < receive; i++) in __ps2_command()
206 ps2dev->cmdbuf[(receive - 1) - i] = param[i]; in __ps2_command()
245 for (i = 0; i < receive; i++) in __ps2_command()
246 param[i] = ps2dev->cmdbuf[(receive - 1) - i]; in __ps2_command()
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dcirrus,clps711x-intc.txt25 13: URXINT1 UART1 receive FIFO half full
29 17: SS2RX SSI2 receive FIFO half or greater full
32 29: URXINT2 UART2 receive FIFO half full
Dbrcm,bcm2836-l1-intc.txt4 events, and SMP IPIs. One of the CPUs may receive interrupts for the
/linux-4.4.14/net/caif/
Dcfveil.c33 vei->layer.receive = cfvei_receive; in cfvei_create()
44 caif_assert(layr->receive != NULL); in cfvei_receive()
55 ret = layr->up->receive(layr->up, pkt); in cfvei_receive()
Dcfdgml.c34 dgm->layer.receive = cfdgml_receive; in cfdgml_create()
47 caif_assert(layr->receive != NULL); in cfdgml_receive()
62 ret = layr->up->receive(layr->up, pkt); in cfdgml_receive()
Dcfutill.c34 util->layer.receive = cfutill_receive; in cfutill_create()
46 caif_assert(layr->up->receive != NULL); in cfutill_receive()
56 return layr->up->receive(layr->up, pkt); in cfutill_receive()
Dcfdbgl.c27 dbg->layer.receive = cfdbgl_receive; in cfdbgl_create()
35 return layr->up->receive(layr->up, pkt); in cfdbgl_receive()
Dcfvidl.c30 vid->layer.receive = cfvidl_receive; in cfvidl_create()
44 return layr->up->receive(layr->up, pkt); in cfvidl_receive()
Dcaif_dev.c239 static int receive(struct sk_buff *skb, struct net_device *dev, in receive() function
251 if (!caifd || !caifd->layer.up || !caifd->layer.up->receive || in receive()
262 err = caifd->layer.up->receive(caifd->layer.up, pkt); in receive()
278 .func = receive,
350 *rcv_func = receive; in caif_enroll_dev()
Dcfrfml.c56 this->serv.layer.receive = cfrfml_receive; in cfrfml_create()
107 caif_assert(layr->receive != NULL); in cfrfml_receive()
167 err = rfml->serv.layer.up->receive(rfml->serv.layer.up, pkt); in cfrfml_receive()
Dcfserl.c40 this->layer.receive = cfserl_receive; in cfserl_create()
153 ret = layr->layer.up->receive(layr->layer.up, pkt); in cfserl_receive()
Dcffrml.c48 this->layer.receive = cffrml_receive; in cffrml_create()
134 return layr->up->receive(layr->up, pkt); in cffrml_receive()
Dcaif_usb.c46 return layr->up->receive(layr->up, pkt); in cfusbl_receive()
96 this->layer.receive = cfusbl_receive; in cfusbl_create()
Dcfmuxl.c54 this->layer.receive = cfmuxl_receive; in cfmuxl_create()
205 ret = up->receive(up, pkt); in cfmuxl_receive()
Dchnl_net.c411 priv->chnl.receive = chnl_recv_cb; in ipcaif_net_setup()
/linux-4.4.14/Documentation/isdn/
DINTERFACE.fax18 In receive-mode the LL-driver takes care of the bit-order conversion
67 Defines outgoing/send or incoming/receive connection.
87 (+FCSI/+FTSI on send/receive)
112 ISDN_TTY_FAX_TRAIN_OK output of +FDCS and OK message (for receive mode).
114 ISDN_TTY_FAX_EOP signals end of data in receive mode,
132 Set by HL in receive-mode for +FET message.
DREADME.concap99 - receive data from lower (hardware) layer
169 The network interface does not explicitly provide a receive service
DREADME.avmb197 recvqueuelen: number of messages on receive queue
/linux-4.4.14/Documentation/networking/
Dscaling.txt23 Contemporary NICs support multiple receive and transmit descriptor queues
27 of logical flows. Packets for each flow are steered to a separate receive
38 stores a queue number. The receive queue for a packet is determined
45 can be directed to their own receive queue. Such “n-tuple” filters can
53 num_queues. A typical RSS configuration would be to have one receive queue
68 Each receive queue has a separate IRQ associated with it. The NIC triggers
74 processing takes place in receive interrupt handling, it is advantageous
75 to spread receive interrupts between CPUs. To manually adjust the IRQ
82 RSS should be enabled when latency is a concern or whenever receive
87 is likely the one with the smallest number of receive queues where no
[all …]
Ds2io.txt44 and receive, TSO.
46 c. Multi-buffer receive mode. Scattering of packet across multiple
58 f. Multi-FIFO/Ring. Supports up to 8 transmit queues and receive rings,
68 Number of receive rings
78 Size of each receive ring(in 4K blocks)
Dvxge.txt45 Checksum offload (TCP/UDP/IP) on transmit and receive paths
47 Generic Receive Offload (GRO) on receive path
64 Up to 17 hardware based transmit and receive data channels, with
Daltera_tse.txt36 The SGDMA supports only a single transmit or receive operation at a time, and
74 The driver will post receive buffers to the receive DMA logic during driver
76 underlying DMA logic (MSGDMA is able queue receive buffers, SGDMA is not able
77 to queue receive buffers to the SGDMA receive logic). When a packet is
78 received, the DMA logic generates an interrupt. The driver handles a receive
79 interrupt by obtaining the DMA receive logic status, reaping receive
80 completions until no more receive completions are available.
84 using NAPI for receive operations. Interrupt mitigation is not yet supported
Dixgb.txt132 This value is the number of receive descriptors allocated by the driver.
134 Each descriptor is 16 bytes. A receive buffer is also allocated for
137 receive buffer size is 2048 bytes. When the MTU is greater than 1500 the
138 receive buffer size will be either 4056, 8192, or 16384 bytes. The
144 This value delays the generation of receive interrupts in units of
150 run out of available receive descriptors.
172 of Linux to transmit and receive data. The following enhancements were
230 # set maximum receive socket buffer size, default 131071
234 # set default receive socket buffer size, default 65535
254 If your server does not seem to be able to receive UDP traffic as fast as it
[all …]
Diphase.txt97 RX_CNT = number of receive buffers in the range (1-128)
98 RX_SIZE = size of receive buffers in the range (48-64K)
102 1. Transmit and receive buffer size must be a multiple of 4.
104 transmit and receive buffers is less than or equal to the
124 At the test machine intended to receive data, type:
Dnetdevices.txt38 MTU is symmetrical and applies both to receive and transmit. A device
39 must be able to receive at least the maximum size packet allowed by
40 the MTU. A network device may use the MTU as mechanism to size receive
Dppp_generic.txt26 to be able to send PPP frames, receive PPP frames, and optionally
35 on receive.
263 and receive PPP control frames, using the read() and write() system
265 attached to a channel can be used to send and receive PPP frames on
279 makes it available to send and receive data packets for that unit.
324 * PPPIOCSMRU sets the MRU (maximum receive unit) for the interface.
334 SC_REJ_COMP_TCP disable receive TCP header decompression
365 field. If this is 0, the ioctl will affect the receive path,
385 the transmit and receive idle timers is restricted to those which
402 NPMODE_PASS normal operation, transmit and receive packets
[all …]
De100.txt56 Rx Descriptors: Number of receive descriptors. A receive descriptor is a data
57 structure that describes a receive buffer and its attributes to the network
158 This results in unbalanced receive traffic.
Dcxgb.txt126 Setting maximum receive socket buffer size:
135 Setting default receive socket buffer size:
157 The receive buffer (RX_WINDOW) size must be at least as large as the
166 Setting the min, max, and default receive buffer (RX_WINDOW) size:
170 The receive buffer (RX_WINDOW) size may be calculated the same as single
176 correct receive buffer size.
177 Setting the min, max, and default receive buffer (RX_WINDOW) size is
Drds.txt50 Sockets must be bound before you can send or receive data.
73 setsockopt(SOL_SOCKET): send and receive buffer size
74 RDS honors the send and receive buffer size socket options.
80 The SO_RCVSIZE option controls the maximum receive queue length.
113 Applications can ask the RDS kernel module to receive
218 there is space in the peer's receive buffers for more data. This
223 Messages waiting in the receive queue on the receiving socket
De1000e.txt98 traffic is mostly transmit or mostly receive, the interrupt rate could
106 RxAbsIntDelay parameters. In other words, minimizing the receive
131 This value delays the generation of receive interrupts in units of 1.024
136 may be set too high, causing the driver to run out of available receive
152 receive interrupt is generated. Useful only if RxIntDelay is non-zero,
227 you have a machine with a BMC enabled but cannot receive IPMI traffic after
De1000.txt130 traffic is mostly transmit or mostly receive, the interrupt rate could
138 RxAbsIntDelay parameters. In other words, minimizing the receive
174 This value specifies the number of receive buffer descriptors allocated
178 Each descriptor is 16 bytes. A receive buffer is also allocated for each
184 for a higher number of receive descriptors may be denied. In this
192 This value delays the generation of receive interrupts in units of 1.024
197 may be set too high, causing the driver to run out of available receive
214 receive interrupt is generated. Useful only if RxIntDelay is non-zero,
Dcan.txt14 3.1 receive lists
32 4.2.5 Broadcast Manager receive filter timers
33 4.2.6 Broadcast Manager multiplex message receive filter
83 receive raw CAN frames, directly to/from the controller hardware.
167 3.1 receive lists
173 high efficient receive lists for this reason. If e.g. a user space
180 To optimize the CPU usage at runtime the receive lists are split up
198 example (2) as it would receive in example (1) there is need for
430 - The socket does not receive its own sent frames (in loopback mode)
456 receive filters for each open socket separately:
[all …]
Dphonet.txt9 receive and send messages from/to the modem, or any other external
62 only send and receive Phonet packets.
94 2^10 object IDs available, and can send and receive packets with any
Dproc_net_tcp.txt24 | |----------------------> receive-queue
Dipvlan.txt34 that in L3 mode the slaves wont receive any multicast / broadcast traffic.
49 will not receive nor can send multicast / broadcast traffic.
Dnetlink_mmap.txt9 overhead of unicast receive and transmit operations. Some netlink subsystems
51 On kernel side, in order to make use of memory mapped I/O on receive, the
186 to invoke recvmsg() to receive the message and release
281 /* Frame queued to socket receive queue */
Dtimestamping.txt17 reading the looped packet receive timestamp.
30 same is true for all early receive timestamp options.
62 requested by a particular socket, such as when receive timestamping is
71 kernel receive stack.
158 are already supported unconditionally on all packets with receive
170 charged to the socket's receive budget (SO_RCVBUF) and delivers
277 set and with a msg_control buffer sufficiently large to receive the
Dspider_net.txt18 The receive (RX) ring is a circular linked list of RX descriptors,
28 to receive data from the hardware. A "full" descriptor has data in it,
35 buffers. These are all marked "empty", ready to receive data. This
65 then mark the descr as "empty", ready to receive data. Thus, when there
Dframerelay.txt16 activate/deactivate and dlci_config. The DLCI supplies a receive function
Dnetdev-features.txt164 This requests that the NIC receive all possible frames, including errored
166 bad packets on it. Some NICs may receive more packets if also put into normal
Ddriver.txt88 not receive or transmit any data. All in flight packets must
DLICENSE.qlcnic34 this service if you wish), that you receive source code or can get it
45 you have. You must make sure that they, too, receive or can get the
90 source code as you receive it, in any medium, provided that you
216 all those who receive copies directly or indirectly through you, then
DLICENSE.qlge34 this service if you wish), that you receive source code or can get it
45 you have. You must make sure that they, too, receive or can get the
90 source code as you receive it, in any medium, provided that you
216 all those who receive copies directly or indirectly through you, then
Dipvs-sysctl.txt192 of incoming packets that a connection needs to receive before
241 Kernels with this sync_version entry are able to receive messages
Dip-sysctl.txt287 valid "receive only" state for an un-orphaned connection, an
396 If set, TCP performs receive buffer auto-tuning, attempting to
493 min: Minimal size of receive buffer used by TCP sockets.
498 default: initial size of receive buffer used by TCP sockets.
504 max: maximal size of receive buffer allowed for automatically
507 automatic tuning of that socket's receive buffer size, in which
676 not receive a window scaling option from them.
735 Minimal size of receive buffer used by UDP sockets in moderation.
1126 with the hope we will receive reply for our request and
1746 provides the ability to send and receive authenticated chunks and is
[all …]
Dl2tp.txt101 referenced tunnel id. This hooks up the UDP receive path via
127 RECVSEQ - 0 => receive packet sequence numbers are optional
128 1 => drop receive packets without sequence numbers
Dvortex.txt152 short period if they receive a PAUSE frame from the link partner.
179 The driver's interrupt service routine can handle many receive and
210 decrease in throughput for send(). There is no effect upon receive
Dnfc.txt64 * data_exchange - send data and receive the response (transceive operation)
Dtlan.txt52 0x02 Turn on receive debugging messages.
Drxrpc.txt8 receive data, aborts and errors.
250 Any messages waiting in the receive queue for that call will be discarded.
286 the receive queue, then recvmsg will keep working through them until:
662 Any packets waiting in the socket's receive queue will be discarded if
932 The size of the receive window in packets. This is the maximum number of
938 The maximum packet MTU size that we're willing to receive in bytes. This
Ddecnet.txt124 there will be a routing daemon to send and receive routing messages for
208 will simply set themselves into promiscuous mode in order to receive
Dixgbe.txt109 frames are generated when the receive packet buffer crosses a predefined
124 Supports advanced filters that direct receive packets by their flows to
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Ddesignware-i2s.txt12 one for receive.
13 - dma-names : "tx" for the transmit channel, "rx" for the receive channel.
Dadi,axi-i2s.txt13 receive.
14 - dma-names : "tx" for the transmit channel, "rx" for the receive channel.
Dfsl-sai.txt42 receiver will send and receive data by following
48 receive data by following their own bit clocks and
54 transimitter and receiver will send and receive data by following clocks
Dtas2552.txt17 tas2552 can receive it's reference clock via MCLK, BCLK, IVCLKIN pin or use the
Drockchip-spdif.txt4 processor to receive and transmit digital audio via an coaxial cable or
Dfsl,spdif.txt4 processor to receive and transmit digital audio via an coaxial cable or
Dfsl,esai.txt31 - fsl,fifo-depth : The number of elements in the transmit and receive
Dfsl,ssi.txt29 - fsl,fifo-depth: The number of elements in the transmit and receive FIFOs.
/linux-4.4.14/drivers/staging/rdma/hfi1/
DKconfig33 This option toggles the prescanning of the receive queue for
36 After the prescanning step, the receive queue is processed as
/linux-4.4.14/Documentation/devicetree/bindings/ata/
Dimx-sata.txt20 - fsl,receive-eq-mdB : receive equalisation, in milli-decibels
/linux-4.4.14/Documentation/networking/caif/
DLinux-CAIF.txt69 CAIF payload with receive and transmit functions.
73 to the called function (except for framing layers' receive function)
151 layer->up->receive(layer->up, packet);
162 Net device and Socket implement the 'receive()' function defined by
164 receive of packets is handled as by the rest of the layers: the 'dn->transmit()'
Dspi_porting.txt33 you a chance to set up your hardware to be ready to receive
141 * receive the data from the master SPI. */
153 * the master that you are ready to receive the data from the master
/linux-4.4.14/drivers/net/ethernet/ibm/emac/
DKconfig11 int "Number of receive buffers"
35 Additional receive skb headroom. Note, that driver
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Dqcom,msm-uartdm.txt4 transmit and/or receive channels can be offloaded to a dma-engine. From a
27 - dmas: Should contain dma specifiers for transmit and receive channels
28 - dma-names: Should contain "tx" for transmit and "rx" for receive channels
Dnxp,lpc1850-uart.txt15 and named "rx" for receive.
Domap_serial.txt21 - dma-names : "rx" for receive channel, "tx" for transmit channel.
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dmarvell-orion-net.txt45 - marvell,rx-queue-size: size of the receive ring buffer.
46 - marvell,rx-sram-addr: address of receive descriptor buffer located in SRAM.
47 - marvell,rx-sram-size: size of receive descriptor buffer located in SRAM.
Dsamsung-sxgbe.txt10 trasmit DMA interrupts, receive DMA interrupts and lpi interrupt.
13 index 1 to 25 - 8 variable trasmit interrupts, variable 16 receive interrupts
Dethernet.txt22 - rx-fifo-depth: the size of the controller's receive fifo in bytes. This
23 is used for components that can have configurable receive fifo sizes,
Dbrcm,systemport.txt19 - systemport,num-rxq: number of HW receive queues, an integer
Daltera_tse.txt22 - rx-fifo-depth: MAC receive FIFO buffer depth in bytes
Dfsl-tsec-phy.txt52 transmit, the second is receive, and the third is error.
/linux-4.4.14/drivers/s390/crypto/
Dap_bus.h220 void (*receive)(struct ap_device *, struct ap_message *, member
250 ap_msg->receive = NULL; in ap_init_message()
Dzcrypt_msgtype6.c924 ap_msg.receive = zcrypt_msgtype6_receive; in zcrypt_msgtype6_modexpo()
968 ap_msg.receive = zcrypt_msgtype6_receive; in zcrypt_msgtype6_modexpo_crt()
1012 ap_msg.receive = zcrypt_msgtype6_receive; in zcrypt_msgtype6_send_cprb()
1054 ap_msg.receive = zcrypt_msgtype6_receive_ep11; in zcrypt_msgtype6_send_ep11_cprb()
1098 ap_msg.receive = zcrypt_msgtype6_receive; in zcrypt_msgtype6_rng()
Dap_bus.c570 ap_msg->receive(ap_dev, ap_msg, ap_dev->reply); in ap_sm_recv()
662 ap_msg->receive(ap_dev, ap_msg, NULL); in ap_sm_write()
980 BUG_ON(!ap_msg->receive); in ap_queue_message()
1344 ap_msg->receive(ap_dev, ap_msg, NULL); in __ap_flush_queue()
1350 ap_msg->receive(ap_dev, ap_msg, NULL); in __ap_flush_queue()
Dzcrypt_msgtype50.c440 ap_msg.receive = zcrypt_cex2a_receive; in zcrypt_cex2a_modexpo()
486 ap_msg.receive = zcrypt_cex2a_receive; in zcrypt_cex2a_modexpo_crt()
/linux-4.4.14/drivers/spi/
Dspi-fsl-spi.h35 __be32 receive; member
Dspi-fsl-espi.c36 __be32 receive; /* 0x014 - eSPI receive FIFO access register*/ member
550 rx_data = mpc8xxx_spi_read_reg(&reg_base->receive); in fsl_espi_cpu_irq()
555 rx_data_8 = in_8((u8 *)&reg_base->receive); in fsl_espi_cpu_irq()
/linux-4.4.14/include/linux/
Dif_frad.h64 void (*receive)(struct sk_buff *skb, struct net_device *); member
Dif_team.h105 rx_handler_result_t (*receive)(struct team *team, member
/linux-4.4.14/include/uapi/linux/
Datmlec.h89 unsigned char receive; /* 1= receive vcc, 0 = send vcc */ member
/linux-4.4.14/drivers/staging/wilc1000/
DKconfig20 for the receive buffer. The driver will allocate the RX buffer
28 for the receive buffer. The driver will allocate the RX buffer
/linux-4.4.14/drivers/isdn/hisax/
Dhfc_2bs0.c331 int receive, transmit, count = 5; in main_irq_hfc() local
342 receive = 0; in main_irq_hfc()
352 receive = 1; in main_irq_hfc()
355 if (receive || (bcs->mode == L1_MODE_TRANS)) { in main_irq_hfc()
373 receive = 1; in main_irq_hfc()
393 if ((receive || transmit) && count) in main_irq_hfc()
Dhfc_pci.c454 int receive, count = 5; in main_rec_hfcpci() local
502 receive = 1; in main_rec_hfcpci()
504 receive = 0; in main_rec_hfcpci()
506 receive = hfcpci_empty_fifo_trans(bcs, bz, bdata); in main_rec_hfcpci()
508 receive = 0; in main_rec_hfcpci()
510 if (count && receive) in main_rec_hfcpci()
832 int receive, count = 5; in receive_emsg() local
914 receive = 1; in receive_emsg()
916 receive = 0; in receive_emsg()
918 receive = 0; in receive_emsg()
[all …]
Dhfc_2bds0.c356 int receive, count = 5; in main_rec_2bds0() local
393 receive = 1; in main_rec_2bds0()
395 receive = 0; in main_rec_2bds0()
397 receive = 0; in main_rec_2bds0()
399 if (count && receive) in main_rec_2bds0()
Darcofi.c73 if (cs->dc.isac.arcofi_list->receive) { in arcofi_fsm()
/linux-4.4.14/Documentation/hid/
Duhid.txt51 That is, you might put your device asleep unless you receive the UHID_OPEN
52 event. If you receive the UHID_OPEN event, you should start I/O. If the last
53 user closes the HID device, you will receive an UHID_CLOSE event. This may be
55 reference-counting in user-space. That is, you will never receive multiple
96 may still be pending messages that you can receive with read() but no further
107 If you receive a UHID_GET_REPORT request you must answer with this request.
Dhidraw.txt15 which send and receive data in a way that is inconsistent with their report
/linux-4.4.14/Documentation/accounting/
Dtaskstats.txt50 receive buffer sizes.
156 unnecessarily receive large structures whose fields are of no interest, then
169 - increase the receive buffer sizes for the netlink sockets opened by
170 listeners to receive exit data.
178 indicated overflow of receive buffers, it should take measures to handle the
/linux-4.4.14/Documentation/devicetree/bindings/spi/
Dspi-meson.txt7 receive buffer.
Dspi_pl022.txt23 receive.
Dqcom,spi-qup.txt40 receive.
Dspi-samsung.txt24 named "tx" for transmit and named "rx" for receive.
Dspi-bus.txt67 Now the value that spi-tx-bus-width and spi-rx-bus-width can receive is
/linux-4.4.14/include/net/caif/
Dcaif_layer.h179 int (*receive)(struct cflayer *layr, struct cfpkt *cfpkt); member
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dsi4713.txt3 The Silicon Labs Si4713 is an FM radio transmitter with receive power scan
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Ducc.txt24 - rx-clock-name: the UCC receive clock source
37 - rx-clock : represents the UCC receive clock source.
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Drenesas,mmcif.txt21 receive DMA channel.
Dexynos-dw-mshc.txt31 in transmit mode and CIU clock phase shift value in receive mode for single
36 in transmit mode and CIU clock phase shift value in receive mode for double
/linux-4.4.14/Documentation/
DIPMI.txt111 I2C kernel driver's SMBus interfaces to send and receive IPMI messages
235 You should look at the receive type and handle the message
276 look at the receive type, too.
288 EMSGSIZE error and the driver will leave the data in the receive
295 command. If the response is not receive in the IPMI-specified 5
300 In kernelland, after you receive a message and are done with it, you
306 that lets you supply the smi and receive message. This is useful for
317 commands that other things on the IPMB bus have sent you). To receive
321 To receive events, you must call ipmi_set_gets_events() and set the
325 for events, they will all receive all events that come in.
[all …]
Dio_ordering.txt27 In the case above, the device may receive newval2 before it receives newval,
Dmd-cluster.txt73 is used to inform the receive node that a node wants to communicate.
77 1. receive status
Dlockup-watchdogs.txt44 does not receive any hrtimer interrupt during that time the
/linux-4.4.14/drivers/net/team/
Dteam_mode_activebackup.c120 .receive = ab_receive,
Dteam.c534 !team->mode->ops->receive) in team_adjust_ops()
535 team->ops.receive = team_dummy_receive; in team_adjust_ops()
537 team->ops.receive = team->mode->ops->receive; in team_adjust_ops()
733 res = team->ops.receive(team, port, skb); in team_handle_frame()
/linux-4.4.14/Documentation/thermal/
Dx86_pkg_temperature_thermal21 user mode can receive notification via thermal notification mechanism and can
/linux-4.4.14/arch/mn10300/kernel/
Dgdb-io-serial-low.S28 # GDB stub serial receive interrupt entry point
Dgdb-io-ttysm-low.S28 # GDB stub serial receive interrupt entry point
Dmn10300-serial-low.S59 # serial port receive interrupt virtual DMA entry point
/linux-4.4.14/drivers/net/ethernet/marvell/
DKconfig103 transmit and receive rings.
138 transmit and receive rings.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dprimecell.txt21 Devices with exactly one receive and transmit channel shall name
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-fpga-manager33 * write = FPGA ready to receive image data
Dsysfs-driver-hid-roccat-kone8 processed to receive the real dpi value.
33 further usage in other programs. To receive the real version
Dsysfs-class-net-statistics59 Indicates the number of receive FIFO errors seen by this
88 due to lack of capacity in the receive side. See the network
Dsysfs-class-net-queues17 processed by this particular network device receive queue.
Ddev-kmsg32 Every read() will receive the next available record. If no more
Dsysfs-class-net-cdc_ncm7 than this to tx_max, allowing the device to receive
/linux-4.4.14/drivers/scsi/
D53c700.scr30 ABSOLUTE StatusAddress = 0 ; Addr to receive status return
31 ABSOLUTE ReceiveMsgAddress = 0 ; Addr to receive msg
185 ; receive it correctly
D53c700_d.h_shipped33 ABSOLUTE StatusAddress = 0 ; Addr to receive status return
34 ABSOLUTE ReceiveMsgAddress = 0 ; Addr to receive msg
248 ; receive it correctly
/linux-4.4.14/Documentation/scsi/
Dlibsas.txt76 attached_sas_addr -- set this when you (LLDD) receive an
368 receive SMP responses.
379 4. Read the amount of data you expect to receive for the frame you built.
380 If you receive different amount of data you expected to receive,
DLICENSE.qla4xxx35 this service if you wish), that you receive source code or can get it
46 you have. You must make sure that they, too, receive or can get the
91 source code as you receive it, in any medium, provided that you
217 all those who receive copies directly or indirectly through you, then
DLICENSE.qla2xxx36 this service if you wish), that you receive source code or can get it
47 you have. You must make sure that they, too, receive or can get the
92 source code as you receive it, in any medium, provided that you
218 all those who receive copies directly or indirectly through you, then
/linux-4.4.14/drivers/scsi/libsas/
DKconfig46 Allows sas hosts to receive SMP frames. Selecting this
/linux-4.4.14/Documentation/sysctl/
Dnet.txt95 The default setting of the socket receive buffer in bytes.
100 The maximum receive socket buffer size in bytes.
104 Allow processes to receive tx timestamps looped together with the original
283 The TIPC protocol now has a tunable for the receive memory, similar to the
/linux-4.4.14/Documentation/devicetree/bindings/dma/xilinx/
Dxilinx_dma.txt4 is to receive from the device.
Dxilinx_vdma.txt4 to receive from the video device.
/linux-4.4.14/drivers/atm/
DKconfig76 receive (RX) direction.
121 Burst sixteen words at once in the receive direction. This may work
128 Burst eight words at once in the receive direction. This may work
136 Burst four words at once in the receive direction. This is the
144 Burst two words at once in the receive direction. You may want to
/linux-4.4.14/drivers/net/hamradio/
DKconfig42 radio. If you say Y here, you will be able to send and receive AX.25
54 modem), in order to send and receive AX.25 packet radio network
108 Some transmitters feed the transmitted signal back to the receive
Dbaycom_epp.c561 static int receive(struct net_device *dev, int cnt) in receive() function
693 if (receive(dev, cnt)) in epp_bh()
735 if (receive(dev, cnt)) in epp_bh()
746 if (receive(dev, 1)) in epp_bh()
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dti-dma-crossbar.txt9 - dma-requests: Number of DMA requests the crossbar can receive
/linux-4.4.14/drivers/net/ethernet/adi/
DKconfig51 int "Number of receive buffer packets"
/linux-4.4.14/Documentation/mtd/
Dspi-nor.txt15 receive bytes (Tx and Rx). Therefore, we must define a new layering scheme under
/linux-4.4.14/Documentation/infiniband/
Duser_mad.txt36 MADs are received using read(). The receive side now supports
72 If a send times out, a receive will be generated with mad.status set
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dhead.S462 ; 115.2kbaud for both transmit and receive
496 ; 115.2kbaud for both transmit and receive
531 ; 115.2kbaud for both transmit and receive
567 ; 115.2kbaud for both transmit and receive
/linux-4.4.14/drivers/infiniband/
DKconfig21 userspace processes to send and receive MADs. You will also
/linux-4.4.14/Documentation/filesystems/
Dsharedsubtree.txt119 2c) A private mount does not forward or receive propagation.
300 receive or forward any propagation events.
305 receive or forward any propagation events and cannot
479 are created and mounted at dentry 'b' on all mounts that receive
488 are created and mounted at dentry 'b' on all mounts that receive
497 receive propagation from mount 'B'. A new propagation tree is created
506 create new mounts that get mounted on the mounts that receive
547 'b' on mounts that receive propagation from mount 'B' and does not have
907 be attached to each of the mounts that receive
/linux-4.4.14/arch/arm/boot/dts/
Dimx6q-hummingboard.dts57 fsl,receive-eq-mdB = <3000>;
/linux-4.4.14/net/bridge/
DKconfig57 receive and forward traffic based on VLAN information in the packet
/linux-4.4.14/drivers/rapidio/
DKconfig19 enable and a Input port receive enable. The recommended state
/linux-4.4.14/net/can/
DKconfig29 To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dcros-ec.txt22 time to wake up from sleep before they can receive SPI transfers at a high
/linux-4.4.14/arch/cris/boot/rescue/
Dkimagerescue.S82 ; and receive
Dhead_v10.S250 move.b $r0, [SERBAUD] ; 115.2kbaud for both transmit and receive
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-pyra8 processed to receive the real dpi value.
33 further usage in other programs. To receive the real version
Dsysfs-driver-hid-roccat-kovaplus47 further usage in other programs. To receive the real version
/linux-4.4.14/Documentation/vm/
Dovercommit-accounting20 pages but will receive errors on memory allocation as
/linux-4.4.14/Documentation/sound/alsa/soc/
DDAI.txt47 receive the audio data. Bit clock usually varies depending on sample rate
/linux-4.4.14/fs/cifs/
Dtransport.c538 mid_receive_t *receive, mid_callback_t *callback, in cifs_call_async() argument
563 mid->receive = receive; in cifs_call_async()
/linux-4.4.14/Documentation/connector/
Dconnector.txt118 If we receive a message and its sequence number is not equal to one we
119 are expecting, then it is a new message. If we receive a message and
/linux-4.4.14/Documentation/prctl/
Dno_new_privs.txt37 setuid(2) and receive SCM_RIGHTS datagrams.
/linux-4.4.14/Documentation/dvb/
Davermedia.txt24 The purpose of an Analogue TV is to receive and display an
35 * Tune the receiver to receive a broadcast signal
58 * Tune the received to receive a broadcast signal.
/linux-4.4.14/Documentation/serial/
Dserial-rs485.txt79 /* Set this flag if you want to receive data even whilst sending data */
Dn_gsm.txt75 - and to use gnokii to send / receive SMS on ttygsm1
Dtty.txt63 If not defined, the process will receive an EIO
69 process will receive an EIO error. May sleep.
247 minimal impact as most receive logic uses the flip buffers and they only
/linux-4.4.14/Documentation/devicetree/bindings/reset/
Dreset.txt8 Hardware blocks typically receive a reset signal. This signal is generated by
/linux-4.4.14/Documentation/i2c/
Di2c-protocol29 Simple receive transaction
/linux-4.4.14/Documentation/fb/
Ddeferred_io.txt66 device. You receive the pagelist which is the list of pages that were written
/linux-4.4.14/Documentation/mic/
Dscif_overview.txt81 /* Send and receive short messages */
/linux-4.4.14/net/
DKconfig105 overhead in the transmit and receive paths.
140 reach the outside and can receive replies. It is even possible to
293 The network stack has to drop packets when a receive processing CPU's
/linux-4.4.14/drivers/net/hyperv/
Dhyperv_net.h971 } receive; member
1122 struct rndis_flowspec receive; member
/linux-4.4.14/net/mac80211/
DKconfig90 packet receive/transmit events.
126 easier debugging of problems in the transmit and receive
/linux-4.4.14/Documentation/sound/alsa/
Dhdspm.txt36 transmission/receive-mode , only 28 are transmitted/received
44 transmission/receive-mode , only 14 are transmitted/received
/linux-4.4.14/Documentation/ptp/
Dptp.txt50 ancillary clock features. User space can receive time stamped
/linux-4.4.14/drivers/s390/net/
DKconfig46 Select this option if you want to be able to receive SMSG messages
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei-client-bus.txt8 MEI misc character device is useful for dedicated applications to send and receive
/linux-4.4.14/Documentation/ABI/stable/
Dfirewire-cdev74 buffer which is large enough to receive the largest event that
/linux-4.4.14/drivers/net/ethernet/realtek/
DKconfig92 reset sequence, in the face of severe receive errors. This "new"
/linux-4.4.14/Documentation/watchdog/
Dhpwdt.txt58 Now, the hpwdt can successfully receive and source the NMI and provide a log
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/
Ddsi.txt38 driving a 2-DSI panel whose 2 links need receive command simultaneously.
/linux-4.4.14/arch/powerpc/platforms/pseries/
DKconfig70 to receive events.
/linux-4.4.14/Documentation/usb/
Dgadget_hid.txt84 Send and receive HID reports
108 gadget and you should receive the host answer, corresponding
Derror-codes.txt160 processing, devices may receive such fault reports for every request.
/linux-4.4.14/drivers/staging/rtl8192u/
Dcopying24 this service if you wish), that you receive source code or can get it
35 you have. You must make sure that they, too, receive or can get the
80 source code as you receive it, in any medium, provided that you
206 all those who receive copies directly or indirectly through you, then
/linux-4.4.14/tools/usb/usbip/
DCOPYING24 this service if you wish), that you receive source code or can get it
35 you have. You must make sure that they, too, receive or can get the
80 source code as you receive it, in any medium, provided that you
206 all those who receive copies directly or indirectly through you, then
/linux-4.4.14/drivers/staging/rtl8192e/
Dlicense30 wish), that you receive source code or can get it if you want it, that you
41 must make sure that they, too, receive or can get the source code. And you
84 as you receive it, in any medium, provided that you conspicuously and
208 receive copies directly or indirectly through you, then the only way you
/linux-4.4.14/
DCOPYING40 this service if you wish), that you receive source code or can get it
51 you have. You must make sure that they, too, receive or can get the
96 source code as you receive it, in any medium, provided that you
222 all those who receive copies directly or indirectly through you, then
/linux-4.4.14/Documentation/hwmon/
Dw8379377 slow down all controlled fans, this means one fan can receive different
Dadm924059 measurement update rate and will receive cached data from the most
/linux-4.4.14/Documentation/driver-model/
Dclass.txt60 from the class and re-added, it will receive a different enumerated
/linux-4.4.14/drivers/staging/unisys/Documentation/
Dproc-entries.txt44 virtnic module, including interrupt information, send and receive
/linux-4.4.14/drivers/staging/fsl-mc/
DREADME.txt74 on data, such as packet transmit/receive, are not mediated by
337 other drivers such as the Ethernet driver to receive and transmit data.
/linux-4.4.14/Documentation/fpga/
Dfpga-mgr.txt160 The .write_init function will prepare the FPGA to receive the image data.
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dam33xx-usb.txt48 - dma-names: specifies the names of the channels. Use "rxN" for receive
/linux-4.4.14/Documentation/cgroups/
Ddevices.txt16 never receive a device access which is denied by its parent.
/linux-4.4.14/drivers/net/wan/
Ddlci.c480 dlp->receive = dlci_receive; in dlci_setup()
/linux-4.4.14/net/netfilter/ipvs/
DKconfig127 in a round-robin manner. Servers with higher weights receive
264 allow destinations to receive more connections, the table is
/linux-4.4.14/drivers/isdn/hardware/mISDN/
Dhfcpci.c615 int receive = 0, count = 5; in main_rec_hfcpci() local
658 receive = 1; in main_rec_hfcpci()
660 receive = 0; in main_rec_hfcpci()
665 receive = 0; in main_rec_hfcpci()
666 if (count && receive) in main_rec_hfcpci()
/linux-4.4.14/Documentation/filesystems/nfs/
Dknfsd-stats.txt78 receive some data from an NFS transport.
/linux-4.4.14/drivers/tty/
Dn_gsm.c231 void (*receive)(struct gsm_mux *gsm, u8 ch); member
2099 gsm->receive = gsm0_receive; in gsm_activate_mux()
2101 gsm->receive = gsm1_receive; in gsm_activate_mux()
2290 gsm->receive(gsm, *dp); in gsmld_receive_buf()
/linux-4.4.14/Documentation/scheduler/
Dsched-deadline.txt47 "deadline", to schedule tasks. A SCHED_DEADLINE task should receive
418 This means that non -deadline tasks will receive at least 5% of the CPU time,
419 and that -deadline tasks will receive their runtime with a guaranteed
423 deterministically guarantee that -deadline tasks will receive their runtime
/linux-4.4.14/drivers/net/can/
DKconfig60 This option adds two LED triggers for packet receive and transmit
/linux-4.4.14/drivers/s390/char/
DKconfig168 Select this option if you want to be able to receive records collected
/linux-4.4.14/Documentation/video4linux/
Dsi4713.txt13 The chip also allows integrated receive power scanning to identify low signal
/linux-4.4.14/Documentation/input/
Dsentelic.txt416 That is, when the device is in MFMC mode, the host will receive
427 FSP will send out enable/disable packet when FSP receive PS/2 enable/disable
428 command. Host will receive the packet which Middle, Right, Left button will
806 bit 2 and 3. That is, if any of those bit is 1, host will receive
/linux-4.4.14/Documentation/pcmcia/
Ddriver-changes.txt51 being; they might receive a shared IRQ nonetheless.

12