From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: jason@lakedaemon.net, andrew@lunn.ch,
gregory.clement@bootlin.com, linux@roeck-us.net
Cc: linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v2 0/3] watchdog: orion_wdt: add pretimeout support
Date: Wed, 6 Mar 2019 09:19:21 +1300 [thread overview]
Message-ID: <20190305201924.14853-1-chris.packham@alliedtelesis.co.nz> (raw)
It appears that the kernel has only ever used timer0 on the armada platforms so
timer1 appears to be spare on these. Timers 2 and 3 are also free which could
be used if it is deemed that timer1 should be kept for some other purpose.
Chris Packham (3):
ARM: dts: armada-38x: add interrupts for watchdog
watchdog: orion: remove orion_wdt_set_timeout
watchdog: orion_wdt: use timer1 as a pretimeout
Changes in v2:
I've reduced this to just touching the Armada-38x. It would probably
also work on Armada-XP just by adding the appropriate interrupt nodes
to the dts. I don't have access to the Armada-370 datasheet but it'd
likely work there as well..
arch/arm/boot/dts/armada-38x.dtsi | 2 +
drivers/watchdog/orion_wdt.c | 67 +++++++++++++++++++++++--------
2 files changed, 52 insertions(+), 17 deletions(-)
--
2.21.0
next reply other threads:[~2019-03-05 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 20:19 Chris Packham [this message]
2019-03-05 20:19 ` [PATCH v2 1/3] ARM: dts: armada-38x: add interrupts for watchdog Chris Packham
2019-03-05 21:30 ` Guenter Roeck
2019-04-21 17:24 ` Gregory CLEMENT
2019-03-05 20:19 ` [PATCH v2 2/3] watchdog: orion: remove orion_wdt_set_timeout Chris Packham
2019-03-05 20:19 ` [PATCH v2 3/3] watchdog: orion_wdt: use timer1 as a pretimeout Chris Packham
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=20190305201924.14853-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).