Home
last modified time | relevance | path

Searched refs:receive (Results 1 – 25 of 241) sorted by relevance

12345678910

/linux-3.4.99/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>;
/linux-3.4.99/drivers/input/serio/
Dlibps2.c188 int receive = (command >> 8) & 0xf; in __ps2_command() local
192 if (receive > sizeof(ps2dev->cmdbuf)) { in __ps2_command()
204 ps2dev->cmdcnt = receive; in __ps2_command()
205 if (receive && param) in __ps2_command()
206 for (i = 0; i < receive; i++) in __ps2_command()
207 ps2dev->cmdbuf[(receive - 1) - i] = param[i]; in __ps2_command()
239 for (i = 0; i < receive; i++) in __ps2_command()
240 param[i] = ps2dev->cmdbuf[(receive - 1) - i]; in __ps2_command()
/linux-3.4.99/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()
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()
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()
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.c237 static int receive(struct sk_buff *skb, struct net_device *dev, in receive() function
249 if (!caifd || !caifd->layer.up || !caifd->layer.up->receive || in receive()
260 err = caifd->layer.up->receive(caifd->layer.up, pkt); in receive()
276 .func = receive,
347 *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.c45 return layr->up->receive(layr->up, pkt); in cfusbl_receive()
96 this->layer.receive = cfusbl_receive; in cfusbl_create()
/linux-3.4.99/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.
/linux-3.4.99/Documentation/networking/caif/
DLinux-CAIF.txt51 The user of the API has to implement two callbacks for receive
53 The receive callback gives a CAIF packet as a SKB. The control
92 with receive and transmit functions.
95 CAIF payload with receive and transmit functions.
99 to the called function (except for framing layers' receive functions
184 layer->up->receive(layer->up, packet);
195 Net device and Socket implement the 'receive()' function defined by
197 receive of packets is handled as by the rest of the layers: the 'dn->transmit()'
/linux-3.4.99/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
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 …]
/linux-3.4.99/include/linux/
Dif_macvlan.h63 int (*receive)(struct sk_buff *skb); member
93 int (*receive)(struct sk_buff *skb),
Datmlec.h96 unsigned char receive; /* 1= receive vcc, 0 = send vcc */ member
/linux-3.4.99/drivers/net/ethernet/ibm/emac/
DKconfig11 int "Number of receive buffers"
35 Additional receive skb headroom. Note, that driver
/linux-3.4.99/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()

12345678910