Searched full:slave (Results 1 – 25 of 357) sorted by relevance
12345678910>>...15
| /Documentation/driver-api/soundwire/ |
| D | summary.rst | 25 The SoundWire protocol supports up to eleven Slave interfaces. All the
36 two Slave devices. ::
40 | Master |-------+-------------------------------| Slave |
49 | Slave |
59 or Slave interface, which of course can be confusing. In this summary and
61 Linux device model by mapping each Slave interface connected on the bus as a
63 a framework to implement a SoundWire Slave driver with an API allowing
69 Programs all the MIPI-defined Slave registers. Represents a SoundWire
72 Slave:
73 Registers as SoundWire Slave device (Linux Device). Multiple Slave devices
[all …]
|
| D | stream.rst | 29 Slave. Both Master and Slave is using single port. ::
32 | Master +----------------------------------+ Slave |
41 Example 2: Stereo Stream with L and R channels is captured from Slave to
42 Master. Both Master and Slave is using single port. ::
46 | Master +----------------------------------+ Slave |
60 | Master +---------+------------------------+ Slave |
70 | +----------------------> | Slave |
81 L+R. Each Slave device processes the L + R data locally, typically
86 | Master +---------+------------------------+ Slave |
96 | +----------------------> | Slave |
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | amlogic,axg-audio-clkc.yaml | 46 - description: slave bit clock N0 provided by external components
47 - description: slave bit clock N1 provided by external components
48 - description: slave bit clock N2 provided by external components
49 - description: slave bit clock N3 provided by external components
50 - description: slave bit clock N4 provided by external components
51 - description: slave bit clock N5 provided by external components
52 - description: slave bit clock N6 provided by external components
53 - description: slave bit clock N7 provided by external components
54 - description: slave bit clock N8 provided by external components
55 - description: slave bit clock N9 provided by external components
[all …]
|
| /Documentation/i2c/ |
| D | slave-interface.rst | 2 Linux I2C slave interface description
7 Linux can also be an I2C slave if the I2C controller in use has slave
8 functionality. For that to work, one needs slave support in the bus driver plus
10 example for the latter is the slave-eeprom driver, which acts as a dual memory
12 EEPROM, the Linux I2C slave can access the content via sysfs and handle data as
19 e.g. sysfs I2C slave events I/O registers
34 I2C slave backends behave like standard I2C clients. So, you can instantiate
36 difference is that i2c slave backends have their own address space. So, you
38 instantiating the slave-eeprom driver from userspace at the 7 bit address 0x64
41 # echo slave-24c02 0x1064 > /sys/bus/i2c/devices/i2c-1/new_device
[all …]
|
| D | i2c-address-translators.rst | 13 An I2C Address Translator (ATR) is a device with an I2C slave parent
16 with a modified slave address. The address used on the parent bus is
18 slave address of the child bus. Address translation is done by the
40 Slave X @ 0x10
46 Slave Y @ 0x10
68 - Slave X driver requests a transaction (on adapter B), slave address 0x10
69 - ATR driver finds slave X is on bus B and has alias 0x20, rewrites
71 - Physical I2C transaction on bus A, slave address 0x20
75 - Slave X chip (on bus B) detects transaction at its own physical
81 - Slave X driver gets back the msgs[], with reply and address 0x10
|
| D | slave-eeprom-backend.rst | 2 Linux I2C slave EEPROM backend
10 /sys/bus/i2c/devices/<device-directory>/slave-eeprom
14 'slave-<type>[ro]'. Examples follow:
17 # echo slave-24c02 0x1064 > /sys/bus/i2c/devices/i2c-1/new_device
20 # echo slave-24c512ro 0x1042 > /sys/bus/i2c/devices/i2c-1/new_device
|
| D | index.rst | 44 Slave I2C
50 slave-interface
51 slave-eeprom-backend
52 slave-testunit-backend
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,wcd938x-sdw.yaml | 7 title: Qualcomm SoundWire Slave devices on WCD9380/WCD9385
14 It has RX and TX Soundwire slave devices. This bindings is for the
15 slave devices.
26 Specifies static port mapping between slave and master tx ports.
27 In the order of slave port index.
34 Specifies static port mapping between slave and master rx ports.
35 In the order of slave port index.
|
| D | fsl,ssi.yaml | 132 enum: [ ac97-slave, ac97-master, i2s-slave, i2s-master,
133 lj-slave, lj-master, rj-slave, rj-master ]
135 "ac97-slave" - AC97 mode, SSI is clock slave
137 "i2s-slave" - I2S mode, SSI is clock slave
139 "lj-slave" - Left justified mode, SSI is clock slave
141 "rj-slave" - Right justified mode, SSI is clock slave
|
| /Documentation/w1/masters/ |
| D | omap-hdq.rst | 18 communication between the master (HDQ/1-Wire controller) and the slave
25 difference between the HDQ and 1-wire mode is how the slave device responds to
27 create an initialization pulse to the slave.However, the slave can be reset by
28 using an initialization pulse (also referred to as a break pulse).The slave
36 be used to calculate the CRC and pass back an appropriate slave ID to the W1
39 By default the master driver and the BQ slave i/f
42 that the ID used should be same for both master and slave driver loading.
50 pass slave ID as parameter. The driver will auto-detect slaves connected
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 16 represent the FSI slaves and their slave engines. As a basic outline:
22 fsi-slave@<link,id> {
23 /* this node defines the FSI slave device, and is handled
26 fsi-slave-engine@<addr> {
32 fsi-slave-engine@<addr> {
54 addresses (link index and slave ID), and no size:
69 Slaves are identified by a (link-index, slave-id) pair, so require two cells
71 required. For an example, a slave on link 1, with ID 2, could be represented
79 Each slave provides an address-space, under which the engines are accessible.
81 addresses and sizes in the slave address space:
[all …]
|
| /Documentation/gpu/ |
| D | komeda-kms.rst | 91 pipeline_A.timing_ctrlr. The pipeline_B works just like a "slave" of
140 Dual pipeline with Slave enabled
144 :alt: Slave pipeline digraph
145 :caption: Slave pipeline enabled data flow
157 label="Slave Pipeline_B"
161 "Slave.Scaler-0";
162 "Slave.Scaler-1";
166 "Slave.Layer-0" -> "Slave.Scaler-0"
167 "Slave.Layer-1" -> "Slave.Scaler-0"
168 "Slave.Layer-2" -> "Slave.Scaler-1"
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-fsi | 6 Initiates a FSI master scan for all connected slave devices
19 What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/term
25 connected slave. A terminate resets the slave's state machines
27 addition the slave freezes its internal error register for
32 What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/raw
|
| /Documentation/filesystems/ |
| D | sharedsubtree.rst | 37 b. slave mount
86 2b) A slave mount is like a shared mount except that mount and umount events
89 All slave mounts have a master mount which is a shared.
102 Now let's make the mount at /tmp; a slave of /mnt
103 # mount --make-slave /tmp
156 mount --make-slave mountpoint
193 of its namespace as slave::
253 2) slave
254 3) shared and slave
280 (2) Slave mounts
[all …]
|
| /Documentation/devicetree/bindings/ipmi/ |
| D | ipmi-ipmb.yaml | 39 slave-dev:
42 The slave i2c device. If not present, the main device is used. This
43 lets you use two devices on the IPMB, one for master and one for slave,
44 in case you have a slave device that can only be a slave. The slave
|
| /Documentation/devicetree/bindings/fpga/ |
| D | lattice-machxo2-spi.txt | 1 Lattice MachXO2 Slave SPI FPGA Manager
4 'slave SPI' interface.
9 - compatible: should contain "lattice,machxo2-slave-spi"
25 compatible = "lattice,machxo2-slave-spi";
|
| D | xlnx,fpga-slave-serial.yaml | 4 $id: http://devicetree.org/schemas/fpga/xlnx,fpga-slave-serial.yaml#
7 title: Xilinx Slave Serial SPI FPGA
14 over what is referred to as slave serial interface.The slave serial link is
29 - xlnx,fpga-slave-serial
71 compatible = "xlnx,fpga-slave-serial";
|
| /Documentation/devicetree/bindings/spi/ |
| D | mediatek,spi-slave-mt27xx.yaml | 4 $id: http://devicetree.org/schemas/spi/mediatek,spi-slave-mt27xx.yaml#
7 title: SPI Slave controller for MediaTek ARM SoCs
18 - mediatek,mt2712-spi-slave
19 - mediatek,mt8195-spi-slave
51 compatible = "mediatek,mt2712-spi-slave";
|
| /Documentation/devicetree/bindings/ata/ |
| D | cortina,gemini-sata-bridge.yaml | 58 ata0 slave interface brought out on IDE pads
61 ata1 slave interface brought out on IDE pads
63 ata1 slave <-> sata0
64 ata0 master and slave interfaces brought out on IDE pads
66 ata0 slave <-> sata1
67 ata1 master and slave interfaces brought out on IDE pads
73 and whether master, slave or both interfaces get brought out.
|
| /Documentation/w1/ |
| D | w1-netlink.rst | 10 1. Events. They are generated each time a new master or slave device
28 slave add/remove events
35 userspace command for slave device
40 __u8 id[8]; - slave unique device id
47 [struct w1_netlink_cmd] - command for given master or slave device.
56 W1_CMD_SLAVE_ADD - add slave to kernel list
57 W1_CMD_SLAVE_REMOVE - remove slave from kernel list
71 either 8 bytes of slave unique id in host order,
140 Each command (either root, master or slave with or without w1_netlink_cmd
169 master or slave request, according to w1_netlink_msg.type field.
[all …]
|
| D | w1-generic.rst | 5 The 1-wire bus is a simple master-slave bus that communicates via a single
14 All w1 slave devices must be connected to a w1 bus master device.
30 - the w1 bus is periodically searched for new slave devices
33 and check if it is loaded. If so, the family driver is attached to the slave.
45 and slave device will be even removed, but in this case 0xff will
52 Slave devices are handled by a driver written for a family of w1 devices.
93 w1_master_add (rw) manually register a slave device
98 w1_master_remove (rw) manually remove a slave device
110 set to zero, then manually add the slave device serial numbers by
122 w1 slave sysfs interface
[all …]
|
| /Documentation/networking/ |
| D | bonding.rst | 172 Specifies the new active slave for modes that support it
175 string. If a name is given, the slave and its link must be up in order
176 to be selected as the new active slave. If an empty string is
177 specified, the current active slave is cleared, and a new active
178 slave is selected automatically.
184 active slave, or the empty string if there is no active slave or
185 the current mode does not use an active slave.
230 - A slave is added to or removed from the bond
232 - Any slave's link state changes
234 - Any slave's 802.3ad association state changes
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | cpsw.txt | 20 - active_slave : Specifies the slave to use for time stamping,
37 driven low so that cpsw slave 0 and phy data
45 Slave Properties:
52 - phy_id : Specifies slave phy id (deprecated, use phy-handle)
58 Slave sub-nodes:
87 cpsw_emac0: slave@0 {
94 cpsw_emac1: slave@1 {
118 cpsw_emac0: slave@0 {
125 cpsw_emac1: slave@1 {
|
| /Documentation/driver-api/dmaengine/ |
| D | client.rst | 11 Below is a guide to device driver writers on how to use the Slave-DMA API of the
12 DMA Engine. This is applicable only for slave DMA usage only.
17 The slave DMA usage consists of following steps:
19 - Allocate a DMA slave channel
21 - Set slave and controller specific parameters
31 1. Allocate a DMA slave channel
33 Channel allocation is slightly different in the slave DMA context,
51 2. Set slave and controller specific parameters
54 driver. Most of the generic information which a slave DMA can use
78 For slave usage the various modes of slave transfers supported by the
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,cci-400.yaml | 19 space and multiple sets of interface control registers, one per slave
43 "^slave-if@[0-9a-f]+$":
131 * CCI slave interface @0x000000002c091000 is connected to dma
134 * CCI slave interface @0x000000002c094000 is connected to CPUs
137 * CCI slave interface @0x000000002c095000 is connected to CPUs
181 cci_control0: slave-if@1000 {
187 cci_control1: slave-if@4000 {
193 cci_control2: slave-if@5000 {
|
12345678910>>...15