From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [RFC PATCH 3/4] dt-bindings: mtd: add OTP bindings
Date: Sat, 27 Mar 2021 11:09:20 -0600 [thread overview]
Message-ID: <20210327170920.GA249312@robh.at.kernel.org> (raw)
In-Reply-To: <20210322181949.2805-4-michael@walle.cc>
On Mon, Mar 22, 2021 at 07:19:48PM +0100, Michael Walle wrote:
> Flash devices can have one-time-programmable regions. Add a nvmem
> binding so they can be used as a nvmem provider.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> .../devicetree/bindings/mtd/mtd.yaml | 71 +++++++++++++++++++
> 1 file changed, 71 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mtd/mtd.yaml b/Documentation/devicetree/bindings/mtd/mtd.yaml
> index 321259aab0f6..2b852f91a6a9 100644
> --- a/Documentation/devicetree/bindings/mtd/mtd.yaml
> +++ b/Documentation/devicetree/bindings/mtd/mtd.yaml
> @@ -21,6 +21,25 @@ properties:
> based name) in order to ease flash device identification and/or
> describe what they are used for.
>
> +patternProperties:
> + "^otp(-[0-9]+)?":
Needs '$' on the end.
> + type: object
> + $ref: ../nvmem/nvmem.yaml#
> +
> + description: |
> + An OTP memory region. Some flashes provide a one-time-programmable
> + memory whose content can either be programmed by a user or is already
> + pre-programmed by the factory. Some flashes might provide both.
> +
> + properties:
> + compatible:
> + enum:
> + - mtd-user-otp
> + - mtd-factory-otp
> +
> + required:
> + - compatible
> +
> additionalProperties: true
>
> examples:
> @@ -36,4 +55,56 @@ examples:
> };
> };
>
> + - |
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + flash@0 {
> + reg = <0>;
> + compatible = "some,flash";
Soon (in linux-next, but off by default) this will be a warning for
undocumented compatible string. Use a real device.
> +
> + otp {
> + compatible = "mtd-user-otp";
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + serial-number@0 {
> + reg = <0 16>;
> + };
> + };
> + };
> + };
> +
> + - |
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + flash@0 {
> + reg = <0>;
> + compatible = "some,flash";
> +
> + otp-1 {
> + compatible = "mtd-factory-otp";
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + electronic-serial-number@0 {
> + reg = <0 8>;
> + };
> + };
> +
> + otp-2 {
> + compatible = "mtd-user-otp";
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + mac-address@0 {
> + reg = <0 6>;
> + };
> + };
> + };
> + };
The 2nd example is a superset of the 1st, so drop the first one.
Rob
next prev parent reply other threads:[~2021-03-27 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 18:19 [RFC PATCH 0/4] mtd: core: OTP nvmem provider support Michael Walle
2021-03-22 18:19 ` [RFC PATCH 1/4] nvmem: core: allow specifying of_node Michael Walle
2021-03-30 10:35 ` Srinivas Kandagatla
2021-03-22 18:19 ` [RFC PATCH 2/4] dt-bindings: mtd: add YAML schema for the generic MTD bindings Michael Walle
2021-03-27 17:04 ` Rob Herring
2021-03-22 18:19 ` [RFC PATCH 3/4] dt-bindings: mtd: add OTP bindings Michael Walle
2021-03-27 17:09 ` Rob Herring [this message]
2021-03-30 10:07 ` Michael Walle
2021-03-22 18:19 ` [RFC PATCH 4/4] mtd: core: add OTP nvmem provider support Michael Walle
2021-03-30 9:42 ` [RFC PATCH 0/4] mtd: core: " Srinivas Kandagatla
2021-03-30 9:49 ` Michael Walle
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=20210327170920.GA249312@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=srinivas.kandagatla@linaro.org \
--cc=vigneshr@ti.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: 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).