[RFC PATCH] watchdog: base rate-limiting on get_ticks() rather than get_timer()

[Stefan Roese]

On 05.06.20 14:11, Rasmus Villemoes wrote:
> On 05/06/2020 13.48, Stefan Roese wrote:
>> On 05.06.20 13:16, Rasmus Villemoes wrote:
>>> This is what I had in mind. I also considered making it a config knob
>>> (possibly just auto-selected based on $ARCH) whether to use
>>> get_timer() or get_ticks(), but that becomes quite ugly.
>>
>> I hesitate a bit, moving with this generic code from get_timer()
>> to get_ticks() for all boards. Did you test this patch on other
>> platforms, like some ARM boards?
>>
>> Please note that I don't reject it - just asking.
> 
> Yeah, I'm not really too happy about it myself, exactly because it
> affects all arches/platforms. And no, I don't have other hardware handy
> unfortunately. So it's very much an RFC where I hope someone with
> knowledge of the various arches can say whether one can expect
> get_ticks() to be at least as widely available as get_timer().

I'll try to test it on a non-powerpc platform soon'ish.

Thanks,
Stefan