[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150915094443.GA3296@dhcppc13.redhat.com>
Date: Tue, 15 Sep 2015 15:14:43 +0530
From: Pratyush Anand <panand@...hat.com>
To: Dave Young <dyoung@...hat.com>
Cc: fu.wei@...aro.org, Suravee.Suthikulpanit@....com,
hanjun.guo@...aro.org, linaro-acpi@...ts.linaro.org,
linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
tekkamanninja@...il.com, graeme.gregory@...aro.org,
al.stone@...aro.org, arnd@...db.de, linux@...ck-us.net,
vgandhi@...eaurora.org, wim@...ana.be, jcm@...hat.com,
leo.duran@....com, corbet@....net, mark.rutland@....com,
catalin.marinas@....com, will.deacon@....com, rjw@...ysocki.net,
Geoff Levand <geoff@...radead.org>
Subject: Re: [PATCH v7 2/8] ARM64: add SBSA Generic Watchdog device node in
foundation-v8.dts
On 15/09/2015:04:43:32 PM, Dave Young wrote:
> On 08/25/15 at 01:01am, fu.wei@...aro.org wrote:
> > From: Fu Wei <fu.wei@...aro.org>
> >
> > This can be a example of adding SBSA Generic Watchdog device node
> > into some dts files for the Soc which contains SBSA Generic Watchdog.
> >
> > Acked-by: Arnd Bergmann <arnd@...db.de>
> > Signed-off-by: Fu Wei <fu.wei@...aro.org>
> > ---
> > arch/arm64/boot/dts/arm/foundation-v8.dts | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/arm/foundation-v8.dts b/arch/arm64/boot/dts/arm/foundation-v8.dts
> > index 4eac8dc..824431f 100644
> > --- a/arch/arm64/boot/dts/arm/foundation-v8.dts
> > +++ b/arch/arm64/boot/dts/arm/foundation-v8.dts
> > @@ -237,4 +237,11 @@
> > };
> > };
> > };
> > + watchdog@...40000 {
> > + compatible = "arm,sbsa-gwdt";
> > + reg = <0x0 0x2a440000 0 0x1000>,
> > + <0x0 0x2a450000 0 0x1000>;
> > + interrupts = <0 27 4>;
> > + timeout-sec = <10 5>;
>
> I assume 10 is timeout, 5 is pre timeout, but in the driver code the default
> value is 30/10, I think the example dts[i] should use same default values as in code.
>
> BTW, for kdump kernel Pratyush is working on kdump on wdt enabled system.
> Basiclly we expect one configure longer timeout, and kick it in shorter
> period so we can get a chance to save vmcore. 10s sounds too short for the case..
Specially if D-cache is not enabled in ARM64 kexec-tool/purgatory then its more
than 2 min. Geoff has yet not agreed [1] to take D-cache support in purgatory.
[1] https://www.mail-archive.com/kexec@lists.infradead.org/msg12881.html
~Pratyush
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists