On 2018-07-12 10:08, Arnd Bergmann wrote:
> On Thu, Jul 12, 2018 at 6:41 AM, Peter Rosin wrote:
>> On 2018-07-11 19:12, Boris Brezillon wrote:
>>> On Wed, 11 Jul 2018 17:39:56 +0200 Arnd Bergmann wrote:
>>>
>>> That's exactly the sort of discussion I wanted to trigger. Maybe we
>>> shouldn't care
On Thu, Jul 12, 2018 at 6:41 AM, Peter Rosin wrote:
> On 2018-07-11 19:12, Boris Brezillon wrote:
>> On Wed, 11 Jul 2018 17:39:56 +0200 Arnd Bergmann wrote:
>>
>> That's exactly the sort of discussion I wanted to trigger. Maybe we
>> shouldn't care and expose this use case as if it was X differen
On Wed, Jul 11, 2018 at 4:41 PM, Boris Brezillon
wrote:
> On Wed, 11 Jul 2018 16:01:56 +0200 Arnd Bergmann wrote:
>> > - the bus element is a separate object and is not implicitly described
>> > by the master (as done in I2C). The reason is that I want to be able
>> > to handle multiple maste
On Fri, Mar 30, 2018 at 9:47 AM, Boris Brezillon
wrote:
> Add core infrastructure to support I3C in Linux and document it.
>
> 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 de
Add core infrastructure to support I3C in Linux and document it.
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 t
5 matches
Mail list logo
