From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fu Wei Subject: Re: [PATCH v7 2/8] ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts Date: Tue, 15 Sep 2015 18:15:50 +0800 Message-ID: References: <=fu.wei@linaro.org> <1440435683-7343-1-git-send-email-fu.wei@linaro.org> <1440435683-7343-3-git-send-email-fu.wei@linaro.org> <20150915084332.GC5767@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20150915084332.GC5767@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org To: Dave Young Cc: Suravee Suthikulpanit , Hanjun Guo , Linaro ACPI Mailman List , linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org, LKML , linux-doc@vger.kernel.org, Wei Fu , G Gregory , Al Stone , Arnd Bergmann , Guenter Roeck , Vipul Gandhi , Wim Van Sebroeck , Jon Masters , Leo Duran , Jon Corbet , Mark Rutland , Catalin Marinas , Will Deacon , Rafael Wysocki , Pratyush Anand List-Id: devicetree@vger.kernel.org Hi Dave, On 15 September 2015 at 16:43, Dave Young wrote: > On 08/25/15 at 01:01am, fu.wei@linaro.org wrote: >> From: Fu Wei >> >> 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 >> Signed-off-by: Fu Wei >> --- >> 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@2a440000 { >> + 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. yes, that is good idea, will make them to be the same. :-) > > 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.. Thanks for your info. So that means: we may need that long timeout support in the second stage. WOR is not enough for the second stage in most of kdump case. > >> + }; >> }; >> -- >> 2.4.3 >> -- Best regards, Fu Wei Software Engineer Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch Ph: +86 21 61221326(direct) Ph: +86 186 2020 4684 (mobile) Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021