From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Shawn Guo" <shawnguo@kernel.org>, "Li Yang" <leoyang.li@nxp.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Frank Rowand" <frowand.list@gmail.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"Philipp Zabel" <p.zabel@pengutronix.de>
Subject: Re: [PATCH v2 15/20] dt-bindings: nvmem: add YAML schema for the sl28 vpd layout
Date: Mon, 12 Sep 2022 14:20:38 -0500 [thread overview]
Message-ID: <20220912192038.GA1661550-robh@kernel.org> (raw)
In-Reply-To: <20220901221857.2600340-16-michael@walle.cc>
On Fri, Sep 02, 2022 at 12:18:52AM +0200, Michael Walle wrote:
> Add a schema for the NVMEM layout on Kontron's sl28 boards.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> changes since v1:
> - add custom select
> - add description
> - add "additionalProperties: false", I wasn't sure if all the
> subnodes needs it. I'd say yes, but the brcm,nvram binding
> doesn't have them neither.
>
> .../nvmem/layouts/kontron,sl28-vpd.yaml | 67 +++++++++++++++++++
> 1 file changed, 67 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
>
> diff --git a/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml b/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
> new file mode 100644
> index 000000000000..0c180f29e880
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
> @@ -0,0 +1,67 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/layouts/kontron,sl28-vpd.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NVMEM layout of the Kontron SMARC-sAL28 vital product data
> +
> +maintainers:
> + - Michael Walle <michael@walle.cc>
> +
> +description:
> + The vital product data (VPD) of the sl28 boards contains a serial
> + number and a base MAC address. The actual MAC addresses for the
> + on-board ethernet devices are derived from this base MAC address by
> + adding an offset.
> +
> +# We need a select here so we don't match all nodes with 'user-otp'
> +select:
> + properties:
> + compatible:
> + contains:
> + const: kontron,sl28-vpd
> + required:
> + - compatible
> +
> +properties:
> + compatible:
> + items:
> + - const: kontron,sl28-vpd
> + - const: user-otp
> +
> + serial-number:
> + type: object
> + description: The board's serial number
> +
> + base-mac-address:
> + type: object
> + description:
> + Base MAC address for all on-module network interfaces. The first
> + argument of the phandle will be treated as an offset.
> +
> + properties:
> + "#nvmem-cell-cells":
You can't just add a new #.*-cells buried in a device binding. I'm fine
with the concept though having more than 1 user would be nice.
Any case that doesn't match foos->#foo-cells or has a default # of
cells if missing (as this does) has to be added to dtschema to decode it
properly. It won't really matter until there's a user with 2 or more
entries. I'm happy to do update the dtschema part, but I'd prefer to see
the schema in dtschema rather than the kernel.
Rob
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Shawn Guo" <shawnguo@kernel.org>, "Li Yang" <leoyang.li@nxp.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Frank Rowand" <frowand.list@gmail.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"Philipp Zabel" <p.zabel@pengutronix.de>
Subject: Re: [PATCH v2 15/20] dt-bindings: nvmem: add YAML schema for the sl28 vpd layout
Date: Mon, 12 Sep 2022 14:20:38 -0500 [thread overview]
Message-ID: <20220912192038.GA1661550-robh@kernel.org> (raw)
In-Reply-To: <20220901221857.2600340-16-michael@walle.cc>
On Fri, Sep 02, 2022 at 12:18:52AM +0200, Michael Walle wrote:
> Add a schema for the NVMEM layout on Kontron's sl28 boards.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> changes since v1:
> - add custom select
> - add description
> - add "additionalProperties: false", I wasn't sure if all the
> subnodes needs it. I'd say yes, but the brcm,nvram binding
> doesn't have them neither.
>
> .../nvmem/layouts/kontron,sl28-vpd.yaml | 67 +++++++++++++++++++
> 1 file changed, 67 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
>
> diff --git a/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml b/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
> new file mode 100644
> index 000000000000..0c180f29e880
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
> @@ -0,0 +1,67 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/layouts/kontron,sl28-vpd.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NVMEM layout of the Kontron SMARC-sAL28 vital product data
> +
> +maintainers:
> + - Michael Walle <michael@walle.cc>
> +
> +description:
> + The vital product data (VPD) of the sl28 boards contains a serial
> + number and a base MAC address. The actual MAC addresses for the
> + on-board ethernet devices are derived from this base MAC address by
> + adding an offset.
> +
> +# We need a select here so we don't match all nodes with 'user-otp'
> +select:
> + properties:
> + compatible:
> + contains:
> + const: kontron,sl28-vpd
> + required:
> + - compatible
> +
> +properties:
> + compatible:
> + items:
> + - const: kontron,sl28-vpd
> + - const: user-otp
> +
> + serial-number:
> + type: object
> + description: The board's serial number
> +
> + base-mac-address:
> + type: object
> + description:
> + Base MAC address for all on-module network interfaces. The first
> + argument of the phandle will be treated as an offset.
> +
> + properties:
> + "#nvmem-cell-cells":
You can't just add a new #.*-cells buried in a device binding. I'm fine
with the concept though having more than 1 user would be nice.
Any case that doesn't match foos->#foo-cells or has a default # of
cells if missing (as this does) has to be added to dtschema to decode it
properly. It won't really matter until there's a user with 2 or more
entries. I'm happy to do update the dtschema part, but I'd prefer to see
the schema in dtschema rather than the kernel.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Shawn Guo" <shawnguo@kernel.org>, "Li Yang" <leoyang.li@nxp.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Frank Rowand" <frowand.list@gmail.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"Philipp Zabel" <p.zabel@pengutronix.de>
Subject: Re: [PATCH v2 15/20] dt-bindings: nvmem: add YAML schema for the sl28 vpd layout
Date: Mon, 12 Sep 2022 14:20:38 -0500 [thread overview]
Message-ID: <20220912192038.GA1661550-robh@kernel.org> (raw)
In-Reply-To: <20220901221857.2600340-16-michael@walle.cc>
On Fri, Sep 02, 2022 at 12:18:52AM +0200, Michael Walle wrote:
> Add a schema for the NVMEM layout on Kontron's sl28 boards.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> changes since v1:
> - add custom select
> - add description
> - add "additionalProperties: false", I wasn't sure if all the
> subnodes needs it. I'd say yes, but the brcm,nvram binding
> doesn't have them neither.
>
> .../nvmem/layouts/kontron,sl28-vpd.yaml | 67 +++++++++++++++++++
> 1 file changed, 67 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
>
> diff --git a/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml b/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
> new file mode 100644
> index 000000000000..0c180f29e880
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml
> @@ -0,0 +1,67 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/layouts/kontron,sl28-vpd.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NVMEM layout of the Kontron SMARC-sAL28 vital product data
> +
> +maintainers:
> + - Michael Walle <michael@walle.cc>
> +
> +description:
> + The vital product data (VPD) of the sl28 boards contains a serial
> + number and a base MAC address. The actual MAC addresses for the
> + on-board ethernet devices are derived from this base MAC address by
> + adding an offset.
> +
> +# We need a select here so we don't match all nodes with 'user-otp'
> +select:
> + properties:
> + compatible:
> + contains:
> + const: kontron,sl28-vpd
> + required:
> + - compatible
> +
> +properties:
> + compatible:
> + items:
> + - const: kontron,sl28-vpd
> + - const: user-otp
> +
> + serial-number:
> + type: object
> + description: The board's serial number
> +
> + base-mac-address:
> + type: object
> + description:
> + Base MAC address for all on-module network interfaces. The first
> + argument of the phandle will be treated as an offset.
> +
> + properties:
> + "#nvmem-cell-cells":
You can't just add a new #.*-cells buried in a device binding. I'm fine
with the concept though having more than 1 user would be nice.
Any case that doesn't match foos->#foo-cells or has a default # of
cells if missing (as this does) has to be added to dtschema to decode it
properly. It won't really matter until there's a user with 2 or more
entries. I'm happy to do update the dtschema part, but I'd prefer to see
the schema in dtschema rather than the kernel.
Rob
next prev parent reply other threads:[~2022-09-12 19:21 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 22:18 [PATCH v2 00/20] nvmem: core: introduce NVMEM layouts Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 01/20] net: add helper eth_addr_add() Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 23:22 ` Randy Dunlap
2022-09-01 23:22 ` Randy Dunlap
2022-09-01 23:22 ` Randy Dunlap
2022-09-02 7:27 ` Michael Walle
2022-09-02 7:27 ` Michael Walle
2022-09-02 7:27 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 02/20] of: base: add of_parse_phandle_with_optional_args() Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 03/20] nvmem: core: add an index parameter to the cell Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-09 8:12 ` Srinivas Kandagatla
2022-09-09 8:12 ` Srinivas Kandagatla
2022-09-09 8:12 ` Srinivas Kandagatla
2022-09-01 22:18 ` [PATCH v2 04/20] nvmem: core: move struct nvmem_cell_info to nvmem-provider.h Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 05/20] nvmem: core: drop the removal of the cells in nvmem_add_cells() Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 06/20] nvmem: core: add nvmem_add_one_cell() Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-09 8:52 ` Srinivas Kandagatla
2022-09-09 8:52 ` Srinivas Kandagatla
2022-09-09 8:52 ` Srinivas Kandagatla
2022-09-01 22:18 ` [PATCH v2 07/20] nvmem: core: use nvmem_add_one_cell() in nvmem_add_cells_from_of() Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 08/20] nvmem: core: introduce NVMEM layouts Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 09/20] nvmem: core: add per-cell post processing Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 10/20] nvmem: core: allow to modify a cell before adding it Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 11/20] nvmem: imx-ocotp: replace global post processing with layouts Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-07 12:31 ` Michael Walle
2022-09-07 12:31 ` Michael Walle
2022-09-07 12:31 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 12/20] nvmem: cell: drop global cell_post_process Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 13/20] nvmem: core: drop priv pointer in post process callback Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-09 8:52 ` Srinivas Kandagatla
2022-09-09 8:52 ` Srinivas Kandagatla
2022-09-09 8:52 ` Srinivas Kandagatla
2022-09-09 8:58 ` Michael Walle
2022-09-09 8:58 ` Michael Walle
2022-09-09 8:58 ` Michael Walle
2022-09-09 9:08 ` Srinivas Kandagatla
2022-09-09 9:08 ` Srinivas Kandagatla
2022-09-09 9:08 ` Srinivas Kandagatla
2022-09-09 9:39 ` Michael Walle
2022-09-09 9:39 ` Michael Walle
2022-09-09 9:39 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 14/20] dt-bindings: mtd: relax the nvmem compatible string Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-08 12:21 ` Krzysztof Kozlowski
2022-09-08 12:21 ` Krzysztof Kozlowski
2022-09-08 12:21 ` Krzysztof Kozlowski
2022-09-01 22:18 ` [PATCH v2 15/20] dt-bindings: nvmem: add YAML schema for the sl28 vpd layout Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-08 12:22 ` Krzysztof Kozlowski
2022-09-08 12:22 ` Krzysztof Kozlowski
2022-09-08 12:22 ` Krzysztof Kozlowski
2022-09-12 19:20 ` Rob Herring [this message]
2022-09-12 19:20 ` Rob Herring
2022-09-12 19:20 ` Rob Herring
2022-09-13 14:21 ` Michael Walle
2022-09-13 14:21 ` Michael Walle
2022-09-13 14:21 ` Michael Walle
2022-09-22 9:22 ` Miquel Raynal
2022-09-22 9:22 ` Miquel Raynal
2022-09-22 9:22 ` Miquel Raynal
2022-09-01 22:18 ` [PATCH v2 16/20] nvmem: layouts: add sl28vpd layout Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 17/20] nvmem: core: export nvmem device size Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [PATCH v2 18/20] arm64: dts: ls1028a: sl28: get MAC addresses from VPD Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` [RFC PATCH v2 19/20] nvmem: layouts: rewrite the u-boot-env driver as a NVMEM layout Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-21 10:37 ` Miquel Raynal
2022-09-21 10:37 ` Miquel Raynal
2022-09-21 10:37 ` Miquel Raynal
2022-09-01 22:18 ` [RFC PATCH v2 20/20] nvmem: layouts: u-boot-env: add device node Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-01 22:18 ` Michael Walle
2022-09-21 9:58 ` [PATCH v2 00/20] nvmem: core: introduce NVMEM layouts Miquel Raynal
2022-09-21 9:58 ` Miquel Raynal
2022-09-21 9:58 ` Miquel Raynal
2022-09-22 21:22 ` Srinivas Kandagatla
2022-09-22 21:22 ` Srinivas Kandagatla
2022-09-22 21:22 ` Srinivas Kandagatla
2022-09-23 8:31 ` Miquel Raynal
2022-09-23 8:31 ` Miquel Raynal
2022-09-23 8:31 ` Miquel Raynal
2022-09-23 15:47 ` Miquel Raynal
2022-09-23 15:47 ` Miquel Raynal
2022-09-23 15:47 ` Miquel Raynal
2022-09-23 17:28 ` Michael Walle
2022-09-23 17:28 ` Michael Walle
2022-09-23 17:28 ` 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=20220912192038.GA1661550-robh@kernel.org \
--to=robh@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.zabel@pengutronix.de \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=shawnguo@kernel.org \
--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 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.