Re: [PATCH v2 06/29] mtd: Add support for reading MTD devices via the nvmem API
From: Alban
Date: Mon Aug 20 2018 - 17:29:18 EST
On Mon, 20 Aug 2018 20:20:38 +0200
Boris Brezillon <boris.brezillon@xxxxxxxxxxx> wrote:
> On Mon, 20 Aug 2018 11:43:34 +0100
> Srinivas Kandagatla <srinivas.kandagatla@xxxxxxxxxx> wrote:
>
> >
> > Overall am still not able to clear visualize on how MTD bindings with
> > nvmem cells would look in both partition and un-partition usecases?
> > An example DT would be nice here!!
>
> Something along those lines:
We must also have a compatible string on the nvmem-cells node to make
sure we don't clash with the old style MTD partitions, or some other
device specific binding.
>
> mtdnode {
> nvmem-cells {
compatible = "nvmem-cells";
> #address-cells = <1>;
> #size-cells = <1>;
>
> cell@0 {
> reg = <0x0 0x14>;
> };
> };
>
> partitions {
> compatible = "fixed-partitions";
> #address-cells = <1>;
> #size-cells = <1>;
>
> partition@0 {
> reg = <0x0 0x20000>;
>
> nvmem-cells {
compatible = "nvmem-cells";
> #address-cells = <1>;
> #size-cells = <1>;
>
> cell@0 {
> reg = <0x0 0x10>;
> };
> };
> };
> };
> };
Alban
Attachment:
pgpgng9J1Gei_.pgp
Description: OpenPGP digital signature