[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210310030222.GA1667188@robh.at.kernel.org>
Date: Tue, 9 Mar 2021 20:02:22 -0700
From: Rob Herring <robh@...nel.org>
To: Rafał Miłecki <zajec5@...il.com>
Cc: Rafał Miłecki <rafal@...ecki.pl>,
linux-arm-kernel@...ts.infradead.org,
Vivek Unune <npcomplete13@...il.com>,
bcm-kernel-feedback-list@...adcom.com,
Rob Herring <robh+dt@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>,
linux-kernel@...r.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
linux-mips@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH V2 1/2] dt-bindings: nvmem: add Broadcom's NVRAM
On Fri, 05 Mar 2021 19:32:35 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> Broadcom's NVRAM structure contains device data and can be accessed
> using I/O mapping.
>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>
> ---
> V2: Use Broadcom's NVRAM specific binding. Generic "nvmem-iomap" binding
> didn't make much sense. Thanks Srinivas!
> ---
> .../devicetree/bindings/nvmem/brcm,nvram.yaml | 34 +++++++++++++++++++
> 1 file changed, 34 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists