From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 0/3] watchdog: Add Amlogic Meson GXBB Watchdog Timer driver
Date: Sun, 10 Jul 2016 11:11:03 +0200 [thread overview]
Message-ID: <1468141867-4172-1-git-send-email-narmstrong@baylibre.com> (raw)
Adds support for the Amlogic Meson GXBB SoC Watchdog Timer.
It differs from the meson6/meson8b HW, so need for a separate driver.
The HW provides a divider capable of having a 1ms timebase thus simplifying
the counter update.
The restart call is not provided even if the HW is capable of triggering a
system reset immediately because of the PSCI firmare having such functionnality.
The watchdog is not expected to be running at boot time since there is a separate
system-level watchdog running from the SCPI co-processor, but this case would be
handle in a next driver update.
Changes since v2 at http://lkml.kernel.org/r/1464943007-18000-1-git-send-email-narmstrong at baylibre.com :
- Fix set_timeout behaviour
Changes since v1 at http://lkml.kernel.org/r/1464614948-28247-1-git-send-email-narmstrong at baylibre.com :
- Update default timeout to 30sec
- Add separate CONFIG_
- Remove unused defines & functions
- Fix indentation
- Check set_timeout max value
- Reorder includes alphabetically
- Switch to human identify string
- clk_disable_unprepare on probe failure or removal
Changes since RFC version at http://lkml.kernel.org/r/1464249112-13658-1-git-send-email-narmstrong at baylibre.com :
- Remove status callback, will re-introduce it later to managed the already-running use case
- Fix registers defines indentation
- Fix space between operators
- Make all callbacks static functions
- Fix bindings with missing clocks attribute
- Do not stop/start watchdog on a timeout setup
- Fix probe device configuration
Neil Armstrong (3):
watchdog: Add Meson GXBB Watchdog Driver
dt-bindings: watchdog: Add Meson GXBB Watchdog bindings
ARM64: dts: amlogic: meson-gxbb: Add watchdog node
.../bindings/watchdog/meson-gxbb-wdt.txt | 16 ++
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 6 +
drivers/watchdog/Kconfig | 10 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/meson_gxbb_wdt.c | 270 +++++++++++++++++++++
5 files changed, 303 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/meson-gxbb-wdt.txt
create mode 100644 drivers/watchdog/meson_gxbb_wdt.c
--
2.7.0
next reply other threads:[~2016-07-10 9:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 9:11 Neil Armstrong [this message]
2016-07-10 9:11 ` [PATCH v3 1/3] watchdog: Add Meson GXBB Watchdog Driver Neil Armstrong
2016-07-10 16:02 ` Guenter Roeck
2016-07-10 9:11 ` [PATCH v3 2/3] dt-bindings: watchdog: Add Meson GXBB Watchdog bindings Neil Armstrong
2016-07-10 16:02 ` Guenter Roeck
2016-07-10 9:11 ` [PATCH v3 3/3] ARM64: dts: amlogic: meson-gxbb: Add watchdog node Neil Armstrong
2016-07-10 16:03 ` Guenter Roeck
2016-07-12 4:12 ` Kevin Hilman
2016-08-04 0:27 ` Kevin Hilman
2016-08-04 0:29 ` Kevin Hilman
2016-08-15 20:40 ` Kevin Hilman
2016-08-16 1:51 ` Guenter Roeck
2016-08-16 13:10 ` Kevin Hilman
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=1468141867-4172-1-git-send-email-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@lists.infradead.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).