From: Joel Stanley <joel@jms.id.au>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Tomer Maimon <tmaimon77@gmail.com>,
Avi Fishman <avifishman70@gmail.com>,
Brendan Higgins <brendanhiggins@google.com>
Subject: [PATCH v3 0/2] watchdog: Add Nuvoton NPCM (Poleg) driver
Date: Fri, 9 Mar 2018 15:21:05 +1030 [thread overview]
Message-ID: <20180309045107.8515-1-joel@jms.id.au> (raw)
v3: Address comments from Guneter and Tomer, add Rob's review
v2: Address comments from Guenter and Marcus
This is a driver for the Poleg board that is in the process of being
upstreamed. I have tested it on an evaluation board.
The watchdog is a single register inside of the timer IP. This made me
think about how to describe the device tree bindings for a while, but
after some discussion I settled on describing the watchdog separately,
and giving it's own compatible string, and it's own driver.
The timer is being reviewed over here:
https://lkml.org/lkml/2018/2/26/492
Joel Stanley (2):
dt-bindings: watchdog: Add Nuvoton NPCM description
watchdog: Add Nuvoton NPCM watchdog driver
.../bindings/watchdog/nuvoton,npcm-wdt.txt | 28 +++
drivers/watchdog/Kconfig | 11 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/npcm_wdt.c | 254 +++++++++++++++++++++
4 files changed, 294 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/nuvoton,npcm-wdt.txt
create mode 100644 drivers/watchdog/npcm_wdt.c
--
2.15.1
next reply other threads:[~2018-03-09 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 4:51 Joel Stanley [this message]
2018-03-09 4:51 ` [PATCH v3 1/2] dt-bindings: watchdog: Add Nuvoton NPCM description Joel Stanley
2018-03-09 4:51 ` [PATCH v3 2/2] watchdog: Add Nuvoton NPCM watchdog driver Joel Stanley
2018-03-09 14:39 ` 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=20180309045107.8515-1-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=avifishman70@gmail.com \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marcus.folkesson@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tmaimon77@gmail.com \
--cc=wim@linux-watchdog.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
all inboxes | Powered by JetHome®