linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 00/18] Armada 370/XP watchdog
Date: Tue, 11 Feb 2014 05:31:23 -0300	[thread overview]
Message-ID: <20140211083122.GB3687@localhost> (raw)
In-Reply-To: <1392073237-2554-1-git-send-email-ezequiel.garcia@free-electrons.com>

On Mon, Feb 10, 2014 at 08:00:19PM -0300, Ezequiel Garcia wrote:
> Yet another round. This time, addressing Guenter's comment about the nowayout
> parameter. So, to allow for proper nowayout behavior, we now restrict the
> initial watchdog stop; which is only done if the watchdog is not properly
> enabled.
> 
> I've dropped the clocksource patch which was previously part of the series.
> The patch is independent and will be merged through the subsystem maintainer,
> Daniel Lezcano.
> 
> Also, I've updated the multi_v7_defconfig, as per Jason Cooper request.
> 
> This series depends on Sebastian's irqchip fixes to clear the bridge irqs
> cause, which Jason picked here:
> 
>   http://git.infradead.org/linux-mvebu.git mvebu-next/irqchip-fixes
> 
> Wim: Can we take all the watchdog changes through mvebu, with your Ack?
> This way, we can sort out the irqchip dependency.
> 

Wim: Do you have any comments about these patches?

-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  parent reply	other threads:[~2014-02-11  8:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 23:00 [PATCH v7 00/18] Armada 370/XP watchdog Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 01/18] watchdog: orion: Add clock error handling Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 02/18] watchdog: orion: Use atomic access for shared registers Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 03/18] watchdog: orion: Remove unused macros Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 04/18] watchdog: orion: Make sure the watchdog is initially stopped Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 05/18] watchdog: orion: Handle the interrupt so it's properly acked Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 06/18] watchdog: orion: Make RSTOUT register a separate resource Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 07/18] watchdog: orion: Remove unneeded BRIDGE_CAUSE clear Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 08/18] watchdog: orion: Introduce an orion_watchdog device structure Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 09/18] watchdog: orion: Introduce per-compatible of_device_id data Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 10/18] watchdog: orion: Add per-compatible clock initialization Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 11/18] watchdog: orion: Add per-compatible watchdog start implementation Ezequiel Garcia
2014-02-17 21:08   ` Jason Cooper
2014-02-17 21:11     ` Jason Cooper
2014-02-17 23:42       ` Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 12/18] watchdog: orion: Add support for Armada 370 and Armada XP SoC Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 13/18] ARM: mvebu: Enable Armada 370/XP watchdog in the devicetree Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 14/18] ARM: kirkwood: Add RSTOUT 'reg' entry to devicetree Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 15/18] ARM: dove: Enable Dove watchdog in the devicetree Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 16/18] watchdog: orion: Enable the build on ARCH_MVEBU Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 17/18] ARM: mvebu: Enable watchdog support in defconfig Ezequiel Garcia
2014-02-10 23:00 ` [PATCH v7 18/18] ARM: dove: Enable watchdog support in the defconfig Ezequiel Garcia
2014-02-11  8:31 ` Ezequiel Garcia [this message]
2014-02-17 22:09 ` [PATCH v7 00/18] Armada 370/XP watchdog Jason Cooper

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=20140211083122.GB3687@localhost \
    --to=ezequiel.garcia@free-electrons.com \
    --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).