Re: [RFC 0/5] Add I3C subsystem

2017-12-12 Thread Wolfram Sang
> MIPI has opened the I3C spec [1], it can be downloaded here [2]. Wow, that's good news. And so fast. Congrats and thanks a lot! signature.asc Description: PGP signature

Re: [RFC 0/5] Add I3C subsystem

2017-12-12 Thread Boris Brezillon
On Mon, 31 Jul 2017 21:17:45 +0200 Wolfram Sang wrote: > Hi Boris, > > > This patch series is a proposal for a new I3C [1] subsystem. > > Nice. Good luck with that! > > Some hi-level comments from me related to I2C. I can't say a lot more > because the specs are not public :( > > > - the bu

Re: [RFC 0/5] Add I3C subsystem

2017-07-31 Thread Wolfram Sang
> > I agree this is the least invasive and also the most compatible > > approach. The other solution would probably be to have some kind of > > emulation layer? > > Could you detail a bit more what you mean by "emulation layer"? Not really. That was more a extremly high level approach of what th

Re: [RFC 0/5] Add I3C subsystem

2017-07-31 Thread Boris Brezillon
Hi Wolfram, Le Mon, 31 Jul 2017 21:17:45 +0200, Wolfram Sang a écrit : > Hi Boris, > > > This patch series is a proposal for a new I3C [1] subsystem. > > Nice. Good luck with that! > > Some hi-level comments from me related to I2C. I can't say a lot more > because the specs are not public

Re: [RFC 0/5] Add I3C subsystem

2017-07-31 Thread Wolfram Sang
Hi Boris, > This patch series is a proposal for a new I3C [1] subsystem. Nice. Good luck with that! Some hi-level comments from me related to I2C. I can't say a lot more because the specs are not public :( > - the bus element is a separate object and is not implicitly described > by the maste

[RFC 0/5] Add I3C subsystem

2017-07-31 Thread Boris Brezillon
This patch series is a proposal for a new I3C [1] subsystem. This infrastructure is not complete yet and will be extended over time. There are a few design choices that are worth mentioning because they impact the way I3C device drivers can interact with their devices: - all functions used to se