[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221110165906.GA241353-robh@kernel.org>
Date: Thu, 10 Nov 2022 10:59:06 -0600
From: Rob Herring <robh@...nel.org>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
devicetree@...r.kernel.org, Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Tudor Ambarus <Tudor.Ambarus@...rochip.com>,
Pratyush Yadav <p.yadav@...com>,
Michael Walle <michael@...le.cc>,
linux-mtd@...ts.infradead.org,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 13/17] dt-bindings: mtd: nvmem-cells: Fix example
On Fri, Nov 04, 2022 at 05:47:14PM +0100, Miquel Raynal wrote:
> There is no such thing as a "ranges" property within an nvmem-cells
> node. There is no use of it, it is anyway not pictured anywhere that
> this is valid, so drop it from the example.
For a memory mapped device such as parallel NOR flash. It would be
perfectly fine to translate a nvmem cell 'reg' address to a CPU address.
If the partitions are not memory mapped, then it's a gray area. Whether
it makes sense to translate just to just the absolute offset of the
flash device, maybe or maybe not. At a minimum, 'ranges' just means
can translate to the parent address space. The Linux DT translate code
only supports the full translation to CPU addresses, but then it mainly
just supports creating resources.
Rob
Powered by blists - more mailing lists