[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210114201704.GA3520207@robh.at.kernel.org>
Date: Thu, 14 Jan 2021 14:17:04 -0600
From: Rob Herring <robh@...nel.org>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Cc: tim.gover@...pberrypi.com, srinivas.kandagatla@...aro.org,
linux-arm-kernel@...ts.infradead.org, robh+dt@...nel.org,
bcm-kernel-feedback-list@...adcom.com, phil@...pberrypi.com,
linux-kernel@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org,
linux@...linux.org.uk, devicetree@...r.kernel.org,
catalin.marinas@....com, will@...nel.org
Subject: Re: [PATCH v3 1/5] dt-bindings: nvmem: Add bindings for rmem driver
On Tue, 12 Jan 2021 15:23:38 +0100, Nicolas Saenz Julienne wrote:
> Firmware/co-processors might use reserved memory areas in order to pass
> data stemming from an nvmem device otherwise non accessible to Linux.
> For example an EEPROM memory only physically accessible to firmware, or
> data only accessible early at boot time.
>
> Introduce the dt-bindings to nvmem's rmem.
>
> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
>
> ---
>
> Changes since v2:
> - Run yamllint and fix indentation issues
>
> Changes since v1:
> - Update schema to new driver design
>
> .../devicetree/bindings/nvmem/rmem.yaml | 49 +++++++++++++++++++
> 1 file changed, 49 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/rmem.yaml
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists