From: Rob Herring <robh@kernel.org>
To: Vadym Kochan <vadym.kochan@plvision.eu>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: nvmem: add description for ONIE provider
Date: Tue, 29 Sep 2020 12:56:32 -0500 [thread overview]
Message-ID: <20200929175632.GA860453@bogus> (raw)
In-Reply-To: <20200921235237.7980-3-vadym.kochan@plvision.eu>
On Tue, Sep 22, 2020 at 02:52:37AM +0300, Vadym Kochan wrote:
> Add device-tree binding description for the ONIE nvmem provider.
What's ONIE?
>
> Signed-off-by: Vadym Kochan <vadym.kochan@plvision.eu>
> ---
> .../devicetree/bindings/nvmem/onie-nvmem.txt | 11 +++++++++++
Bindings are in schema format now.
> 1 file changed, 11 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/onie-nvmem.txt
>
> diff --git a/Documentation/devicetree/bindings/nvmem/onie-nvmem.txt b/Documentation/devicetree/bindings/nvmem/onie-nvmem.txt
> new file mode 100644
> index 000000000000..16fb903118d0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/onie-nvmem.txt
> @@ -0,0 +1,11 @@
> += Device tree bindings for ONIE NVMEM provider =
> +
> +Required properties:
> +- compatible: should be "onie-nvmem"
> +- nvmem: phandle to nvmem device node
Not a standard property.
I don't understand what you are trying to do.
> +
> +Example:
> + onie_cells {
> + compatible = "onie-nvmem"
> + nvmem = <&at24>;
> + };
> --
> 2.17.1
>
prev parent reply other threads:[~2020-09-29 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 23:52 [PATCH 0/2] Add ONIE NVMEM provider Vadym Kochan
2020-09-21 23:52 ` [PATCH 1/2] nvmem: add ONIE nvmem provider Vadym Kochan
2020-09-21 23:52 ` [PATCH 2/2] dt-bindings: nvmem: add description for ONIE provider Vadym Kochan
2020-09-29 17:56 ` Rob Herring [this message]
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=20200929175632.GA860453@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=vadym.kochan@plvision.eu \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).