From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
Wim Van Sebroeck <wim@iguana.be>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>
Subject: Re: [PATCH v2 0/7] Watchdog support for Armada 375/38x SoC
Date: Tue, 4 Mar 2014 17:03:28 -0300 [thread overview]
Message-ID: <20140304200328.GA11316@arch.cereza> (raw)
In-Reply-To: <20140304175341.GO1872@titan.lakedaemon.net>
On Mar 04, Jason Cooper wrote:
> On Tue, Mar 04, 2014 at 01:07:17PM -0300, Ezequiel Garcia wrote:
> > Here's a new patchset adding support for watchdog on Armada 375 and
> > Armada 38x SoCs. Regarding the previous patchset, this time we're handling
> > the SoCs differences in the watchdog driver itself.
> >
> > The new Armada 375/385 SoCs have two registers for the watchdog RSTOUT:
> >
> > 1. It has a dedicated register (similar to the one in A370/XP)
> > 2. Also has a bit in a shared RSTOUT register.
> >
> > Therefore, in order to support this two-folded RSTOUT, we extend the 'reg'
> > property in the watchdog devicetree and require a new pair of cells to specify
> > the shared RSTOUT.
> >
> > On the driver side, we need to implement per-SoC stop() and enabled()
> > functions. Such somewhat complex infrastructure is needed to ensure the driver
> > performs proper reset of the watchdog timer, by masking and disabling the
> > RSTOUT before the interrupt is enabled.
> >
> > Changes from v1:
> >
> > * Reworked entirely!
> >
> > Ezequiel Garcia (7):
> > watchdog: orion: Introduce a SoC-specific RSTOUT mapping
> > watchdog: orion: Introduce per-SoC stop() function
> > watchdog: orion: Introduce per-SoC enabled() function
> > watchdog: orion: Add Armada 375/380 SoC support
> > ARM: mvebu: Enable Armada 375 watchdog in the devicetree
> > ARM: mvebu: Enable Armada 380/385 watchdog in the devicetree
> > ARM: mvebu: Add A375/A380 watchdog binding documentation
> >
> > .../devicetree/bindings/watchdog/marvel.txt | 7 +
> > arch/arm/boot/dts/armada-375.dtsi | 6 +
> > arch/arm/boot/dts/armada-38x.dtsi | 7 +
> > drivers/watchdog/orion_wdt.c | 167 +++++++++++++++++++--
> > 4 files changed, 177 insertions(+), 10 deletions(-)
>
> From a cursory look, this is a big improvement. Just one small note: I
> almost didn't see this, since I wasn't in the Cc. No need to resend, I
> bounced it around to the right folders so I can track it.
>
Ouch.. sorry about that. Of course, wasn't on purpose!
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-04 20:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 16:07 [PATCH v2 0/7] Watchdog support for Armada 375/38x SoC Ezequiel Garcia
2014-03-04 16:07 ` [PATCH v2 1/7] watchdog: orion: Introduce a SoC-specific RSTOUT mapping Ezequiel Garcia
2014-03-10 2:09 ` Guenter Roeck
2014-03-11 20:06 ` Ezequiel Garcia
2014-03-04 16:07 ` [PATCH v2 2/7] watchdog: orion: Introduce per-SoC stop() function Ezequiel Garcia
2014-03-10 2:30 ` Guenter Roeck
2014-03-04 16:07 ` [PATCH v2 3/7] watchdog: orion: Introduce per-SoC enabled() function Ezequiel Garcia
2014-03-10 2:30 ` Guenter Roeck
2014-03-04 16:07 ` [PATCH v2 4/7] watchdog: orion: Add Armada 375/380 SoC support Ezequiel Garcia
2014-03-10 2:12 ` Guenter Roeck
2014-03-11 20:16 ` Ezequiel Garcia
2014-03-04 16:07 ` [PATCH v2 5/7] ARM: mvebu: Enable Armada 375 watchdog in the devicetree Ezequiel Garcia
2014-03-04 16:07 ` [PATCH v2 6/7] ARM: mvebu: Enable Armada 380/385 " Ezequiel Garcia
2014-03-04 16:07 ` [PATCH v2 7/7] ARM: mvebu: Add A375/A380 watchdog binding documentation Ezequiel Garcia
2014-03-04 17:53 ` [PATCH v2 0/7] Watchdog support for Armada 375/38x SoC Jason Cooper
2014-03-04 20:03 ` Ezequiel Garcia [this message]
2014-03-07 0:13 ` Ezequiel Garcia
2014-03-11 21:45 ` Jason Gunthorpe
2014-03-12 21:12 ` Ezequiel Garcia
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=20140304200328.GA11316@arch.cereza \
--to=ezequiel.garcia@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wim@iguana.be \
/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