lkml.org 
[lkml]   [2015]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2 6/7] Watchdog: introduce ARM SBSA watchdog driver
On 05/24/2015 08:50 AM, Fu Wei wrote:
[ ...]

> Actually, I have added my thought at the head of sbsa_gwdt.c as a comment :
>
> *
> * Note: This SBSA Generic watchdog driver is compatible with
> * the pretimeout concept of Linux kernel.
> * The timeout and pretimeout are set by the different REGs.
> * The first watch period is set by writing WCV directly,
> * that can support more than 10s timeout at the maximum
> * system counter frequency.
> * The second watch period is set by WOR(32bit) which will be loaded
> * automatically by hardware, when WS0 is triggered.
> * This gives a maximum watch period of around 10s at the maximum
> * system counter frequency.
> * The System Counter shall run at maximum of 400MHz.
> * More details: DEN0029B - Server Base System Architecture (SBSA)
> *
> * Kernel/API: P---------| pretimeout
> * |-------------------------------T timeout
> * SBSA GWDT: P--WOR---WS1 pretimeout
> * |-------WCV----------WS0~~~~~~~~T timeout
> */
>

Yes, but do we actually _know_ that it works that way, ie that WCV
drives WS0 and that WOR drives WS1 ? Unless I am missing something,
the specification doesn't say that, and it would have been a really
easy statement to make if that was the intent.

My concern here is that the above behavior is not spelled out in
the document, meaning it is up to interpretation by the hardware
engineer implementing it, to the point where it appears that not
even two software engineers can agree how it is supposed to work.
Which is a really bad starting point :-(.

Thanks,
Guenter



\
 
 \ /
  Last update: 2015-05-24 18:41    [W:0.111 / U:0.936 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site