From: Kousik Sanagavarapu <five231003@gmail.com>
To: 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,
Kousik Sanagavarapu <five231003@gmail.com>
Subject: [PATCH v4 0/2] ti: davinci, keystone: txt to yaml
Date: Sat, 27 Jul 2024 10:34:42 +0530 [thread overview]
Message-ID: <20240727050736.4756-1-five231003@gmail.com> (raw)
Convert txt bindings of DaVinci Timer and DaVinci/Keystone WDT
Controller to dtschema.
v3: https://lore.kernel.org/linux-devicetree/20240726150537.6873-1-five231003@gmail.com/
Changes since v3:
- No changes in 1/2.
- Explain why "power-domians" is needed in the commit msg and also add
the Reviewed-by tag.
v2: https://lore.kernel.org/linux-devicetree/20240725153711.16101-1-five231003@gmail.com/
Changes since v2:
- Add Reviewed-by tag on 1/2.
- Change the compatible to match the DTS on 2/2 and also mention in the
commit msg that we are adding "power-domins" as an extra optional
property, which was missing in txt binding.
v1: https://lore.kernel.org/linux-devicetree/20240721170840.15569-1-five231003@gmail.com/
Changes vs v1:
- Change davinci timer binding's file name to match with the compatible.
Also add "maxItems" for interrupts.
- Change the order of compatibles in wdt controller bindings touched in
order to match DTS.
- Drop 3/3 from v1 which might effect users and should not have been
included in this series in the first place.
Kousik Sanagavarapu (2):
dt-bindings: timer: ti,davinci-timer: convert to dtschema
dt-bindings: watchdog: ti,davinci-wdt: convert to dtschema
.../bindings/timer/ti,da830-timer.yaml | 68 +++++++++++++++++++
.../bindings/timer/ti,davinci-timer.txt | 37 ----------
.../bindings/watchdog/davinci-wdt.txt | 24 -------
.../bindings/watchdog/ti,davinci-wdt.yaml | 55 +++++++++++++++
4 files changed, 123 insertions(+), 61 deletions(-)
create mode 100644 Documentation/devicetree/bindings/timer/ti,da830-timer.yaml
delete mode 100644 Documentation/devicetree/bindings/timer/ti,davinci-timer.txt
delete mode 100644 Documentation/devicetree/bindings/watchdog/davinci-wdt.txt
create mode 100644 Documentation/devicetree/bindings/watchdog/ti,davinci-wdt.yaml
--
2.45.2.827.g557ae147e6.dirty
next reply other threads:[~2024-07-27 5:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 5:04 Kousik Sanagavarapu [this message]
2024-07-27 5:04 ` [PATCH v4 1/2] dt-bindings: timer: ti,davinci-timer: convert to dtschema Kousik Sanagavarapu
2024-08-13 15:45 ` Rob Herring (Arm)
2024-07-27 5:04 ` [PATCH v4 2/2] dt-bindings: watchdog: ti,davinci-wdt: " Kousik Sanagavarapu
2024-08-13 15:45 ` Rob Herring (Arm)
2024-08-05 7:06 ` [PATCH v4 0/2] ti: davinci, keystone: txt to yaml Kousik Sanagavarapu
2024-08-05 14:44 ` Rob Herring
2024-08-05 15:33 ` Kousik Sanagavarapu
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=20240727050736.4756-1-five231003@gmail.com \
--to=five231003@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).