Messages in this thread | | | Subject | Re: [RESEND RFC 3/3] nvmem: Add 'nvmem-composite' driver | From | Srinivas Kandagatla <> | Date | Mon, 21 Mar 2016 16:56:48 +0000 |
| |
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 >
| |