[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <563B869F.2010004@roeck-us.net>
Date: Thu, 5 Nov 2015 08:41:03 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Fu Wei <fu.wei@...aro.org>, Timur Tabi <timur@...eaurora.org>
Cc: Linaro ACPI Mailman List <linaro-acpi@...ts.linaro.org>,
linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org,
lkml <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Arnd Bergmann <arnd@...db.de>,
Jonathan Corbet <corbet@....net>, Jon Masters <jcm@...hat.com>,
Pratyush Anand <panand@...hat.com>,
Will Deacon <will.deacon@....com>,
Wim Van Sebroeck <wim@...ana.be>,
Catalin Marinas <catalin.marinas@....com>,
Wei Fu <tekkamanninja@...il.com>,
Rob Herring <robherring2@...il.com>,
Vipul Gandhi <vgandhi@...eaurora.org>,
Dave Young <dyoung@...hat.com>
Subject: Re: [Linaro-acpi] [PATCH v8 5/5] Watchdog: introduce ARM SBSA
watchdog driver
On 11/05/2015 07:00 AM, Fu Wei wrote:
> Hi Timur,
>
> On 5 November 2015 at 22:40, Timur Tabi <timur@...eaurora.org> wrote:
>> Fu Wei wrote:
>>>
>>> Did you really read the "Note" above???????? OK, let me paste it again
>>> and again:
>>>
>>> SBSA 2.3 Page 23 :
>>> If a larger watch period is required then the compare value can be
>>> programmed directly into the compare value register.
>>
>>
>> Well, okay. Sorry, I should have read what you pasted more closely. But I
>
> Thanks for reading it again.
>
>> think that means during initialization, not during the WS0 timeout.
>
> I really don't see SBSA say "during initialization, not during the WS0 timeout",
> please point it out the page number and the line number in SBSA spec.
> maybe I miss it?
> Thanks for your help in advance.
>
>>
>> Anyway, I still don't like the fact that you're programming WCV in the
>
> "you don't like" doesn't mean "it is wrong" or "we can't do this", so
> I will keep this way unless we have better idea to extend second stage
> timeout.
>
>> interrupt handler, but I'm not going to make a big deal about it any more.
>
> Deal, Thanks a lot.
>
The problem with your driver, as I see it, is that dealing with WS0/WS1
and pretimeout makes the driver so complex that, at least for my part,
I am very wary about it. The driver could long since have been accepted
if it were not for that. Besides that, I really believe that any system designer
using the highest permitted frequency should be willing to live with the
consequences, and not force the implementation of a a complex driver.
Ultimately, you'll have to decide if you want a simple driver accepted, or
a complex driver hanging in the review queue forever.
Thanks,
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/
Powered by blists - more mailing lists