Groups > linux.kernel > #1361964

Re: [RESEND RFC 3/3] nvmem: Add 'nvmem-composite' driver

From	Andrey Smirnov <andrew.smirnov@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [RESEND RFC 3/3] nvmem: Add 'nvmem-composite' driver
Date	2016-03-21 17:20 +0100
Message-ID	<rfaIF-8aj-5@gated-at.bofh.it> (permalink)
References	<r7VOq-3gD-5@gated-at.bofh.it> <r7VOq-3gD-3@gated-at.bofh.it> <r8ftM-8on-15@gated-at.bofh.it> <r8jQL-3th-39@gated-at.bofh.it> <rdEhP-6LW-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

>> 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?

Thanks,
Andrey

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [RESEND RFC 3/3] nvmem: Add 'nvmem-composite' driver Andrey Smirnov <andrew.smirnov@gmail.com> - 2016-03-21 17:20 +0100
  Re: [RESEND RFC 3/3] nvmem: Add 'nvmem-composite' driver Srinivas Kandagatla <srinivas.kandagatla@linaro.org> - 2016-03-21 18:00 +0100

csiph-web