Re: [PATCH V5 0/6] Introduce framework for SLIMbus device drivers

From: Masami Hiramatsu
Date: Sun Jun 26 2016 - 21:31:14 EST


Hello Sagar,

On Fri, 3 Jun 2016 18:14:19 +0900
Masami Hiramatsu <masami.hiramatsu@xxxxxxxxxx> wrote:

> Hi Sagar,
>
> On Wed, 27 Apr 2016 17:58:03 -0600
> Sagar Dharia <sdharia@xxxxxxxxxxxxxx> wrote:
>
> > 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-codec.
> > SLIMbus uses Time-Division-Multiplexing to accommodate multiple data
> > channels, and control channel. Control channel has messages to do
> > device-enumeration, messages to send/receive control-data to/from
> > slimbus devices, messages for port/channel management, and messages to
> > do bandwidth allocation.
> > Framework is introduced to support multiple instances of the bus
> > (1 controller per bus), and multiple slave devices per controller.
> > SPI and I2C frameworks, and comments from last time when I submitted
> > the patches were referred-to while working on this framework.
> >
> > These patchsets introduce device-management, OF helpers, and messaging
> > APIs, controller driver for Qualcomm's slimbus controller, and
> > clock-pause feature for entering/exiting low-power mode for SLIMbus.
> > Framework patches to do channel, port and bandwidth
> > management are work-in-progress and will be sent out once these
> > initial patches are accepted.
>
> I'm interested in this framework, especially the channel and port
> parts since it is needed for device drivers on the slimbus.
> Would you have any public git repository where I can review the
> work-in-progress part of the framework?

So, I've found git repositories on codeaurora.org,

https://source.codeaurora.org/

But there are too many repositories and branches to get the
correct working source code. Could you help me to find it?

Thank you,


--
Masami Hiramatsu <masami.hiramatsu@xxxxxxxxxx>