From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 01/15] watchdog: orion: Remove unneeded BRIDGE_CAUSE clear
Date: Tue, 27 Aug 2013 16:11:17 -0600 [thread overview]
Message-ID: <20130827221117.GA1324@obsidianresearch.com> (raw)
In-Reply-To: <20130827220431.GJ19598@titan.lakedaemon.net>
On Tue, Aug 27, 2013 at 06:04:31PM -0400, Jason Cooper wrote:
> I understand that they both *can* use it. Do any distro's actually use
> it in default configurations? Do any users actually load it and kick
> the dog in their main loop?
watchdog is always fully optional in distros. Even in x86 where there
is watchdog hardware on every new chipset. It is rare to even see the
kernel modules to enable watchdog loaded (they don't autoprobe for
some reason), let alone the userspace to tickle it.
> I don't have the answers to those questions, but I'd be surprised if it
> was more than a few specialty users.
I thought things were now at the point where orion5x/etc were just
needing a dts file and testing? Is there any more code work required?
Sebastian's IRQ and timer changes seemed like the last of it?
> </pokes self> Once pxa-impedance-matcher can edit the dtb, those users
> would have a means to upgrade to a DT enabled kernel without bootloader
> modifications... I really gotta get back to that. :)
Doesn't appended dtb already work?
I didn't think bootloader support was a gating item to run with DT??
Jason
next prev parent reply other threads:[~2013-08-27 22:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 14:34 [PATCH 00/15] Armada 370/XP watchdog support Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 01/15] watchdog: orion: Remove unneeded BRIDGE_CAUSE clear Ezequiel Garcia
2013-08-27 14:39 ` Thomas Petazzoni
2013-08-27 15:11 ` Ezequiel Garcia
2013-08-27 15:25 ` Jason Cooper
2013-08-27 19:13 ` Ezequiel Garcia
2013-08-27 20:04 ` Sebastian Hesselbarth
2013-08-27 21:02 ` Jason Gunthorpe
2013-08-27 21:41 ` Jason Cooper
2013-08-27 21:55 ` Thomas Petazzoni
2013-08-27 22:04 ` Jason Cooper
2013-08-27 22:11 ` Jason Gunthorpe [this message]
2013-08-28 12:02 ` Jason Cooper
2013-09-05 16:32 ` Gregory CLEMENT
2013-08-27 22:17 ` Ezequiel Garcia
2013-08-27 22:25 ` Jason Gunthorpe
2013-08-28 12:08 ` Ezequiel Garcia
2013-08-28 16:33 ` Jason Gunthorpe
2013-10-01 11:55 ` Jason Cooper
2014-01-17 15:48 ` Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 02/15] ARM: orion: Assert watchdog RSTOUT enable bit Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 03/15] ARM: mvebu: Add watchdog RSTOUT enable in system-controller init Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 04/15] watchdog: orion: Remove RSTOUT bit enable/disable Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 05/15] watchdog: orion: Allow to build in any Orion platform Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 06/15] watchdog: orion: Introduce an orion_watchdog device structure Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 07/15] watchdog: orion: Introduce per-compatible of_device_id data Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 08/15] watchdog: orion: Add per-compatible clock initialization Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 09/15] watchdog: orion: Add support for Armada 370 and Armada XP SoC Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 10/15] ARM: mvebu: Add RSTOUT cell to system-controller DT node Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 11/15] ARM: mvebu: Enable Armada 370/XP watchdog in the devicetree Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 12/15] watchdog: orion: Rename device-tree binding documentation Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 13/15] watchdog: orion: Add other compatibles to devicetree binding Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 14/15] ARM: mvebu: system-controller: Add second reg cell devicetree specification Ezequiel Garcia
2013-08-27 14:34 ` [PATCH 15/15] ARM: mvebu: Enable watchdog in defconfig Ezequiel Garcia
2013-08-27 15:06 ` [PATCH 00/15] Armada 370/XP watchdog support 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=20130827221117.GA1324@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.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).