From: Rob Herring <robh@kernel.org> To: "Rafał Miłecki" <zajec5@gmail.com> Cc: "Florian Fainelli" <f.fainelli@gmail.com>, "Vivek Unune" <npcomplete13@gmail.com>, linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org, devicetree@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl> Subject: Re: [PATCH stblinux.git 1/2] dt-bindings: firmware: add Broadcom's NVRAM memory mapping Date: Mon, 8 Mar 2021 11:43:08 -0700 [thread overview] Message-ID: <20210308184308.GA2762703@robh.at.kernel.org> (raw) In-Reply-To: <20210302074405.18998-1-zajec5@gmail.com> On Tue, Mar 02, 2021 at 08:44:04AM +0100, Rafał Miłecki wrote: > From: Rafał Miłecki <rafal@milecki.pl> > > NVRAM structure contains device data and can be accessed using MMIO. > > Signed-off-by: Rafał Miłecki <rafal@milecki.pl> > --- > .../bindings/firmware/brcm,nvram.yaml | 41 +++++++++++++++++++ > 1 file changed, 41 insertions(+) > create mode 100644 Documentation/devicetree/bindings/firmware/brcm,nvram.yaml > > diff --git a/Documentation/devicetree/bindings/firmware/brcm,nvram.yaml b/Documentation/devicetree/bindings/firmware/brcm,nvram.yaml > new file mode 100644 > index 000000000000..12af8e2e7c9c > --- /dev/null > +++ b/Documentation/devicetree/bindings/firmware/brcm,nvram.yaml > @@ -0,0 +1,41 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: "http://devicetree.org/schemas/firmware/brcm,nvram.yaml#" > +$schema: "http://devicetree.org/meta-schemas/core.yaml#" > + > +title: Broadcom's NVRAM > + > +maintainers: > + - Rafał Miłecki <rafal@milecki.pl> > + > +description: | > + NVRAM is a structure containing device specific environment variables. > + It is used for storing device configuration, booting parameters and > + calibration data. The structure of the data is fully discoverable just from a genericish 'brcm,nvram'? And it's a dedicated memory outside of regular RAM? > + > + It's required very early in booting process and so is made available > + using memory mapping. > + > + NVRAM can be found on Broadcom BCM47xx MIPS, Northstar ARM Cortex-A9 > + and some more devices. > + > +properties: > + compatible: > + const: brcm,nvram > + > + reg: > + description: memory region with NVRAM data > + maxItems: 1 > + > +required: > + - reg > + > +additionalProperties: false > + > +examples: > + - | > + nvram@1e000000 { > + compatible = "brcm,nvram"; > + reg = <0x1e000000 0x10000>; > + }; > -- > 2.26.2 >
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org> To: "Rafał Miłecki" <zajec5@gmail.com> Cc: "Florian Fainelli" <f.fainelli@gmail.com>, "Vivek Unune" <npcomplete13@gmail.com>, linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org, devicetree@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl> Subject: Re: [PATCH stblinux.git 1/2] dt-bindings: firmware: add Broadcom's NVRAM memory mapping Date: Mon, 8 Mar 2021 11:43:08 -0700 [thread overview] Message-ID: <20210308184308.GA2762703@robh.at.kernel.org> (raw) In-Reply-To: <20210302074405.18998-1-zajec5@gmail.com> On Tue, Mar 02, 2021 at 08:44:04AM +0100, Rafał Miłecki wrote: > From: Rafał Miłecki <rafal@milecki.pl> > > NVRAM structure contains device data and can be accessed using MMIO. > > Signed-off-by: Rafał Miłecki <rafal@milecki.pl> > --- > .../bindings/firmware/brcm,nvram.yaml | 41 +++++++++++++++++++ > 1 file changed, 41 insertions(+) > create mode 100644 Documentation/devicetree/bindings/firmware/brcm,nvram.yaml > > diff --git a/Documentation/devicetree/bindings/firmware/brcm,nvram.yaml b/Documentation/devicetree/bindings/firmware/brcm,nvram.yaml > new file mode 100644 > index 000000000000..12af8e2e7c9c > --- /dev/null > +++ b/Documentation/devicetree/bindings/firmware/brcm,nvram.yaml > @@ -0,0 +1,41 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: "http://devicetree.org/schemas/firmware/brcm,nvram.yaml#" > +$schema: "http://devicetree.org/meta-schemas/core.yaml#" > + > +title: Broadcom's NVRAM > + > +maintainers: > + - Rafał Miłecki <rafal@milecki.pl> > + > +description: | > + NVRAM is a structure containing device specific environment variables. > + It is used for storing device configuration, booting parameters and > + calibration data. The structure of the data is fully discoverable just from a genericish 'brcm,nvram'? And it's a dedicated memory outside of regular RAM? > + > + It's required very early in booting process and so is made available > + using memory mapping. > + > + NVRAM can be found on Broadcom BCM47xx MIPS, Northstar ARM Cortex-A9 > + and some more devices. > + > +properties: > + compatible: > + const: brcm,nvram > + > + reg: > + description: memory region with NVRAM data > + maxItems: 1 > + > +required: > + - reg > + > +additionalProperties: false > + > +examples: > + - | > + nvram@1e000000 { > + compatible = "brcm,nvram"; > + reg = <0x1e000000 0x10000>; > + }; > -- > 2.26.2 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-08 18:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-02 7:44 [PATCH stblinux.git 1/2] dt-bindings: firmware: add Broadcom's NVRAM memory mapping Rafał Miłecki 2021-03-02 7:44 ` Rafał Miłecki 2021-03-02 7:44 ` [PATCH stblinux.git 2/2] firmware: bcm47xx_nvram: support platform device "brcm,nvram" Rafał Miłecki 2021-03-02 7:44 ` [PATCH stblinux.git 2/2] firmware: bcm47xx_nvram: support platform device "brcm, nvram" Rafał Miłecki 2021-03-02 16:59 ` [PATCH stblinux.git 2/2] firmware: bcm47xx_nvram: support platform device "brcm,nvram" Florian Fainelli 2021-03-02 16:59 ` Florian Fainelli 2021-03-03 11:44 ` Rafał Miłecki 2021-03-03 11:44 ` Rafał Miłecki 2021-03-08 18:43 ` Rob Herring [this message] 2021-03-08 18:43 ` [PATCH stblinux.git 1/2] dt-bindings: firmware: add Broadcom's NVRAM memory mapping Rob Herring 2021-03-08 21:37 ` Rafał Miłecki 2021-03-08 21:37 ` Rafał Miłecki 2021-03-08 21:41 ` Rafał Miłecki 2021-03-08 21:41 ` Rafał Miłecki
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210308184308.GA2762703@robh.at.kernel.org \ --to=robh@kernel.org \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=devicetree@vger.kernel.org \ --cc=f.fainelli@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=npcomplete13@gmail.com \ --cc=rafal@milecki.pl \ --cc=zajec5@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.