/linux-4.4.14/drivers/net/irda/ |
D | kingsun-sir.c | 118 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()
|
D | stir4200.c | 179 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 …]
|
D | ks959-sir.c | 197 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()
|
D | ksdazzle-sir.c | 163 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()
|
D | mcs7780.h | 120 int receiving; member
|
D | mcs7780.c | 717 mcs->receiving = 0; in mcs_net_open()
|
/linux-4.4.14/drivers/virt/ |
D | Kconfig | 28 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/ |
D | cxgb3i.txt | 16 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
|
D | libsas.txt | 284 PORTE_BYTES_DMAED -- on receiving an IDENTIFY/FIS frame 285 PORTE_BROADCAST_RCVD -- on receiving a primitive
|
D | ChangeLog.megaraid | 450 no BIOS to start the controller. The FW starts to boot after receiving
|
D | ChangeLog.lpfc | 87 * 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/ |
D | st-rc.txt | 11 protocol used for receiving remote control signals. rx-mode should
|
/linux-4.4.14/Documentation/devicetree/bindings/sound/ |
D | imx-audio-spdif.txt | 21 - spdif-in : This is a boolean property. If present, the receiving
|
/linux-4.4.14/net/irda/ |
D | Kconfig | 70 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/ |
D | rs485.txt | 18 - rs485-rx-during-tx: empty property that enables the receiving of data even
|
D | atmel-usart.txt | 15 - atmel,use-dma-rx: use of PDC or DMA for receiving data
|
/linux-4.4.14/Documentation/devicetree/bindings/pci/ |
D | hisilicon-pcie.txt | 16 - msi-parent: Should be its_pcie which is an ITS receiving MSI interrupts.
|
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/ |
D | edp.txt | 23 to HPD receiving chip
|
/linux-4.4.14/arch/cris/ |
D | Kconfig | 397 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/ |
D | Kconfig | 35 transmitting and receiving. This memory cannot be used by any other
|
/linux-4.4.14/drivers/media/radio/si470x/ |
D | Kconfig | 13 if you don't want to use the device solely for RDS receiving,
|
/linux-4.4.14/Documentation/networking/ |
D | tuntap.txt | 15 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
|
D | PLIP.txt | 204 That raises the ACK line, triggering an interrupt in the receiving 205 machine. The receiving machine disables interrupts and raises its own ACK
|
D | 3c509.txt | 127 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,
|
D | README.sb1000 | 171 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
|
D | rxrpc.txt | 242 (*) 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
|
D | phonet.txt | 85 The resource field is only used when sending and receiving;
|
D | netconsole.txt | 193 NOTE: if you find that the remote logging agent is not receiving or
|
D | 6pack.txt | 18 that the PC knows at any time if the TNC is receiving data, if a TNC
|
D | timestamping.txt | 4 The interfaces for receiving network packages timestamps are: 313 The calling application is often not interested in receiving the whole
|
D | ppp_generic.txt | 21 For sending and receiving PPP frames, the generic PPP driver calls on 163 algorithms rely on receiving compressed packets in the same order that
|
D | rds.txt | 223 Messages waiting in the receive queue on the receiving socket
|
D | ixgbe.txt | 108 receiving and transmitting pause frames for ixgbe. When TX is enabled, PAUSE
|
D | vortex.txt | 167 for receiving. When a packet arrives, the driver has to decide
|
D | ip-sysctl.txt | 736 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."
|
D | bonding.txt | 351 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
|
D | cs89x0.txt | 301 j) The cs89x0 supports DMA for receiving only. DMA mode is
|
D | arcnet.txt | 528 Buffers 0 and 1 are used for receiving, and Buffers 2 and 3 are for sending.
|
D | can.txt | 427 - The filters are set to exactly one filter receiving everything
|
/linux-4.4.14/drivers/staging/media/lirc/ |
D | TODO.lirc_zilog | 20 receiving button presses again and ir_send worked without error.)
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
D | mpic-msgr.txt | 19 for receiving interrupts. Interrupt-specifier consists of two cells: first
|
/linux-4.4.14/Documentation/arm/ |
D | uefi.txt | 22 The implementation depends on receiving information about the UEFI environment
|
/linux-4.4.14/drivers/block/drbd/ |
D | Kconfig | 63 512 insert data corruption on receiving side
|
/linux-4.4.14/Documentation/usb/ |
D | functionfs.txt | 29 for receiving events and handling setup requests.
|
D | WUSB-Design-overview.txt | 181 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
|
D | gadget-testing.txt | 668 sending or receiving when this configuration is
|
D | power-management.txt | 565 Upon receiving a ClearPortFeature(PORT_POWER) request a USB port is
|
/linux-4.4.14/Documentation/isdn/ |
D | README.audio | 96 When receiving audio data, a kind of bisync protocol is used.
|
D | INTERFACE | 654 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/ |
D | stm.txt | 13 On the receiving end of this STP stream (the decoder side), trace
|
D | tracepoint-analysis.txt | 210 o When receiving an event about a PID, it can record who the parent was so
|
/linux-4.4.14/arch/m68k/ifpsp060/ |
D | CHANGES | 71 Upon receiving a non-zero (failing) return value from
|
/linux-4.4.14/Documentation/networking/caif/ |
D | Linux-CAIF.txt | 72 - When receiving / transmitting CAIF Packets (cfpkt), ownership is passed
|
/linux-4.4.14/drivers/net/ethernet/dec/tulip/ |
D | Kconfig | 82 when the driver is receiving lots of packets from the card. It is
|
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/ |
D | omap-mailbox.txt | 70 (ti,mbox-tx) or for receiving (ti,mbox-rx)
|
/linux-4.4.14/drivers/net/can/ |
D | Kconfig | 20 As only the sending and receiving of CAN frames is implemented, this
|
/linux-4.4.14/Documentation/dvb/ |
D | ci.txt | 72 the application programmer it would be as simple as sending/receiving an
|
D | README.dvb-usb | 176 This is not enough for receiving the complete transport stream of a
|
D | avermedia.txt | 128 tuning, receiving and supplying the MPEG2 data stream is
|
/linux-4.4.14/Documentation/serial/ |
D | driver | 151 Stop receiving characters; the port is in the process of 217 the types of events we are interested in receiving. Relevant
|
D | moxa-smartio | 452 This utility provides data sending and receiving ability of all tty ports,
|
/linux-4.4.14/Documentation/ |
D | md-cluster.txt | 141 the list of ranges which are currently suspended. On receiving
|
D | ntb.txt | 58 * delay\_ms - Specify the delay between receiving a doorbell
|
D | IPMI.txt | 207 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
|
D | email-clients.txt | 7 email clients. The man page for this is quite good. On the receiving
|
D | HOWTO | 398 reason, or don't reply only to the list address. Get used to receiving the
|
D | kernel-docs.txt | 460 socket, receiving, transmitting, forwarding, routing, packets,
|
D | memory-barriers.txt | 1830 being unable to get the lock immediately, or due to receiving an unblocked
|
D | kernel-parameters.txt | 3998 If set to 1, on receiving an ACPI notify event
|
/linux-4.4.14/Documentation/connector/ |
D | connector.txt | 140 be lost due to memory pressure or process' receiving queue overflowed,
|
/linux-4.4.14/Documentation/vm/ |
D | userfaultfd.txt | 140 over it when receiving incoming userfaults. After sending each page of
|
/linux-4.4.14/Documentation/input/ |
D | multi-touch-protocol.txt | 64 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/ |
D | draft-ietf-cipso-ipsecurity-01.txt | 442 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/ |
D | sysfs-block | 77 devices that support receiving integrity metadata.
|
/linux-4.4.14/Documentation/video4linux/ |
D | omap3isp.txt | 59 insist on receiving complete frames. Sensors must thus never send the ISP
|
/linux-4.4.14/Documentation/power/ |
D | suspend-and-cpuhotplug.txt | 197 a regular CPU hotplug operation, upon receiving the CPU_DEAD notification
|
D | pci.txt | 49 requiring the device to be active. After receiving a PME the kernel is supposed
|
/linux-4.4.14/drivers/media/usb/cx231xx/ |
D | cx231xx.h | 239 int receiving; member
|
/linux-4.4.14/Documentation/acpi/ |
D | namespace.txt | 11 receiving ACPI hotplug notification events. For each device object in this
|
/linux-4.4.14/Documentation/arm64/ |
D | booting.txt | 173 initialisation to enable the receiving of maintenance operations on
|
/linux-4.4.14/Documentation/thermal/ |
D | intel_powerclamp.txt | 214 Per-CPU kernel threads are started/stopped upon receiving
|
/linux-4.4.14/Documentation/block/ |
D | data-integrity.txt | 172 is capable of sending/receiving integrity metadata. The IMD will
|
/linux-4.4.14/Documentation/PCI/ |
D | pcieaer-howto.txt | 112 an error. The Root Port, upon receiving an error reporting message,
|
/linux-4.4.14/Documentation/nfc/ |
D | nfc-hci.txt | 246 Workflow receiving an HCI event or command
|
/linux-4.4.14/scripts/ |
D | spelling.txt | 793 receving||receiving
|
/linux-4.4.14/drivers/net/ |
D | Kconfig | 244 device, which instead of receiving packets from a physical media,
|
/linux-4.4.14/drivers/atm/ |
D | Kconfig | 237 Enable receiving of all cells on the ATM link, that do not match
|
/linux-4.4.14/Documentation/i2c/ |
D | writing-clients | 312 Sending and receiving
|
/linux-4.4.14/Documentation/timers/ |
D | NO_HZ.txt | 90 An idle CPU that is not receiving scheduling-clock interrupts is said to
|
/linux-4.4.14/Documentation/development-process/ |
D | 5.Posting | 304 receiving end. Tools like git and quilt have commands to mail out a set of
|
/linux-4.4.14/Documentation/networking/dsa/ |
D | dsa.txt | 27 receiving Ethernet frames from the switch. This is a very common setup for all
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | aic79xx.seq | 1110 * SCB. After receiving the tag, look for the SCB at SCB locations tag and 1492 * If we're not still receiving SCSI data,
|
D | aic7xxx.seq | 187 * setup the phase for receiving messages
|
/linux-4.4.14/Documentation/security/ |
D | Smack.txt | 550 packet has write access to the receiving process and if that is not the case
|
/linux-4.4.14/init/ |
D | Kconfig | 248 of receiving it by a process. If you want to compile and run
|