From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kousik Sanagavarapu <five231003@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: watchdog: ti,davinci-wdt: convert to dtschema
Date: Fri, 26 Jul 2024 11:17:25 +0200 [thread overview]
Message-ID: <8c608d74-3c5b-4127-b4af-a91a5d6b82ea@kernel.org> (raw)
In-Reply-To: <20240725153711.16101-3-five231003@gmail.com>
On 25/07/2024 17:03, Kousik Sanagavarapu wrote:
> Convert txt bindings of TI's DaVinci/Keystone Watchdog Timer Controller
> to dtschema to allow for validation.
>
> While at it, change the order of the compatibles w.r.t. the txt binding
> to stay in sync with the existing DTS.
... and add power-domains property, because it is used somwhere?
>
> Signed-off-by: Kousik Sanagavarapu <five231003@gmail.com>
> ---
> .../bindings/watchdog/davinci-wdt.txt | 24 ---------
> .../bindings/watchdog/ti,davinci-wdt.yaml | 52 +++++++++++++++++++
> 2 files changed, 52 insertions(+), 24 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/watchdog/davinci-wdt.txt
> create mode 100644 Documentation/devicetree/bindings/watchdog/ti,davinci-wdt.yaml
>
> diff --git a/Documentation/devicetree/bindings/watchdog/davinci-wdt.txt b/Documentation/devicetree/bindings/watchdog/davinci-wdt.txt
> deleted file mode 100644
> index aa10b8ec36e2..000000000000
> --- a/Documentation/devicetree/bindings/watchdog/davinci-wdt.txt
> +++ /dev/null
> @@ -1,24 +0,0 @@
> -Texas Instruments DaVinci/Keystone Watchdog Timer (WDT) Controller
> -
...
> + - Kousik Sanagavarapu <five231003@gmail.com>
> +
> +description: |
> + TI's Watchdog Timer Controller for DaVinci and Keystone Processors.
> +
> + Datasheets
> +
> + Davinci DM646x - https://www.ti.com/lit/ug/spruer5b/spruer5b.pdf
> + Keystone - https://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf
> +
> +allOf:
> + - $ref: watchdog.yaml#
> +
> +properties:
> + compatible:
> + items:
> + - const: ti,keystone-wdt
> + - const: ti,davinci-wdt
Validate the DTS - you will see this is wrong. You miss davinci standing
alone (so oneOf).
Best regards,
Krzysztof
prev parent reply other threads:[~2024-07-26 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 15:03 [PATCH v2 0/2] ti: davinci, keystone: txt to yaml Kousik Sanagavarapu
2024-07-25 15:03 ` [PATCH v2 1/2] dt-bindings: timer: ti,davinci-timer: convert to dtschema Kousik Sanagavarapu
2024-07-26 9:15 ` Krzysztof Kozlowski
2024-07-25 15:03 ` [PATCH v2 2/2] dt-bindings: watchdog: ti,davinci-wdt: " Kousik Sanagavarapu
2024-07-26 9:17 ` Krzysztof Kozlowski [this message]
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=8c608d74-3c5b-4127-b4af-a91a5d6b82ea@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=five231003@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=wim@linux-watchdog.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