Lines Matching +full:multiple +full:- +full:channel

9 ----------------
12 configuration, and is a 2-wire multi-drop implementation (clock, and data).
15 (System-on-Chip) and peripheral components (typically codec). SLIMbus uses
16 Time-Division-Multiplexing to accommodate multiple data channels, and
17 a control channel.
19 The control channel is used for various control functions such as bus
21 reading/writing device specific values), or multicast (e.g. data channel
24 A data channel is used for data-transfer between 2 SLIMbus devices. Data
25 channel uses dedicated ports on the device.
28 ---------------------
32 channel allocation. Every bus has 1 active manager.
36 Framer device is responsible for clocking the bus, and transmitting frame-sync
42 1 generic device (for data channel support), and 1 interface device.
44 functionality/data channel support), and an associated interface device.
46 be written/read using SLIMbus control channel exchanging control/status type of
48 In case there are multiple framer devices on the same bus, manager device is
49 responsible to select the active-framer for clocking the bus.
55 Each device has a 6-byte enumeration-address and the manager assigns every
56 device with a 1-byte logical address after the devices report presence on the
60 ---------------------
72 -----------------------------------
93 ---------------------------
94 .. kernel-doc:: include/linux/slimbus.h
97 .. kernel-doc:: drivers/slimbus/slimbus.h
100 .. kernel-doc:: drivers/slimbus/core.c
103 Clock-pause:
104 ------------
105 SLIMbus mandates that a reconfiguration sequence (known as clock-pause) be
106 broadcast to all active devices on the bus before the bus can enter low-power
107 mode. Controller uses this sequence when it decides to enter low-power mode so
108 that corresponding clocks and/or power-rails can be turned off to save power.
109 Clock-pause is exited by waking up framer device (if controller driver initiates
113 Clock-pause APIs:
115 .. kernel-doc:: drivers/slimbus/sched.c
119 ----------
120 The framework supports regmap and read/write apis to exchange control-information
126 .. kernel-doc:: drivers/slimbus/messaging.c
131 .. kernel-doc:: drivers/slimbus/stream.c