From: Abel Vesa <abel.vesa@nxp.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
Dong Aisheng <aisheng.dong@nxp.com>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 07/10] dt-bindings: arm: freescale: Add fsl,scu-rtc yaml file
Date: Tue, 7 Jun 2022 13:59:48 +0300 [thread overview]
Message-ID: <20220607105951.1821519-8-abel.vesa@nxp.com> (raw)
In-Reply-To: <20220607105951.1821519-1-abel.vesa@nxp.com>
This documents separately the rtc child node of the SCU main node.
Signed-off-by: Abel Vesa <abel.vesa@nxp.com>
---
.../bindings/arm/freescale/fsl,scu-rtc.yaml | 23 +++++++++++++++++++
1 file changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,scu-rtc.yaml
diff --git a/Documentation/devicetree/bindings/arm/freescale/fsl,scu-rtc.yaml b/Documentation/devicetree/bindings/arm/freescale/fsl,scu-rtc.yaml
new file mode 100644
index 000000000000..199617be4565
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/freescale/fsl,scu-rtc.yaml
@@ -0,0 +1,23 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/arm/freescale/fsl,scu-rtc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: i.MX SCU Client Device Node - RTC bindings based on SCU Message Protocol
+
+maintainers:
+ - Shawn Guo <shawnguo@kernel.org>
+
+description: i.MX SCU Client Device Node
+ Client nodes are maintained as children of the relevant IMX-SCU device node.
+
+properties:
+ compatible:
+ items:
+ - const: fsl,imx8qxp-sc-rtc
+
+additionalProperties: false
+
+required:
+ - compatible
--
2.34.3
next prev parent reply other threads:[~2022-06-07 11:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 10:59 [PATCH 00/10] dt-bindings: arm: freescale: Switch fsl,scu from txt to yaml Abel Vesa
2022-06-07 10:59 ` [PATCH 01/10] dt-bindings: arm: freescale: Switch fsl,scu " Abel Vesa
2022-06-07 15:43 ` Rob Herring
2022-06-07 16:28 ` Rob Herring
2022-06-08 12:07 ` Abel Vesa
2022-06-07 10:59 ` [PATCH 02/10] dt-bindings: arm: freescale: Add fsl,scu-clk yaml file Abel Vesa
2022-06-07 16:29 ` Rob Herring
2022-06-07 10:59 ` [PATCH 03/10] dt-bindings: arm: freescale: Add fsl,scu-iomux " Abel Vesa
2022-06-07 10:59 ` [PATCH 04/10] dt-bindings: arm: freescale: Add fsl,scu-key " Abel Vesa
2022-06-07 16:31 ` Rob Herring
2022-06-07 10:59 ` [PATCH 05/10] dt-bindings: arm: freescale: Add fsl,scu-ocotp " Abel Vesa
2022-06-07 10:59 ` [PATCH 06/10] dt-bindings: arm: freescale: Add fsl,scu-pd " Abel Vesa
2022-06-07 17:29 ` Krzysztof Kozlowski
2022-06-07 10:59 ` Abel Vesa [this message]
2022-06-07 17:30 ` [PATCH 07/10] dt-bindings: arm: freescale: Add fsl,scu-rtc " Krzysztof Kozlowski
2022-06-07 10:59 ` [PATCH 08/10] dt-bindings: arm: freescale: Add fsl,scu-thermal " Abel Vesa
2022-06-07 16:34 ` Rob Herring
2022-06-07 10:59 ` [PATCH 09/10] dt-bindings: arm: freescale: Add fsl,scu-wdt " Abel Vesa
2022-06-07 16:32 ` Rob Herring
2022-06-07 17:31 ` Krzysztof Kozlowski
2022-06-07 10:59 ` [PATCH 10/10] dt-bindings: arm: freescale: Remove fsl,scu txt file Abel Vesa
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=20220607105951.1821519-8-abel.vesa@nxp.com \
--to=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--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).