From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Jason Cooper <jason@lakedaemon.net>,
Wim Van Sebroeck <wim@iguana.be>,
Guenter Roeck <linux@roeck-us.net>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Andrew Lunn <andrew@lunn.ch>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>
Subject: Re: [PATCH v4 0/9] Watchdog support for Armada 375/38x SoC
Date: Mon, 17 Mar 2014 20:10:58 +0100 [thread overview]
Message-ID: <532748C2.9030009@gmail.com> (raw)
In-Reply-To: <1394907484-26002-1-git-send-email-ezequiel.garcia@free-electrons.com>
On 03/15/2014 07:17 PM, Ezequiel Garcia wrote:
> Fourth round of the patchset adding support for watchdog on Armada 375 and
> Armada 38x SoCs.
>
> 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.
>
> I've pushed a branch so people can test this easily, e.g. ensuring
> no regressions on Dove, Kirkwood and A370/XP:
Ezequiel,
Although, I just saw below that you actually already tested on Dove,
you can add my
Tested-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> https://github.com/MISL-EBU-System-SW/mainline-public/tree/wdt_a385_a375_v4
>
> Series based on today's mvebu for-next. Will send a rebased version on top of
> v3.15-rc1. Tested on A375-DB, A385-DB, A370-RD and Dove Cubox.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/9] Watchdog support for Armada 375/38x SoC
Date: Mon, 17 Mar 2014 20:10:58 +0100 [thread overview]
Message-ID: <532748C2.9030009@gmail.com> (raw)
In-Reply-To: <1394907484-26002-1-git-send-email-ezequiel.garcia@free-electrons.com>
On 03/15/2014 07:17 PM, Ezequiel Garcia wrote:
> Fourth round of the patchset adding support for watchdog on Armada 375 and
> Armada 38x SoCs.
>
> 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.
>
> I've pushed a branch so people can test this easily, e.g. ensuring
> no regressions on Dove, Kirkwood and A370/XP:
Ezequiel,
Although, I just saw below that you actually already tested on Dove,
you can add my
Tested-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> https://github.com/MISL-EBU-System-SW/mainline-public/tree/wdt_a385_a375_v4
>
> Series based on today's mvebu for-next. Will send a rebased version on top of
> v3.15-rc1. Tested on A375-DB, A385-DB, A370-RD and Dove Cubox.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ezequiel Garcia
<ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
Wim Van Sebroeck <wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org>,
Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Thomas Petazzoni
<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Gregory Clement
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Lior Amsalem <alior-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
Tawfik Bayouk <tawfik-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH v4 0/9] Watchdog support for Armada 375/38x SoC
Date: Mon, 17 Mar 2014 20:10:58 +0100 [thread overview]
Message-ID: <532748C2.9030009@gmail.com> (raw)
In-Reply-To: <1394907484-26002-1-git-send-email-ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
On 03/15/2014 07:17 PM, Ezequiel Garcia wrote:
> Fourth round of the patchset adding support for watchdog on Armada 375 and
> Armada 38x SoCs.
>
> 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.
>
> I've pushed a branch so people can test this easily, e.g. ensuring
> no regressions on Dove, Kirkwood and A370/XP:
Ezequiel,
Although, I just saw below that you actually already tested on Dove,
you can add my
Tested-by: Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> https://github.com/MISL-EBU-System-SW/mainline-public/tree/wdt_a385_a375_v4
>
> Series based on today's mvebu for-next. Will send a rebased version on top of
> v3.15-rc1. Tested on A375-DB, A385-DB, A370-RD and Dove Cubox.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-17 19:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 18:17 [PATCH v4 0/9] Watchdog support for Armada 375/38x SoC Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:17 ` [PATCH v4 1/9] watchdog: orion: Move the register ioremap'ing to its own function Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 21:25 ` Guenter Roeck
2014-03-15 21:25 ` Guenter Roeck
2014-03-15 21:25 ` Guenter Roeck
2014-03-15 18:17 ` [PATCH v4 2/9] watchdog: orion: Introduce a SoC-specific RSTOUT mapping Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:17 ` [PATCH v4 3/9] watchdog: orion: Remove unneeded atomic access Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:17 ` [PATCH v4 4/9] watchdog: orion: Introduce per-SoC stop() function Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:17 ` Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 5/9] watchdog: orion: Introduce per-SoC enabled() function Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 6/9] watchdog: orion: Add Armada 375/380 SoC support Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 7/9] ARM: mvebu: Enable Armada 375 watchdog in the devicetree Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 8/9] ARM: mvebu: Enable Armada 380/385 " Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 9/9] ARM: mvebu: Add A375/A380 watchdog binding documentation Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-15 18:18 ` Ezequiel Garcia
2014-03-17 19:10 ` Sebastian Hesselbarth [this message]
2014-03-17 19:10 ` [PATCH v4 0/9] Watchdog support for Armada 375/38x SoC Sebastian Hesselbarth
2014-03-17 19:10 ` Sebastian Hesselbarth
2014-03-17 20:47 ` Ezequiel Garcia
2014-03-17 20:47 ` Ezequiel Garcia
2014-03-17 20:47 ` 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=532748C2.9030009@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.