From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/2] ARM: mediatek: Add watchdog driver
Date: Tue, 13 Jan 2015 13:28:54 +0100 [thread overview]
Message-ID: <1421152136-5007-1-git-send-email-matthias.bgg@gmail.com> (raw)
Mediatek SoCs have a watchdog driver. This patch set adds driver and DTS
binding. The driver also implements a restart handler to reboot the SoC.
Changes for v5:
- add newline in dev_info message
- add tested-by and reviewed-by
Changes for v4:
- fix indentation errors
- delete unused include
- reorganize while loop to eliminate code duplication
- eliminate indirection to watchdog_device structure
- delete unnecessary brackets
Changes for v3:
- fix based on file name
- fix style problems
- fix error return value and warning message
- delete unnecessary watchdog_set_drvdata
- delete unused variable
Changes for v2:
- we don't need to have the watchdog enabled to do a software reset
- disable dual mode and irq mode when starting the watchdog
- update commit message to name the SoCs the driver supports
Matthias Brugger (2):
watchdog: Add driver for Mediatek watchdog
ARM: mediatek: dts: Add bindings for watchdog
.../devicetree/bindings/watchdog/mtk-wdt.txt | 13 ++
drivers/watchdog/Kconfig | 10 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/mtk_wdt.c | 252 +++++++++++++++++++++
4 files changed, 276 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/mtk-wdt.txt
create mode 100644 drivers/watchdog/mtk_wdt.c
--
1.9.1
next reply other threads:[~2015-01-13 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 12:28 Matthias Brugger [this message]
2015-01-13 12:28 ` [PATCH v5 1/2] watchdog: Add driver for Mediatek watchdog Matthias Brugger
2015-01-13 12:28 ` [PATCH v5 2/2] ARM: mediatek: dts: Add bindings for watchdog Matthias Brugger
2015-01-23 14:20 ` [PATCH v5 0/2] ARM: mediatek: Add watchdog driver Matthias Brugger
2015-01-23 17:01 ` 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=1421152136-5007-1-git-send-email-matthias.bgg@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=linux-arm-kernel@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).