Lines Matching +full:device +full:- +full:unique

10 SoundWire is a 2-pin multi-drop interface with data and clock line. It
15      commands over a single two-pin interface.
23  (4) Device status monitoring, including interrupt-style alerts to the Master.
38         +---------------+                                       +---------------+
40         |    Master     |-------+-------------------------------|    Slave      |
42         |               |-------|-------+-----------------------|               |
43         +---------------+       |       |                       +---------------+
47                              +--+-------+--+
52                              +-------------+
58 The MIPI SoundWire specification uses the term 'device' to refer to a Master
61 Linux device model by mapping each Slave interface connected on the bus as a
62 device managed by a specific driver. The Linux SoundWire subsystem provides
64 3rd-party vendors to enable implementation-defined functionality while
69 Programs all the MIPI-defined Slave registers. Represents a SoundWire
73 Registers as SoundWire Slave device (Linux Device). Multiple Slave devices
77 Driver controlling the Slave device. MIPI-specified registers are controlled
79 Any implementation-defined Slave register is controlled by Slave driver. In
102 .. code-block:: c
105 				struct device *parent,
110 		mutex_init(&bus->lock);
111 		INIT_LIST_HEAD(&bus->slaves);
122 This will initialize sdw_bus object for Master device. "sdw_master_ops" and
136 then perform hardware-specific configurations.
141 The MIPI specification requires each Slave interface to expose a unique
142 48-bit identifier, stored in 6 read-only dev_id registers. This dev_id
146 identifier, Bus enumerates the Slave device based on these two ids.
147 Slave device and driver match is done based on these two ids . Probe
148 of the Slave driver is called by Bus on successful match between device and
154 board-file, ACPI or DT. The MIPI Software specification defines additional
156 dev_id registers are only unique in the scope of a link, and the link_id
157 unique in the scope of a controller. Both dev_id and link_id are not
158 necessarily unique at the system level but the parent/child information is
161 .. code-block:: c
199 https://members.mipi.org/wg/All-Members/document/70290
203 https://www.mipi.org/specifications/mipi-disco-soundwire