[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <167743670799.150030.2985662299530290415.robh@kernel.org>
Date: Sun, 26 Feb 2023 12:38:28 -0600
From: Rob Herring <robh@...nel.org>
To: Rafał Miłecki <zajec5@...il.com>
Cc: Rafał Miłecki <rafal@...ecki.pl>,
Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
devicetree@...r.kernel.org, linux-mediatek@...ts.infradead.org,
Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-kernel@...r.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH V3 1/2] dt-bindings: nvmem: mmio: new binding for MMIO
accessible NVMEM devices
On Mon, 20 Feb 2023 18:49:29 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> Content of some NVMEM devices can be read using MMIO. Some of them
> (probably very few though) may be also programmable that way. Add
> generic binding to allow describing such hardware.
>
> This *doesn't* apply to any more complicated devices that need more
> complex interface e.g. for writing. While such devices could be
> supported for reading purposes by the same driver - they should get
> their own binding.
>
> This binding will gain even more usability once we fully support NVMEM
> layouts (describing content of NVMEM devices in an independent way).
>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>
> ---
> V3: Make it clear this binding should NOT be used for more complex devices
> ---
> .../devicetree/bindings/nvmem/mmio.yaml | 50 +++++++++++++++++++
> 1 file changed, 50 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/mmio.yaml
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists