From: Animesh Agarwal <animeshagarwal28@gmail.com>
Cc: animeshagarwal28@gmail.com, Daniel Baluta <daniel.baluta@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH] dt-bindings: serial: nxp,sc16is7xx: Add missing child node
Date: Wed, 12 Jun 2024 22:24:55 +0530 [thread overview]
Message-ID: <20240612165457.103575-1-animeshagarwal28@gmail.com> (raw)
Add missing child node property clock-sc16is7xx to nxp,sc16is7xx.yaml. This
fixes the following warning upon running make dtbs_check:
./arch/arm64/boot/dts/freescale/fsl-ls1012a-frdm.dtb: serial@0:
Unevaluated properties are not allowed ('clock-sc16is7xx' was unexpected)
from schema $id: http://devicetree.org/schemas/serial/nxp,sc16is7xx.yaml#
Signed-off-by: Animesh Agarwal <animeshagarwal28@gmail.com>
Cc: Daniel Baluta <daniel.baluta@nxp.com>
---
.../bindings/serial/nxp,sc16is7xx.yaml | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml
index 5dec15b7e7c3..d572b7e76c39 100644
--- a/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml
+++ b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml
@@ -70,6 +70,25 @@ properties:
minimum: 0
maximum: 1
+ clock-sc16is7xx:
+ type: object
+
+ additionalProperties: false
+
+ properties:
+ compatible:
+ const: fixed-clock
+
+ "#clock-cells":
+ const: 0
+
+ clock-frequency: true
+
+ required:
+ - compatible
+ - "#clock-cells"
+ - clock-frequency
+
required:
- compatible
- reg
--
2.45.2
next reply other threads:[~2024-06-12 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 16:54 Animesh Agarwal [this message]
2024-06-12 18:09 ` Rob Herring
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=20240612165457.103575-1-animeshagarwal28@gmail.com \
--to=animeshagarwal28@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hvilleneuve@dimonoff.com \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®