From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: [PATCH 0/5] v3u: add support for RWDT
Date: Fri, 18 Dec 2020 18:37:25 +0100 [thread overview]
Message-ID: <20201218173731.12839-1-wsa+renesas@sang-engineering.com> (raw)
Here is the series to enable the RWDT on V3U. I took the DTS patches
from the BSP, the rest was developed on mainline tree. Note that
currently, the bootloader does not unmask the RWDT reset for us. This is
why patch #5 is needed if you want a reboot. We need to see if this is
going to be added to the bootloader later. Also, while the normal
watchdog trigger works flawlessly, the 'reboot' command will triger a
OOPS. This is a known issue also present on other Gen3 SoCs and will
be addressed seperately soon.
Other than that, patch #1 should go in via watchdog, the rest via
Geert's various trees :)
Looking forward to comments.
Happy hacking and have a nice weekend!
Hoang Vo (2):
arm64: dts: renesas: r8a779a0: Add RWDT node
arm64: dts: renesas: falcon: Enable watchdog timer
Wolfram Sang (3):
dt-bindings: watchdog: renesas,wdt: add r8a779a0 (V3U) support
clk: renesas: r8a779a0: Add RWDT clocks
WIP soc: v3u: allow WDT reset
.../devicetree/bindings/watchdog/renesas,wdt.yaml | 1 +
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts | 5 +++++
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 10 ++++++++++
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 9 +++++++++
drivers/soc/renesas/rcar-rst.c | 8 ++++++++
5 files changed, 33 insertions(+)
--
2.29.2
next reply other threads:[~2020-12-18 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 17:37 Wolfram Sang [this message]
2020-12-18 17:37 ` [PATCH 1/5] dt-bindings: watchdog: renesas,wdt: add r8a779a0 (V3U) support Wolfram Sang
2020-12-22 9:01 ` Geert Uytterhoeven
2020-12-31 20:36 ` Rob Herring
2021-01-18 8:57 ` Wolfram Sang
2021-01-23 17:20 ` Guenter Roeck
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=20201218173731.12839-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.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).