lkml.org 
[lkml]   [2016]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RESEND RFC 3/3] nvmem: Add 'nvmem-composite' driver
From
Date


On 21/03/16 16:12, Andrey Smirnov wrote:
>>> a-node {
>>> nvmem-cells = <&cell_a &cell_b>, ????;
>>> nvmem-cell-names = "some-data", "more-data";
>>> };
>>>
>> Should have replied you long back :-)
>
> No worries :-)
>
>>>
>>> and I want "more-data" to reference only one phandle, how would this be
>>> handled?
>>>
>> yes this would fail.
>>
>> The device tree compiler would concatenate all the cells and we have no
>> means to know where did "more-data" starts.
>>
>> sounds like composite driver is the way forward.
>
> What's your preference on "separate driver" vs. "part of the NVMEM
> framework"? Should I keep it as a separate driver or try to fold it
> into NVMEM core?

It does not make sense to have this driver as a separate nvmem provider,
can you fold it in the nvmem core itself for now.


Thanks,
srini
>
> Thanks,
> Andrey
>

\
 
 \ /
  Last update: 2016-03-21 18:21    [W:0.990 / U:0.700 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site