Searched full:channel (Results 1 – 25 of 995) sorted by relevance
12345678910>>...40
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | dma.txt | 4 This is a little-endian 4-channel DMA controller, used in Freescale mpc83xx 17 - DMA channel nodes: 18 - compatible : must include "fsl,elo-dma-channel" 20 - reg : DMA channel specific registers 21 - cell-index : DMA channel index starts at 0. 24 - interrupts : interrupt specifier for DMA channel IRQ 38 dma-channel@0 { 39 compatible = "fsl,mpc8349-dma-channel", "fsl,elo-dma-channel"; 45 dma-channel@80 { 46 compatible = "fsl,mpc8349-dma-channel", "fsl,elo-dma-channel"; [all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | cirrus,ep9301-dma-m2p.yaml | 30 - description: m2p0 channel registers 31 - description: m2p1 channel registers 32 - description: m2p2 channel registers 33 - description: m2p3 channel registers 34 - description: m2p4 channel registers 35 - description: m2p5 channel registers 36 - description: m2p6 channel registers 37 - description: m2p7 channel registers 38 - description: m2p8 channel registers 39 - description: m2p9 channel registers [all …]
|
| D | stericsson,dma40.yaml | 19 The first cell is the unique device channel number as indicated by this 32 10: Multi-Channel Display Engine MCDE RX 42 20: SLIMbus or HSI channel 0 43 21: SLIMbus or HSI channel 1 44 22: SLIMbus or HSI channel 2 45 23: SLIMbus or HSI channel 3 53 31: MSP port 0 or SLIMbus channel 0 68 46: SLIMbus channel 8 or Multimedia DSP SXA6 69 47: SLIMbus channel 9 or Multimedia DSP SXA7 74 52: SLIMbus or HSI channel 4 [all …]
|
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 2 ALSA PCM channel-mapping API 10 The channel mapping API allows user to query the possible channel maps 11 and the current channel map, also optionally to modify the channel map 14 A channel map is an array of position for each PCM channel. 15 Typically, a stereo PCM stream has a channel map of 17 while a 4.0 surround PCM stream has a channel map of 20 The problem, so far, was that we had no standard channel map 21 explicitly, and applications had no way to know which channel 29 was no way to specify this because of lack of channel map 30 specification. These are the main motivations for the new channel [all …]
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | adi,ad5770r.yaml | 58 channel@0: 59 description: Represents an external channel which are 60 connected to the DAC. Channel 0 can act both as a current 67 description: This represents the channel number. 71 description: Output range of the channel. 83 channel@1: 84 description: Represents an external channel which are 91 description: This represents the channel number. 95 description: Output range of the channel. 100 channel@2: [all …]
|
| D | adi,ad5755.yaml | 7 title: Analog Devices AD5755 Multi-Channel DAC 40 1: Channel A and Channel B clock on the same edge, 41 Channel C and Channel D clock on opposite edges. 42 2: Channel A and Channel C clock on the same edge, 43 Channel B and Channel D clock on opposite edges. 44 3: Channel A, Channel B, Channel C, and Channel D 61 "#io-channel-cells": 69 "^channel@[0-7]$": 71 description: Child node to describe a channel 143 channel@0 { [all …]
|
| /Documentation/networking/ |
| D | ppp_generic.rst | 4 PPP Generic Driver and Channel Interface 26 the services of PPP ``channels``. A PPP channel encapsulates a 28 PPP channel implementation can be arbitrarily complex internally but 31 handle ioctl requests. Currently there are PPP channel 36 natural and straightforward way, by allowing more than one channel to 42 PPP channel API 49 Each channel has to provide two functions to the generic PPP layer, 53 send. The channel has the option of rejecting the frame for 55 and the channel should call the ppp_output_wakeup() function at a 61 program to control aspects of the channel's behaviour. This [all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-most | 19 configure the buffer size for this channel 22 configure the sub-buffer size for this channel 28 channel 32 this channel 51 channel 52 name of the channel the link is to be attached to 74 configure the buffer size for this channel 77 configure the sub-buffer size for this channel 83 channel 87 this channel [all …]
|
| D | sysfs-bus-rpmsg | 6 Every rpmsg device is a communication channel with a remote 11 This sysfs entry contains the name of this channel. 18 Every rpmsg device is a communication channel with a remote 21 starts listening on one end of a channel, it assigns it with 27 of this channel. If it contains 0xffffffff, then an address 29 channel). 36 Every rpmsg device is a communication channel with a remote 39 starts listening on one end of a channel, it assigns it with 45 of this channel. If it contains 0xffffffff, then an address 47 is attached to this channel is exposing a service to the [all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | qcom,pm8018-adc.yaml | 44 a hardware channel on all systems. 49 "#io-channel-cells": 59 - "#io-channel-cells" 62 - adc-channel@c 63 - adc-channel@d 64 - adc-channel@f 67 "^(adc-channel@)[0-9a-f]$": 70 ADC channel specific configuration. 92 Channel calibration type. If this property is specified 93 VADC will use a special voltage references for channel [all …]
|
| D | st,stm32-dfsdm-adc.yaml | 100 - For st,stm32-dfsdm-dmic: 1 channel numbered from 0 to 7. 107 st,adc-channel-names: 108 description: List of single-ended channel names. 120 "#io-channel-cells": 129 st,adc-channel-types: 131 Single-ended channel input type. 141 st,adc-channel-clk-src: 153 st,adc-alt-channel: 157 If not set, channel n is connected to SPI input n. 158 If set, channel n is connected to SPI input n + 1. [all …]
|
| D | ti,ads1119.yaml | 44 "#io-channel-cells": 56 "^channel@([0-6])$": 78 single-channel: 88 - single-channel 118 #io-channel-cells = <1>; 120 channel@0 { 122 single-channel = <0>; 125 channel@1 { 130 channel@2 { 132 single-channel = <3>; [all …]
|
| D | adi,ad7173.yaml | 16 can be used in high precision, low noise single channel applications 137 "^channel@[0-9a-f]$": 150 voltage channel. The first value is the positive input and the second 151 value is the negative input of the channel. 154 To select it set the second channel to 16. 172 single-channel: 174 This property is used for defining a current channel or the positive 175 input of a voltage channel (single-ended or pseudo-differential). 178 Example: (IIN2+, IIN2−) -> single-channel = <2> 179 To correctly configure a current channel set the "adi,current-channel" [all …]
|
| D | adc.yaml | 17 pattern: "^channel(@[0-9a-f]+)?$" 19 A channel index should match reg. 25 description: Unique name to identify which channel this is. 29 description: If provided, the channel is to be used in bipolar mode. 41 single-channel: 45 channel for a single element to be specified, independent of reg (as for 49 common-mode-channel: 54 in addition to single-channel to signal software that this channel is 57 The input pair is specified by setting single-channel to the positive 58 input pin and common-mode-channel to the negative pin. [all …]
|
| D | renesas,rzg2l-adc.yaml | 16 stored in a 32-bit data register corresponding to each channel. 71 "^channel@[0-7]$": 80 The channel number. 95 "^channel@[2-7]$": false 96 "^channel@[0-1]$": 103 "^channel@[0-7]$": 131 channel@0 { 134 channel@1 { 137 channel@2 { 140 channel@3 { [all …]
|
| D | ti,tsc2046.yaml | 29 "#io-channel-cells": 43 "^channel@[0-7]$": 50 The channel number. It can have up to 8 channels 80 #io-channel-cells = <1>; 85 channel@0 { 88 channel@1 { 93 channel@2 { 96 channel@3 { 101 channel@4 { 106 channel@5 { [all …]
|
| /Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.yaml | 4 $id: http://devicetree.org/schemas/iio/multiplexer/io-channel-mux.yaml# 7 title: I/O channel multiplexer 14 e.g. an ADC channel, these bindings describe that situation. 16 For each non-empty string in the channels property, an io-channel will be 17 created. The number of this io-channel is the same as the index into the list 25 const: io-channel-mux 29 description: Channel node of the parent channel that has multiplexed input. 31 io-channel-names: 41 string for a state means that the channel is not available. 48 "#io-channel-cells": [all …]
|
| /Documentation/devicetree/bindings/dma/xilinx/ |
| D | xilinx_dma.txt | 2 It can be configured to have one channel or two channels. If configured 7 target devices. It can be configured to have one channel or two channels. 28 - dma-channel child node: Should have at least one channel and can have up to 30 DMA channel (see child node properties below). 59 - xlnx,flush-fsync: Tells which channel to Flush on Frame sync. 62 {2}, flush mm2s channel 63 {3}, flush s2mm channel 67 For VDMA: It should be either "xlnx,axi-vdma-mm2s-channel" or 68 "xlnx,axi-vdma-s2mm-channel". 69 For CDMA: It should be "xlnx,axi-cdma-channel". [all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr-channel.yaml | 4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr-channel.yaml# 7 title: LPDDR channel with chip/rank topology description 10 An LPDDR channel is a completely independent set of LPDDR pins (DQ, CA, CS, 21 - jedec,lpddr2-channel 22 - jedec,lpddr3-channel 23 - jedec,lpddr4-channel 24 - jedec,lpddr5-channel 28 The number of DQ pins in the channel. If this number is different 31 channel (with the channel's DQ pins split up between the different 34 channel is equal to the sum of the densities of each rank on the [all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | fsl,scu.yaml | 52 channel for general interrupt. The number of expected tx and rx 61 - description: TX0 MU channel 62 - description: RX0 MU channel 64 - description: TX0 MU channel 65 - description: RX0 MU channel 66 - description: optional MU channel for general interrupt 68 - description: TX0 MU channel 69 - description: TX1 MU channel 70 - description: TX2 MU channel 71 - description: TX3 MU channel [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,sta32x.txt | 27 0: 2-channel (full-bridge) power, 2-channel data-out 29 2: 2 Channel (Full-Bridge) Power, 1 Channel FFX 30 3: 1 Channel Mono-Parallel 34 - st,ch1-output-mapping: Channel 1 output mapping 35 - st,ch2-output-mapping: Channel 2 output mapping 36 - st,ch3-output-mapping: Channel 3 output mapping 37 0: Channel 1 38 1: Channel 2 39 2: Channel 3 40 If parameter is missing, channel 1 is chosen. [all …]
|
| /Documentation/devicetree/bindings/dma/ti/ |
| D | k3-bcdma.yaml | 20 optional triggers a block copy channel can service peripherals by accessing 28 PDMAs can be configured via BCDMA split channel's peer registers to match with 49 cell 1: type of the BCDMA channel to be used to service the peripheral: 50 0 - split channel 51 1 - block copy channel using global trigger 1 52 2 - block copy channel using global trigger 2 53 3 - block copy channel using local trigger 55 cell 2: parameter for the channel: 56 if cell 1 is 0 (split channel): 64 if cell 1 is 1 or 2 (block copy channel using global trigger): [all …]
|
| /Documentation/arch/arm/stm32/ |
| D | stm32-dma-mdma-chaining.rst | 58 channel is null. The channel transfer complete of the last node is the end of 64 resources and bus congestion. Transfer Complete signal of STM32 DMA channel 77 | Channel *0* | DMA1 channel 0 | dma1_tcf0 | *0x00* | 79 | Channel *1* | DMA1 channel 1 | dma1_tcf1 | *0x01* | 81 | Channel *2* | DMA1 channel 2 | dma1_tcf2 | *0x02* | 83 | Channel *3* | DMA1 channel 3 | dma1_tcf3 | *0x03* | 85 | Channel *4* | DMA1 channel 4 | dma1_tcf4 | *0x04* | 87 | Channel *5* | DMA1 channel 5 | dma1_tcf5 | *0x05* | 89 | Channel *6* | DMA1 channel 6 | dma1_tcf6 | *0x06* | 91 | Channel *7* | DMA1 channel 7 | dma1_tcf7 | *0x07* | [all …]
|
| /Documentation/filesystems/ |
| D | relay.rst | 11 A 'relay channel' is a kernel->user data relay mechanism implemented 12 as a set of per-cpu kernel buffers ('channel buffers'), each 14 clients write into the channel buffers using efficient write 15 functions; these automatically log into the current cpu's channel 19 are associated with the channel buffers using the API described below. 21 The format of the data logged into the channel buffers is completely 35 Each relay channel has one buffer per CPU, each buffer has one or more 50 A relay channel can operate in a mode where it will overwrite data not 53 The relay channel itself does not provide for communication of such 61 the channel buffers, special-purpose communication between kernel and [all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-ect.rst | 21 0 C 0----------->: : +======>(other CTI channel IO) 31 channels. When an input trigger becomes active, the attached channel will 32 become active. Any output trigger attached to that channel will also 33 become active. The active channel is propagated to other CTIs via the CTM, 35 channel gate. 37 It is also possible to activate a channel using system software directly 43 no programmed trigger/channel attachments, so will not affect the system 89 * ``channels``: Contains the channel API - CTI main programming interface. 158 Attaches trigout(1) to channel(0), then activates channel(0) generating a 164 * ``trigin_attach, trigout_attach``: Attach a channel to a trigger signal. [all …]
|
12345678910>>...40