linux-kernel - Re: [PATCH v2 6/7] Watchdog: introduce ARM SBSA watchdog driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150521151847.GA16668@roeck-us.net>
Date:	Thu, 21 May 2015 08:18:47 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Fu Wei <fu.wei@...aro.org>
Cc:	Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>,
	Linaro ACPI Mailman List <linaro-acpi@...ts.linaro.org>,
	linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
	Wei Fu <tekkamanninja@...il.com>,
	G Gregory <graeme.gregory@...aro.org>,
	Al Stone <al.stone@...aro.org>,
	Hanjun Guo <hanjun.guo@...aro.org>,
	Timur Tabi <timur@...eaurora.org>,
	Ashwin Chaugule <ashwin.chaugule@...aro.org>,
	Arnd Bergmann <arnd@...db.de>, vgandhi@...eaurora.org,
	wim@...ana.be, Jon Masters <jcm@...hat.com>,
	Leo Duran <leo.duran@....com>, Jon Corbet <corbet@....net>,
	Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH v2 6/7] Watchdog: introduce ARM SBSA watchdog driver

On Thu, May 21, 2015 at 07:08:34PM +0800, Fu Wei wrote:
> Hi Guenter,
> 
> Thanks for review :-)
> 
> On 21 May 2015 at 18:34, Guenter Roeck <linux@...ck-us.net> wrote:
> > On 05/21/2015 01:32 AM, fu.wei@...aro.org wrote:
> >>
> >> From: Fu Wei <fu.wei@...aro.org>
> >>
> >> This driver bases on linux kernel watchdog framework, and
> >> use "pretimeout" in the framework. It supports getting timeout and
> >> pretimeout from parameter and FDT at the driver init stage.
> >> In first timeout(WS0), the interrupt routine run panic to save
> >> system context.
> >>
> >> Signed-off-by: Fu Wei <fu.wei@...aro.org>
> >> ---
> >>   drivers/watchdog/Kconfig     |  12 ++
> >>   drivers/watchdog/Makefile    |   1 +
> >>   drivers/watchdog/sbsa_gwdt.c | 476
> >> +++++++++++++++++++++++++++++++++++++++++++
> >>   3 files changed, 489 insertions(+)
> >>   create mode 100644 drivers/watchdog/sbsa_gwdt.c
> >>
> >> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> >> index e5e7c55..25a0df1 100644
> >> --- a/drivers/watchdog/Kconfig
> >> +++ b/drivers/watchdog/Kconfig
> >> @@ -152,6 +152,18 @@ config ARM_SP805_WATCHDOG
> >>           ARM Primecell SP805 Watchdog timer. This will reboot your system
> >> when
> >>           the timeout is reached.
> >>
> >> +config ARM_SBSA_WATCHDOG
> >> +       tristate "ARM SBSA Generic Watchdog"
> >> +       depends on ARM || ARM64 || COMPILE_TEST
> >> +       depends on ARM_ARCH_TIMER
> >> +       select WATCHDOG_CORE
> >> +       help
> >> +         ARM SBSA Generic Watchdog timer. This has two Watchdog Signals
> >> +         (WS0/WS1), will trigger a warning interrupt(do panic) at the
> >> first
> >> +         timeout(WS0); will reboot your system when the second
> >> timeout(WS1)
> >> +         is reached.
> >
> >
> > I think it would be better to keep the WS0/WS1 out of the help text.
> > It is an implementation detail, and no user will be able to make sense of
> > it.
> 
> I don't mind to delete it , but those are in SBSA spec, is that an
> implementation detail ?
> 
I think so.

Ask yourself - assuming you are not involved in the development of this driver,
and you read this help text. Is the help text going to help you to know about
WS0 and WS1 ? Why not just something like the following, if you want to be
verbose ?

	ARM SBSA Generic Watchdog. This watchdog has two Watchdog timeouts.
	The first timeout will trigger a panic; the second timeout will trigger
	a system reset.

Anyway, not worth arguing about.

> >> +
> >> +       /*
> >> +        * Try to determine the frequency from the arch_timer interface
> >> +        */
> >> +       clk = arch_timer_get_rate();
> >
> >
> > arch_timer_get_rate() does not seem to be exported. Did you try to build
> > the driver as module ?
> 
> yes, I have built it as a ko module, that is why I made a patch to
> export this interface in the first patch of this patchset
> 
>  but I will confirm it again :-)
> 
Guess I'll give it a try myself. I don't really understand how this
can work unless arch_timer_get_rate() is exported in your tree.

Guenter
--
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/