From: Julien Panis <jpanis@baylibre.com>
To: nm@ti.com, vigneshr@ti.com, kristo@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] AM62x watchdog support
Date: Thu, 3 Nov 2022 19:14:38 +0100 [thread overview]
Message-ID: <20221103181440.232727-1-jpanis@baylibre.com> (raw)
This patch series adds support for AM62x watchdog.
Changes since v0:
- Mark MCU & WKUP watchdogs as reserved
Link: https://lore.kernel.org/all/20220630070826.11074-1-jpanis@baylibre.com/
Changes since v1:
- Rebase patch to v6.1-rc3
Link: https://lore.kernel.org/all/20220718122328.251602-1-jpanis@baylibre.com/
Julien Panis (2):
arm64: dts: ti: k3-am62: add watchdog nodes
arm64: dts: ti: k3-am625-sk: mark MCU and WKUP watchdogs as reserved
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 45 ++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 9 +++++
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 9 +++++
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 10 +++++
4 files changed, 73 insertions(+)
base-commit: 30a0b95b1335e12efef89dd78518ed3e4a71a763
--
2.37.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-03 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:14 Julien Panis [this message]
2022-11-03 18:14 ` [PATCH v2 1/2] arm64: dts: ti: k3-am62: add watchdog nodes Julien Panis
2022-11-03 18:14 ` [PATCH v2 2/2] arm64: dts: ti: k3-am625-sk: mark MCU and WKUP watchdogs as reserved Julien Panis
2022-11-03 21:47 ` Nishanth Menon
2022-11-03 22:36 ` Andrew Davis
2022-11-03 23:10 ` Nishanth Menon
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=20221103181440.232727-1-jpanis@baylibre.com \
--to=jpanis@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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