Searched refs:transmission (Results 1 – 25 of 103) sorted by relevance
12345
| /Linux-v5.4/drivers/staging/pi433/Documentation/ |
| D | pi433.txt | 9 (www.pi433.de). It supports transmission and reception. It can be opened
10 by multiple applications for transmission and reception. While transmit
20 a) transmission
22 Each transmission can take place with a different configuration of the rf
24 takes care, that each transmission takes place with the parameterset of the
25 application, that requests the transmission. To allow the transmission to take
33 the air, the rf module is set to standby, the parameters for transmission gets
34 set, the hardware fifo of the rf chip gets preloaded and the transmission gets
38 transmission cycle ends.
48 interrupted by the transmission thread at any time to insert a transmission cycle.
[all …]
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | firewire-cdev | 18 - Asynchronous request transmission
24 - Isochronous stream transmission and reception
25 - Asynchronous stream transmission and reception
26 - Asynchronous broadcast request transmission
27 - PHY packet transmission and reception
37 an address range, asynchronous response transmission
48 - PHY packet transmission and reception
80 Allocate a DMA buffer for isochronous reception or transmission
85 for transmission, flags = MAP_SHARED, fd = the handle to the
|
| /Linux-v5.4/Documentation/devicetree/bindings/hsi/ |
| D | client-devices.txt | 9 - hsi-rx-mode: Receiver Bit transmission mode ("stream" or "frame")
10 - hsi-tx-mode: Transmitter Bit transmission mode ("stream" or "frame")
12 the transmission mode is the same for receiver and
14 - hsi-speed-kbps: Max bit transmission speed in kbit/s
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | si4713.rst | 17 Basically, it has transmission and signal noise level measurement features.
19 The Si4713 integrates transmit functions for FM broadcast stereo transmission.
26 Users must comply with local regulations on radio frequency (RF) transmission.
126 - power_level - Sets the output power level for signal transmission.
132 - rds_ps_name - Sets the RDS ps name field for transmission.
133 - rds_radio_text - Sets the RDS radio text for transmission.
134 - rds_pi - Sets the RDS PI field for transmission.
135 - rds_pty - Sets the RDS PTY field for transmission.
139 - preemphasis - sets the preemphasis to be applied for transmission.
179 transmission. To do that use S/G_MODULATOR ioctl and configure txsubchans properly.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-led-trigger-netdev | 32 Signal transmission of data on the named network device.
33 If set to 0 (default), the LED will not blink on transmission.
35 in interval to signal transmission.
|
| D | sysfs-class-net-statistics | 115 during transmission by a network device (e.g: because of
128 transmission.
153 Indicates the number of packets dropped during transmission.
162 Indicates the number of packets in error during transmission by
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | ext-ctrls-fm-tx.rst | 19 limiter, RDS transmission and tuning power features.
37 Sets the RDS Programme Identification field for transmission.
40 Sets the RDS Programme Type field for transmission. This encodes up
44 Sets the Programme Service name (PS_NAME) for transmission. It is
56 Sets the Radio Text info for transmission. It is a textual
179 Sets the output power level for signal transmission. Unit is in
|
| /Linux-v5.4/Documentation/networking/ |
| D | mac80211-injection.txt | 33 legacy rate for the transmission (only for devices without own rate control)
37 HT rate for the transmission (only for devices without own rate control).
50 VHT mcs and number of streams used in the transmission (only for devices
|
| D | packet_mmap.txt | 30 transmission, multiple packets can be sent through one system call to get the
35 transmission process, but it isn't everything. At least, if you are capturing
39 enabled. For transmission, check the MTU (Maximum Transmission Unit) used and
90 for capture and transmission. This can be done by mapping the
99 + How to use mmap() directly to improve transmission process
103 [setup] socket() -------> creation of the transmission socket
106 bind() ---------> bind transmission socket with a network interface
110 [transmission] poll() ---------> wait for free packets (optional)
116 [shutdown] close() --------> destruction of the transmission socket and
410 To use one socket for capture and transmission, the mapping of both the
[all …]
|
| /Linux-v5.4/Documentation/sound/cards/ |
| D | hdspm.rst | 18 Audio transmission
21 * number of channels -- depends on transmission mode
32 (Note: Choosing the 56channel mode for transmission or as
41 transmission/receive-mode , only 28 are transmitted/received
50 transmission/receive-mode , only 14 are transmitted/received
183 MADI-transmission (0).
|
| /Linux-v5.4/Documentation/devicetree/bindings/i2c/ |
| D | renesas,iic.txt | 39 due to the absence of automatic transmission registers.
50 specifiers, one for transmission, and one for
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/ |
| D | nokia,n900-ir | 5 - pwms: specifies PWM used for IR signal transmission.
|
| /Linux-v5.4/sound/soc/sprd/ |
| D | Kconfig | 15 is used for sound stream transmission between audio subsystem
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | sprd-mcdt.txt | 4 transmission between audio subsystem and other AP/CP subsystem. It
|
| D | sirf-audio-port.txt | 10 One of the DMA channels will be responsible for transmission (should be
|
| D | brcm,bcm2835-i2s.txt | 11 One of the DMA channels will be responsible for transmission (should be
|
| D | sirf-usp.txt | 10 One of the DMA channels will be responsible for transmission (should be
|
| /Linux-v5.4/arch/arm/include/debug/ |
| D | at91.S | 30 tst \rd, #AT91_DBGU_TXEMPTY @ DBGU_TXEMPTY = 1 when transmission complete
|
| /Linux-v5.4/Documentation/sound/designs/ |
| D | tracepoints.rst | 30 In a design of ALSA PCM core, data transmission is abstracted as PCM substream.
31 Applications manage PCM substream to maintain data transmission for PCM frames.
32 Before starting the data transmission, applications need to configure PCM
111 a care of hardware design or data transmission protocol.
|
| /Linux-v5.4/net/can/j1939/ |
| D | transport.c | 254 if (!session->transmission) in __j1939_session_drop()
498 session->transmission == transmitter) in j1939_session_get_by_addr_locked()
1062 !session->transmission, in __j1939_session_cancel()
1094 if (session->transmission) in j1939_tp_txtimer()
1147 if (!session->transmission) { in j1939_session_completed()
1380 if (session->transmission) { in j1939_xtp_rx_cts_one()
1492 session->transmission); in j1939_session_activate()
1585 if (!session->transmission) { in j1939_xtp_rx_rts_session_active()
1666 if (cmd != J1939_TP_CMD_BAM && !session->transmission) { in j1939_xtp_rx_rts()
1790 if (!session->transmission) in j1939_xtp_rx_dat_one()
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/display/bridge/ |
| D | thine,thc63lvdm83d.txt | 5 transmission between a host and a flat panel.
|
| /Linux-v5.4/Documentation/devicetree/bindings/dma/ |
| D | fsl-edma.txt | 19 per transmission interrupt, total 16 channel interrupt and 1
42 "edma-tx" - the transmission interrupt
|
| /Linux-v5.4/Documentation/devicetree/bindings/spi/ |
| D | qcom,spi-qcom-qspi.txt | 4 wire transmission modes for read/write access to slaves such as NOR flash.
|
| /Linux-v5.4/Documentation/driver-api/nfc/ |
| D | nfc-pn544.rst | 9 The PN544 is an integrated transmission module for contactless
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | rc-core.rst | 31 The infrared transmission is done by blinking a infrared emitter using a
36 In other words, a typical IR transmission can be viewed as a sequence of
|
12345
