Home
last modified time | relevance | path

Searched refs:receiving (Results 1 – 95 of 95) sorted by relevance

/linux-4.4.14/drivers/net/irda/
Dkingsun-sir.c118 int receiving; member
209 kingsun->receiving = 0; in kingsun_rcv_irq()
218 kingsun->receiving = 0; in kingsun_rcv_irq()
237 kingsun->receiving = in kingsun_rcv_irq()
262 kingsun->receiving = 0; in kingsun_net_open()
367 kingsun->receiving = 0; in kingsun_net_close()
410 irq->ifr_receiving = kingsun->receiving; in kingsun_net_ioctl()
505 kingsun->receiving = 0; in kingsun_probe()
Dstir4200.c179 int receiving; member
677 stir->receiving = 1; in receive_start()
689 stir->receiving = 0; in receive_stop()
704 if (stir->receiving) { in stir_send()
743 if (stir->receiving) in stir_transmit_thread()
776 if (!stir->receiving && in stir_transmit_thread()
787 stir->receiving = 0; in stir_transmit_thread()
829 if (!stir->receiving) in stir_rcv_irq()
839 stir->receiving = 0; in stir_rcv_irq()
869 stir->receiving = 0; in stir_net_open()
[all …]
Dks959-sir.c197 int receiving; member
442 kingsun->receiving = 0; in ks959_rcv_irq()
451 kingsun->receiving = 0; in ks959_rcv_irq()
478 kingsun->receiving = in ks959_rcv_irq()
503 kingsun->receiving = 0; in ks959_net_open()
621 kingsun->receiving = 0; in ks959_net_close()
662 irq->ifr_receiving = kingsun->receiving; in ks959_net_ioctl()
715 kingsun->receiving = 0; in ks959_probe()
Dksdazzle-sir.c163 int receiving; member
356 kingsun->receiving = 0; in ksdazzle_rcv_irq()
365 kingsun->receiving = 0; in ksdazzle_rcv_irq()
377 kingsun->receiving = in ksdazzle_rcv_irq()
400 kingsun->receiving = 0; in ksdazzle_net_open()
516 kingsun->receiving = 0; in ksdazzle_net_close()
558 irq->ifr_receiving = kingsun->receiving; in ksdazzle_net_ioctl()
653 kingsun->receiving = 0; in ksdazzle_probe()
Dmcs7780.h120 int receiving; member
Dmcs7780.c717 mcs->receiving = 0; in mcs_net_open()
/linux-4.4.14/drivers/virt/
DKconfig28 receiving the shutdown doorbell from a manager partition.
30 4) A kernel interface for receiving callbacks when a managed
/linux-4.4.14/Documentation/scsi/
Dcxgb3i.txt16 On receiving, Chelsio S3 h/w computes and verifies the Header and
34 On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
Dlibsas.txt284 PORTE_BYTES_DMAED -- on receiving an IDENTIFY/FIS frame
285 PORTE_BROADCAST_RCVD -- on receiving a primitive
DChangeLog.megaraid450 no BIOS to start the controller. The FW starts to boot after receiving
DChangeLog.lpfc87 * Fixed issue with receiving PLOGI handling when node is on NPR
334 * rport fixes: when receiving PRLI's, set node/rport role values
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dst-rc.txt11 protocol used for receiving remote control signals. rx-mode should
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dimx-audio-spdif.txt21 - spdif-in : This is a boolean property. If present, the receiving
/linux-4.4.14/net/irda/
DKconfig70 receiving a frame if its own transmit queue is currently empty. This
71 will give a lot of speed improvement when receiving much data since
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Drs485.txt18 - rs485-rx-during-tx: empty property that enables the receiving of data even
Datmel-usart.txt15 - atmel,use-dma-rx: use of PDC or DMA for receiving data
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dhisilicon-pcie.txt16 - msi-parent: Should be its_pcie which is an ITS receiving MSI interrupts.
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/
Dedp.txt23 to HPD receiving chip
/linux-4.4.14/arch/cris/
DKconfig397 used when receiving data.
407 used when receiving data.
432 used when receiving data.
524 used when receiving data.
534 used when receiving data.
/linux-4.4.14/drivers/net/hippi/
DKconfig35 transmitting and receiving. This memory cannot be used by any other
/linux-4.4.14/drivers/media/radio/si470x/
DKconfig13 if you don't want to use the device solely for RDS receiving,
/linux-4.4.14/Documentation/networking/
Dtuntap.txt15 instead of receiving packets from physical media, receives them from
111 file descriptors (queues) to parallelize packets sending or receiving. The
203 Ethernet device, which instead of receiving packets from a physical
DPLIP.txt204 That raises the ACK line, triggering an interrupt in the receiving
205 machine. The receiving machine disables interrupts and raises its own ACK
D3c509.txt127 work during that interrupt cycle. With a status of 0x2011 you are receiving
146 interrupt line. If the device is receiving packets but 'ping' doesn't work,
DREADME.sb1000171 Solution -- First, tell your ISP that you're receiving DoS (Denial of Service)
175 to the "cmconfig" command (uncomment that line). If you're not receiving these
Drxrpc.txt242 (*) When receiving data for a call, recvmsg flags MSG_MORE if there's more
245 (*) When receiving data or messages for a call, MSG_EOR is flagged by recvmsg
260 (*) Sending or receiving errors, aborts and busy notifications.
264 (*) Sending debug requests and receiving debug replies [TODO].
880 The amount of time in milliseconds after receiving a packet with the
890 The amount of time in milliseconds after receiving a new packet before we
Dphonet.txt85 The resource field is only used when sending and receiving;
Dnetconsole.txt193 NOTE: if you find that the remote logging agent is not receiving or
D6pack.txt18 that the PC knows at any time if the TNC is receiving data, if a TNC
Dtimestamping.txt4 The interfaces for receiving network packages timestamps are:
313 The calling application is often not interested in receiving the whole
Dppp_generic.txt21 For sending and receiving PPP frames, the generic PPP driver calls on
163 algorithms rely on receiving compressed packets in the same order that
Drds.txt223 Messages waiting in the receive queue on the receiving socket
Dixgbe.txt108 receiving and transmitting pause frames for ixgbe. When TX is enabled, PAUSE
Dvortex.txt167 for receiving. When a packet arrives, the driver has to decide
Dip-sysctl.txt736 Each UDP socket is able to use the size for receiving data, even if
1113 configured on the receiving interface. When we generate the
1132 receiving answer from the resolved target while decreasing
1600 prior to receiving a response to a previous solicitation."
Dbonding.txt351 is receiving the appropriate ARP traffic.
636 If the receiving slave fails, another slave takes over
637 the MAC address of the failed receiving slave.
1673 machine's aggregate, thus receiving a portion of that hosts incoming
2112 receiving inbound traffic.
2311 striping generally results in peer systems receiving packets out
Dcs89x0.txt301 j) The cs89x0 supports DMA for receiving only. DMA mode is
Darcnet.txt528 Buffers 0 and 1 are used for receiving, and Buffers 2 and 3 are for sending.
Dcan.txt427 - The filters are set to exactly one filter receiving everything
/linux-4.4.14/drivers/staging/media/lirc/
DTODO.lirc_zilog20 receiving button presses again and ir_send worked without error.)
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic-msgr.txt19 for receiving interrupts. Interrupt-specifier consists of two cells: first
/linux-4.4.14/Documentation/arm/
Duefi.txt22 The implementation depends on receiving information about the UEFI environment
/linux-4.4.14/drivers/block/drbd/
DKconfig63 512 insert data corruption on receiving side
/linux-4.4.14/Documentation/usb/
Dfunctionfs.txt29 for receiving events and handling setup requests.
DWUSB-Design-overview.txt181 block or reply is expected back. For sending/receiving command/events, a
343 *Sending and receiving data*
423 Handle/file descriptor for receiving notifications or events. The WA
Dgadget-testing.txt668 sending or receiving when this configuration is
Dpower-management.txt565 Upon receiving a ClearPortFeature(PORT_POWER) request a USB port is
/linux-4.4.14/Documentation/isdn/
DREADME.audio96 When receiving audio data, a kind of bisync protocol is used.
DINTERFACE654 of the skb at the time of receiving it from the linklevel.
748 ISDN_STAT_L1ERR_RECV: Packet lost while receiving.
/linux-4.4.14/Documentation/trace/
Dstm.txt13 On the receiving end of this STP stream (the decoder side), trace
Dtracepoint-analysis.txt210 o When receiving an event about a PID, it can record who the parent was so
/linux-4.4.14/arch/m68k/ifpsp060/
DCHANGES71 Upon receiving a non-zero (failing) return value from
/linux-4.4.14/Documentation/networking/caif/
DLinux-CAIF.txt72 - When receiving / transmitting CAIF Packets (cfpkt), ownership is passed
/linux-4.4.14/drivers/net/ethernet/dec/tulip/
DKconfig82 when the driver is receiving lots of packets from the card. It is
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Domap-mailbox.txt70 (ti,mbox-tx) or for receiving (ti,mbox-rx)
/linux-4.4.14/drivers/net/can/
DKconfig20 As only the sending and receiving of CAN frames is implemented, this
/linux-4.4.14/Documentation/dvb/
Dci.txt72 the application programmer it would be as simple as sending/receiving an
DREADME.dvb-usb176 This is not enough for receiving the complete transport stream of a
Davermedia.txt128 tuning, receiving and supplying the MPEG2 data stream is
/linux-4.4.14/Documentation/serial/
Ddriver151 Stop receiving characters; the port is in the process of
217 the types of events we are interested in receiving. Relevant
Dmoxa-smartio452 This utility provides data sending and receiving ability of all tty ports,
/linux-4.4.14/Documentation/
Dmd-cluster.txt141 the list of ranges which are currently suspended. On receiving
Dntb.txt58 * delay\_ms - Specify the delay between receiving a doorbell
DIPMI.txt207 block of data, even when receiving messages. Otherwise the driver
315 The driver takes care of polling for IPMI events and receiving
327 For receiving commands, you have to individually register commands you
Demail-clients.txt7 email clients. The man page for this is quite good. On the receiving
DHOWTO398 reason, or don't reply only to the list address. Get used to receiving the
Dkernel-docs.txt460 socket, receiving, transmitting, forwarding, routing, packets,
Dmemory-barriers.txt1830 being unable to get the lock immediately, or due to receiving an unblocked
Dkernel-parameters.txt3998 If set to 1, on receiving an ACPI notify event
/linux-4.4.14/Documentation/connector/
Dconnector.txt140 be lost due to memory pressure or process' receiving queue overflowed,
/linux-4.4.14/Documentation/vm/
Duserfaultfd.txt140 over it when receiving incoming userfaults. After sending each page of
/linux-4.4.14/Documentation/input/
Dmulti-touch-protocol.txt64 the full state of each initiated contact has to reside in the receiving
65 end. Upon receiving an MT event, one simply updates the appropriate
/linux-4.4.14/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt442 protected by the receiving host or if acceptance may result in violation of
556 receiving system will handle the CIPSO label. Wrong assumptions may
569 receiving port. Without this label the host, gateway, or router will not
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-block77 devices that support receiving integrity metadata.
/linux-4.4.14/Documentation/video4linux/
Domap3isp.txt59 insist on receiving complete frames. Sensors must thus never send the ISP
/linux-4.4.14/Documentation/power/
Dsuspend-and-cpuhotplug.txt197 a regular CPU hotplug operation, upon receiving the CPU_DEAD notification
Dpci.txt49 requiring the device to be active. After receiving a PME the kernel is supposed
/linux-4.4.14/drivers/media/usb/cx231xx/
Dcx231xx.h239 int receiving; member
/linux-4.4.14/Documentation/acpi/
Dnamespace.txt11 receiving ACPI hotplug notification events. For each device object in this
/linux-4.4.14/Documentation/arm64/
Dbooting.txt173 initialisation to enable the receiving of maintenance operations on
/linux-4.4.14/Documentation/thermal/
Dintel_powerclamp.txt214 Per-CPU kernel threads are started/stopped upon receiving
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt172 is capable of sending/receiving integrity metadata. The IMD will
/linux-4.4.14/Documentation/PCI/
Dpcieaer-howto.txt112 an error. The Root Port, upon receiving an error reporting message,
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt246 Workflow receiving an HCI event or command
/linux-4.4.14/scripts/
Dspelling.txt793 receving||receiving
/linux-4.4.14/drivers/net/
DKconfig244 device, which instead of receiving packets from a physical media,
/linux-4.4.14/drivers/atm/
DKconfig237 Enable receiving of all cells on the ATM link, that do not match
/linux-4.4.14/Documentation/i2c/
Dwriting-clients312 Sending and receiving
/linux-4.4.14/Documentation/timers/
DNO_HZ.txt90 An idle CPU that is not receiving scheduling-clock interrupts is said to
/linux-4.4.14/Documentation/development-process/
D5.Posting304 receiving end. Tools like git and quilt have commands to mail out a set of
/linux-4.4.14/Documentation/networking/dsa/
Ddsa.txt27 receiving Ethernet frames from the switch. This is a very common setup for all
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic79xx.seq1110 * SCB. After receiving the tag, look for the SCB at SCB locations tag and
1492 * If we're not still receiving SCSI data,
Daic7xxx.seq187 * setup the phase for receiving messages
/linux-4.4.14/Documentation/security/
DSmack.txt550 packet has write access to the receiving process and if that is not the case
/linux-4.4.14/init/
DKconfig248 of receiving it by a process. If you want to compile and run