Searched full:slave (Results 1 – 25 of 374) sorted by relevance
12345678910>>...15
| /Documentation/devicetree/bindings/clock/ |
| D | brcm,kona-ccu.txt | 32 compatible = "brcm,bcm11351-slave-ccu";
63 "brcm,bcm11351-slave-ccu"
90 slave uartb peri 0 BCM281XX_SLAVE_CCU_UARTB
91 slave uartb2 peri 1 BCM281XX_SLAVE_CCU_UARTB2
92 slave uartb3 peri 2 BCM281XX_SLAVE_CCU_UARTB3
93 slave uartb4 peri 3 BCM281XX_SLAVE_CCU_UARTB4
94 slave ssp0 peri 4 BCM281XX_SLAVE_CCU_SSP0
95 slave ssp2 peri 5 BCM281XX_SLAVE_CCU_SSP2
96 slave bsc1 peri 6 BCM281XX_SLAVE_CCU_BSC1
97 slave bsc2 peri 7 BCM281XX_SLAVE_CCU_BSC2
[all …]
|
| /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 |
80 Ports of the Master and is received by only single Port of the Slave
96 | | 2 || R Channel | Slave |
109 | Master +----------------------------------+ Slave |
[all …]
|
| /Documentation/networking/caif/ |
| D | spi_porting.txt | 7 between the master and the slave. The minimum requirement for running
8 CAIF over SPI is a SPI slave chip and two GPIOs (more details below).
9 Please note that running as a slave implies that you need to keep up
18 SPI slave device part, which is the module that you have to write if
24 - Functionality provided by the CAIF SPI slave device:
37 to map to different CAIF SPI slave devices.
45 SPI slave devices.
51 This function is called by the CAIF SPI slave device in order to
60 This function is called by the CAIF SPI slave device in order to
69 - Filling in the SPI slave device structure:
[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 is that i2c slave backends have their own address space. So, you have to add
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 …]
|
| /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/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/slave@00:00/raw
|
| /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/ata/ |
| D | cortina,gemini-sata-bridge.txt | 20 ata0 slave interface brought out on IDE pads
23 ata1 slave interface brought out on IDE pads
25 ata1 slave <-> sata0
26 ata0 master and slave interfaces brought out
29 ata0 slave <-> sata1
30 ata1 master and slave interfaces brought out
36 and whether master, slave or both interfaces get brought out.
|
| /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/networking/dsa/ |
| D | configuration.rst | 35 All other corresponding linux interfaces are called slave interfaces.
37 The slave interfaces depend on the master interface. They can only brought up,
46 a slave interface
49 another slave interface
52 a third slave interface
55 A slave interface dedicated for upstream traffic
91 # The master interface needs to be brought up before the slave ports.
94 # bring up the slave interfaces
104 # The master interface needs to be brought up before the slave ports.
107 # bring up the slave interfaces
[all …]
|
| /Documentation/filesystems/ |
| D | sharedsubtree.txt | 34 b. slave mount
76 2b) A slave mount is like a shared mount except that mount and umount events
79 All slave mounts have a master mount which is a shared.
92 Now let's make the mount at /tmp; a slave of /mnt
93 # mount --make-slave /tmp
144 mount --make-slave mountpoint
180 of its namespace as slave
239 2) slave
240 3) shared and slave
265 (2) Slave mounts
[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/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 | xilinx-slave-serial.txt | 1 Xilinx Slave Serial SPI FPGA Manager
4 what is referred to as "slave serial" interface.
5 The slave serial link is not technically SPI, and might require extra
11 - compatible: should contain "xlnx,fpga-slave-serial"
36 compatible = "xlnx,fpga-slave-serial";
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,nvec.txt | 5 - reg : the iomem of the i2c slave controller
6 - interrupts : the interrupt line of the i2c slave controller
9 - slave-addr: the i2c address of the slave controller
|
| /Documentation/devicetree/bindings/serial/ |
| D | slave-device.txt | 1 Serial Slave Device DT binding
8 slave device is attached to. It is expected that the attached device is
9 the only child node of the UART device. The slave device node name shall
20 only be present if the maximum is less than the slave device
26 the baud rate of the slave device.
|
| /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/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/devicetree/bindings/spi/ |
| D | spi-fsl-lpspi.txt | 15 - spi-slave : spi slave mode support. In slave mode, add this attribute without
28 spi-slave;
|
| /Documentation/networking/ |
| D | bonding.txt | 167 Specifies the new active slave for modes that support it
170 string. If a name is given, the slave and its link must be up in order
171 to be selected as the new active slave. If an empty string is
172 specified, the current active slave is cleared, and a new active
173 slave is selected automatically.
179 active slave, or the empty string if there is no active slave or
180 the current mode does not use an active slave.
224 - A slave is added to or removed from the bond
226 - Any slave's link state changes
228 - Any slave's 802.3ad association state changes
[all …]
|
| /Documentation/devicetree/bindings/arm/msm/ |
| D | ssbi.txt | 13 with the slave device. This should be one of "ssbi", "ssbi2", or
15 slave.
17 The slave device should be the single child node of the ssbi device
|
| /Documentation/devicetree/bindings/spmi/ |
| D | spmi.txt | 5 each representing a unique slave on the bus.
13 An SPMI controller node can contain zero or more child nodes representing slave
16 SPMI_USID (0) or SPMI_GSID (1) for Unique Slave ID or Group Slave ID respectively.
|
| /Documentation/spi/ |
| D | pxa2xx.rst | 12 - Per slave device (chip) configuration.
32 slave device (chips) attached to this SPI master.
80 Declaring Slave Devices
82 Typically each SPI slave (chip) is defined in the arch/.../mach-*/board-*.c
86 Each slave device attached to the PXA must provide slave specific configuration
89 will uses the configuration whenever the driver communicates with the slave
123 slave device. Please note that the PXA2xx SSP 1 does not support trailing byte
132 function for asserting/deasserting a slave device chip select. If the field is
142 NSSP SLAVE SAMPLE
150 /* Chip Select control for the CS8415A SPI slave device */
[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 {
|
12345678910>>...15