From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
Jason Cooper <jason@lakedaemon.net>,
Guenter Roeck <linux@roeck-us.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Wim Van Sebroeck <wim@iguana.be>
Subject: Re: [PATCH v3 0/8] Watchdog support for Armada 375/38x SoC
Date: Wed, 12 Mar 2014 18:54:56 -0300 [thread overview]
Message-ID: <20140312215456.GA13340@arch.cereza> (raw)
In-Reply-To: <20140312214312.GA14357@obsidianresearch.com>
On Mar 12, Jason Gunthorpe wrote:
> On Wed, Mar 12, 2014 at 06:11:47PM -0300, Ezequiel Garcia wrote:
>
> > I've pushed a branch so people can test this easily, e.g. ensuring
> > no regressions on Dove, Kirkwood and A370/XP:
> >
> > https://github.com/MISL-EBU-System-SW/mainline-public/tree/wdt_a385_a375_v3
>
> This branch worked for me, the watchdog functioned as expected.
>
Good to hear. Is that a Tested-by on Kirkwood?
> # killall -STOP wdt...
> ..
> .
> orion_wdt: Oops: Watchdog Timeout
> CPU: 0 PID: 0 Comm: swapper Not tainted 3.14.0-rc1-00205-g666e53f-dirty #1
> [..]
> <REBOOT>
>
> I got these two oddball messages during boot though:
>
> irq: Cannot allocate irq_descs @ IRQ26, assuming pre-allocated
> irq: Cannot allocate irq_descs @ IRQ61, assuming pre-allocated
>
> Probably unrelated to the watchdog.. Unfortunately I've run out of
> time right now to investigate.
>
Probably. That branch is based on some mvebu/for-next tip, which has all
the watchdog and devicetree dependencies for this patchset to apply.
I can re-send a series based on v3.15-rc1 and we can check again; maybe
we're just missing some irq patch.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Ezequiel Garcia <ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Lior Amsalem <alior-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
Tawfik Bayouk <tawfik-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
Thomas Petazzoni
<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Gregory Clement
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Wim Van Sebroeck <wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org>
Subject: Re: [PATCH v3 0/8] Watchdog support for Armada 375/38x SoC
Date: Wed, 12 Mar 2014 18:54:56 -0300 [thread overview]
Message-ID: <20140312215456.GA13340@arch.cereza> (raw)
In-Reply-To: <20140312214312.GA14357-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
On Mar 12, Jason Gunthorpe wrote:
> On Wed, Mar 12, 2014 at 06:11:47PM -0300, Ezequiel Garcia wrote:
>
> > I've pushed a branch so people can test this easily, e.g. ensuring
> > no regressions on Dove, Kirkwood and A370/XP:
> >
> > https://github.com/MISL-EBU-System-SW/mainline-public/tree/wdt_a385_a375_v3
>
> This branch worked for me, the watchdog functioned as expected.
>
Good to hear. Is that a Tested-by on Kirkwood?
> # killall -STOP wdt...
> ..
> .
> orion_wdt: Oops: Watchdog Timeout
> CPU: 0 PID: 0 Comm: swapper Not tainted 3.14.0-rc1-00205-g666e53f-dirty #1
> [..]
> <REBOOT>
>
> I got these two oddball messages during boot though:
>
> irq: Cannot allocate irq_descs @ IRQ26, assuming pre-allocated
> irq: Cannot allocate irq_descs @ IRQ61, assuming pre-allocated
>
> Probably unrelated to the watchdog.. Unfortunately I've run out of
> time right now to investigate.
>
Probably. That branch is based on some mvebu/for-next tip, which has all
the watchdog and devicetree dependencies for this patchset to apply.
I can re-send a series based on v3.15-rc1 and we can check again; maybe
we're just missing some irq patch.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
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-12 21:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 21:11 [PATCH v3 0/8] Watchdog support for Armada 375/38x SoC Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:11 ` [PATCH v3 1/8] watchdog: orion: Introduce a SoC-specific RSTOUT mapping Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:11 ` [PATCH v3 2/8] watchdog: orion: Remove unneeded atomic access Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:11 ` [PATCH v3 3/8] watchdog: orion: Introduce per-SoC stop() function Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:11 ` [PATCH v3 4/8] watchdog: orion: Introduce per-SoC enabled() function Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:11 ` [PATCH v3 5/8] watchdog: orion: Add Armada 375/380 SoC support Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:11 ` [PATCH v3 6/8] ARM: mvebu: Enable Armada 375 watchdog in the devicetree Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:11 ` [PATCH v3 7/8] ARM: mvebu: Enable Armada 380/385 " Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:11 ` [PATCH v3 8/8] ARM: mvebu: Add A375/A380 watchdog binding documentation Ezequiel Garcia
2014-03-12 21:11 ` Ezequiel Garcia
2014-03-12 21:43 ` [PATCH v3 0/8] Watchdog support for Armada 375/38x SoC Jason Gunthorpe
2014-03-12 21:43 ` Jason Gunthorpe
2014-03-12 21:54 ` Ezequiel Garcia [this message]
2014-03-12 21:54 ` Ezequiel Garcia
2014-03-19 22:21 ` Jason Gunthorpe
2014-03-19 22:21 ` Jason Gunthorpe
2014-03-14 22:21 ` Guenter Roeck
2014-03-14 22:21 ` Guenter Roeck
2014-03-14 22:35 ` Ezequiel Garcia
2014-03-14 22:35 ` 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=20140312215456.GA13340@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=linux@roeck-us.net \
--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 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.