From: Phil Edworthy <phil.edworthy@renesas.com>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Phil Edworthy <phil.edworthy@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH v4 0/2] arm64: renesas: Add RZ/V2M watchdog support
Date: Tue, 23 Aug 2022 10:32:31 +0100 [thread overview]
Message-ID: <20220823093233.8577-1-phil.edworthy@renesas.com> (raw)
Hello all,
This patch series adds support for the Watchdog Timer (WDT) in the
RZ/V2M SoC.
v4:
- driver: Fix enum names from I2C_* to WDT_*
- driver: Change cast from of_device_get_match_data() to avoid clang warning
v3:
- dt-bindings: Add check for too many interrupts or clocks
- driver: Don't call pm_runtime_get_sync() in restart()
- driver: Use mdelay instead of udelay, avoids DIV64_U64_ROUND_UP
v2:
- dt-bindings: Added minItems for interrupt-names and clock-names
- driver: Replace use of parity error registers in restart
- driver: Commit msg modified to reflect different contents
Phil Edworthy (2):
dt-bindings: watchdog: renesas,wdt: Add r9a09g011 (RZ/V2M) support
watchdog: rzg2l_wdt: Add rzv2m support
.../bindings/watchdog/renesas,wdt.yaml | 73 +++++++++++++------
drivers/watchdog/rzg2l_wdt.c | 39 ++++++++--
2 files changed, 85 insertions(+), 27 deletions(-)
--
2.34.1
next reply other threads:[~2022-08-23 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 9:32 Phil Edworthy [this message]
2022-08-23 9:32 ` [PATCH v4 1/2] dt-bindings: watchdog: renesas,wdt: Add r9a09g011 (RZ/V2M) support Phil Edworthy
2022-09-25 14:41 ` Guenter Roeck
2022-08-23 9:32 ` [PATCH v4 2/2] watchdog: rzg2l_wdt: Add rzv2m support Phil Edworthy
2022-09-25 14:41 ` 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=20220823093233.8577-1-phil.edworthy@renesas.com \
--to=phil.edworthy@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).