On 08/15/2011 01:37 PM, Russell King wrote:
On Wed, Aug 10, 2011 at 05:31:28PM -0600, Kenneth Heitke wrote:
From: Sagar Dharia<sdharia@xxxxxxxxxxxxxx>
SLIMbus (Serial Low Power Interchip Media Bus) is a specification
developed by MIPI (Mobile Industry Processor Interface) alliance.
SLIMbus is a 2-wire implementation, which is used to communicate with
peripheral components like audio. Commonly used digital audio
interfaces such as I2S, PCM are intended for point-to-point connection
between application processor and single audio device and support one
or two channels. Adding more channels or functions is difficult
without increasing number of bus structures and hence pin count.
In parallel to audio channels, control buses such as I2C are typically
used for low-bandwidth control tasks.
SLIMbus replaces many digital audio buses and control buses by
providing flexible and dynamic bus-bandwidth between data-functions
and control-functions.
The framework supports message APIs, channel scheduling for SLIMbus.
Message APIs are used for status/control type of communication with a
device. Data Channel APIs are used for setting data channels between
SLIMbus devices.
Framework supports multiple busses (1 controller per bus) and multiple
clients/slave devices per controller.
This looks like another bus doing the same thing as SPI and I2C.
...
I heard of another bus type at the recent Linaro conference which sounds
like it's going to do yet again a similar thing. So it sounds like we're
heading for about four of these things.
Is there any way to consolidate this before we end up with four ways of
solving the same problem?
I agree and am certainly open to suggestions. SPMI is another MIPI
standard bus that is likely going to fall into the same category.
thanks,
Ken
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
