From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND/PATCH v4 0/9] Watchdog support for Armada 375/38x SoC
Date: Thu, 24 Apr 2014 00:51:53 -0400 [thread overview]
Message-ID: <20140424045153.GU28159@titan.lakedaemon.net> (raw)
In-Reply-To: <1397481813-4962-1-git-send-email-ezequiel.garcia@free-electrons.com>
On Mon, Apr 14, 2014 at 10:23:24AM -0300, Ezequiel Garcia wrote:
> Here's the fourth round of the patchset adding support for watchdog
> on Armada 375 and Armada 38x SoCs, rebased on v3.15-rc1 and with
> collected Tested-by's.
>
> 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.
>
> Tested on A375-DB, A385-DB, A370-RD and Dove Cubox. Sebastian did more tests
> on Dove, and Jason Gunthorpe on Kirkwood.
Applied patches 7 and 8 to mvebu/dt. For the rest,
Acked-by: Jason Cooper <jason@lakedaemon.net>
thx,
Jason.
next prev parent reply other threads:[~2014-04-24 4:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 13:23 [RESEND/PATCH v4 0/9] Watchdog support for Armada 375/38x SoC Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 1/9] watchdog: orion: Move the register ioremap'ing to its own function Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 2/9] watchdog: orion: Introduce a SoC-specific RSTOUT mapping Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 3/9] watchdog: orion: Remove unneeded atomic access Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 4/9] watchdog: orion: Introduce per-SoC stop() function Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 5/9] watchdog: orion: Introduce per-SoC enabled() function Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 6/9] watchdog: orion: Add Armada 375/380 SoC support Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 7/9] ARM: mvebu: Enable Armada 375 watchdog in the devicetree Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 8/9] ARM: mvebu: Enable Armada 380/385 " Ezequiel Garcia
2014-04-14 13:23 ` [RESEND/PATCH v4 9/9] ARM: mvebu: Add A375/A380 watchdog binding documentation Ezequiel Garcia
2014-04-24 4:51 ` Jason Cooper [this message]
2014-04-24 11:06 ` [RESEND/PATCH v4 0/9] Watchdog support for Armada 375/38x SoC Ezequiel Garcia
2014-05-06 20:42 ` Ezequiel Garcia
[not found] ` <20140507142705.GE1484@spo001.leaseweb.com>
2014-05-07 14:36 ` Ezequiel Garcia
2014-05-15 12:42 ` Ezequiel Garcia
2014-05-19 12:37 ` Ezequiel Garcia
[not found] ` <20140519130429.GP1484@spo001.leaseweb.com>
2014-05-21 22:47 ` Ezequiel Garcia
[not found] ` <20140526205305.GA23347@spo001.leaseweb.com>
2014-05-26 21:04 ` 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=20140424045153.GU28159@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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).