[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210510104415.11332-1-miquel.raynal@bootlin.com>
Date: Mon, 10 May 2021 12:44:15 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Michael Walle <michael@...le.cc>, linux-mtd@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Rob Herring <robh+dt@...nel.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Subject: Re: [PATCH v2 1/5] nvmem: core: allow specifying of_node
On Sat, 2021-04-24 at 11:06:04 UTC, Michael Walle wrote:
> Until now, the of_node of the parent device is used. Some devices
> provide more than just the nvmem provider. To avoid name space clashes,
> add a way to allow specifying the nvmem cells in subnodes. Consider the
> following example:
>
> flash@0 {
> compatible = "jedec,spi-nor";
>
> partitions {
> compatible = "fixed-partitions";
> #address-cells = <1>;
> #size-cells = <1>;
>
> partition@0 {
> reg = <0x000000 0x010000>;
> };
> };
>
> otp {
> compatible = "user-otp";
> #address-cells = <1>;
> #size-cells = <1>;
>
> serial-number@0 {
> reg = <0x0 0x8>;
> };
> };
> };
>
> There the nvmem provider might be the MTD partition or the OTP region of
> the flash.
>
> Add a new config->of_node parameter, which if set, will be used instead
> of the parent's of_node.
>
> Signed-off-by: Michael Walle <michael@...le.cc>
> Acked-by: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next, thanks.
Miquel
Powered by blists - more mailing lists