From: "Alice Guo (OSS)" <alice.guo@oss.nxp.com>
To: robh+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, krzk@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: [PATCH v10 1/4] dt-bindings: soc: imx8m: add DT Binding doc for soc unique ID
Date: Mon, 4 Jan 2021 17:15:41 +0800 [thread overview]
Message-ID: <20210104091544.13972-1-alice.guo@oss.nxp.com> (raw)
From: Alice Guo <alice.guo@nxp.com>
Add DT Binding doc for the Unique ID of i.MX 8M series.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Alice Guo <alice.guo@nxp.com>
---
Changes for v10:
- add Reviewed-by
Changes for v9:
- add additionalProperties for "^soc@[0-9a-f]+$"
- add examples
Changes for v8:
- match soc node with regular expression
Changes for v7:
- change to a separate schema file
Changes for v6:
- none
Changes for v5:
- correct the error of using allOf
Changes for v4:
- use allOf to limit new version DTS files for i.MX8M to include
"fsl,imx8m*-soc", nvmem-cells and nvmem-cells-names
Changes for v3:
- put it into Documentation/devicetree/bindings/arm/fsl.yaml
- modify the description of nvmem-cells
- use "make ARCH=arm64 dtbs_check" to make sure it is right
Changes for v2:
- remove the subject prefix "LF-2571-1"
.../bindings/soc/imx/imx8m-soc.yaml | 86 +++++++++++++++++++
1 file changed, 86 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/imx/imx8m-soc.yaml
diff --git a/Documentation/devicetree/bindings/soc/imx/imx8m-soc.yaml b/Documentation/devicetree/bindings/soc/imx/imx8m-soc.yaml
new file mode 100644
index 000000000000..effcc72f9425
--- /dev/null
+++ b/Documentation/devicetree/bindings/soc/imx/imx8m-soc.yaml
@@ -0,0 +1,86 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/soc/imx/imx8m-soc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: NXP i.MX8M Series SoC
+
+maintainers:
+ - Alice Guo <alice.guo@nxp.com>
+
+description: |
+ NXP i.MX8M series SoCs contain fuse entries from which SoC Unique ID can be
+ obtained.
+
+select:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - fsl,imx8mm
+ - fsl,imx8mn
+ - fsl,imx8mp
+ - fsl,imx8mq
+ required:
+ - compatible
+
+patternProperties:
+ "^soc@[0-9a-f]+$":
+ type: object
+ properties:
+ compatible:
+ items:
+ - enum:
+ - fsl,imx8mm-soc
+ - fsl,imx8mn-soc
+ - fsl,imx8mp-soc
+ - fsl,imx8mq-soc
+ - const: simple-bus
+
+ "#address-cells":
+ const: 1
+
+ "#size-cells":
+ const: 1
+
+ ranges: true
+
+ dma-ranges: true
+
+ nvmem-cells:
+ maxItems: 1
+ description: Phandle to the SOC Unique ID provided by a nvmem node
+
+ nvmem-cell-names:
+ const: soc_unique_id
+
+ required:
+ - compatible
+ - nvmem-cells
+ - nvmem-cell-names
+
+ additionalProperties:
+ type: object
+
+additionalProperties: true
+
+examples:
+ - |
+ / {
+ model = "FSL i.MX8MM EVK board";
+ compatible = "fsl,imx8mm-evk", "fsl,imx8mm";
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ soc@0 {
+ compatible = "fsl,imx8mm-soc", "simple-bus";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0x0 0x0 0x0 0x3e000000>;
+ nvmem-cells = <&imx8mm_uid>;
+ nvmem-cell-names = "soc_unique_id";
+ };
+ };
+
+...
--
2.17.1
next reply other threads:[~2021-01-04 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 9:15 Alice Guo (OSS) [this message]
2021-01-04 9:15 ` [PATCH v10 2/4] arm64: dts: imx8m: add SoC ID compatible Alice Guo (OSS)
2021-01-04 9:15 ` [PATCH v10 3/4] arm64: dts: imx8m: add NVMEM provider and consumer to read soc unique ID Alice Guo (OSS)
2021-01-04 9:15 ` [PATCH v10 4/4] soc: imx8m: change to use platform driver Alice Guo (OSS)
2021-03-09 13:42 ` [PATCH] arm64: dts: imx8mq: remove SoC ID compatible Martin Kepplinger
2021-03-09 20:56 ` Krzysztof Kozlowski
2021-01-11 2:46 ` [PATCH v10 1/4] dt-bindings: soc: imx8m: add DT Binding doc for soc unique ID Shawn Guo
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=20210104091544.13972-1-alice.guo@oss.nxp.com \
--to=alice.guo@oss.nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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).