Hi Uwe,
On 07/29/2015 12:35 AM, Uwe Kleine-König wrote:
Hello Guenter,
[ ... ]
always-running is meant to indicate that the watchdog can not be stopped
(meaning a timer has to be used to send keepalives while the watchdog
device is closed). The documentation specifically states that.
"If the watchdog timer cannot be disabled ..."
How would you express that condition without always-running or a similar
attribute ? I am also not sure how that relates to hw_algo; I thought
those properties are orthogonal.
For hw_algo = "level" the inactive level of the gpio disables the
watchdog (and resets the counter). So always-running doesn't make sense
for this type.
That is not what is currently implemented. "level" just means that
the watchdog is pinged using a -high-low-high- or -low-high-low-
sequence, while toggle means that the level is changed with each
ping (-low-(wait)-high-(wait)-low-(wait)-high-...).
Of course, 'always-running' _may_ describe driver behavior, but that doesn't
Well in the current state of the binding document we have:
add this flag to have the driver keep toggling the signal
without a client.
Sure it is meant to describe a hardware specific property, but it talks
about the driver.
Then the fix is to update the binding document.
I'd go for these properties then:
toggle-gpio: the gpio used to stroke the watchdog
'toggle' means something different in the current implementation.
enable-gpio: optional, the gpio to enable and disable the watchdog
disable-on-tri-state: optional, signals that the watchdog can
be stopped by setting the trigger-gpio to tri-state.
compatible, hw_algo and hw_margin_ms: as before.
I would agree that a separate 'enable' property would make sense (if you
have a watchdog needing it). Similar to disable-on-tri-state, if there
is some hardware which is implemented that way (mixing up hw_algo==toggle
with that state doesn't seem correct). Deprecating hw_algo and replacing it
with something more sensible might make sense as well ('algorithm' ?).
We have to be careful not to mix up hw_algo and enable, though.
I think there is no need for a property that signals that the watchdog
is unstoppable. For level-gpio-watchdogs you can do it by setting the
trigger gpio to inactive, and you cannot stop level-gpio-watchdogs
unless enable-gpio or disable-on-tri-state is specified.
If we ever feel the need to describe a gpio watchdog with a input that
starts the device but cannot stop it, I'd suggest to use "start-gpio"
for that one.
have to be the case. There are lots of watchdogs out there which can not be
stopped. Some of them run all the time, others can not be stopped once
started.
Yeah, I'm aware of that. For this driver however I wouldn't expect that
you have a dedicated enable-gpio if you cannot disable the device with it.
Why ? There are lots of chips which implement exactly that. There is an
enable bit in some register which can be used to enable the watchdog,
but once enabled it can not be stopped. I don't see why a gpio driven
watchdog would have to be any different.
For hw_algo = "level" there is probably no device with an enable input
Why should that be the case ?
and for hw_algo = "toggle" any sane hardware engineer would simply
enable the watchdog once the first toggle is detected on WDI. (OK,
assuming hardware engineers being sane turned out to be a weak argument
often in the past.)
I still don't see the relationship between enable and the toggle/level
algorithm. Really, those two properties are orthogonal.
I'm aware that using ...-gpios is more common than ...-gpio. I don't
feel strong here, but as only a single gpio makes sense here, having
-gpios seems wrong.
Documentation/devicetree/bindings/gpio/gpio.txt states that gpio pin
references should be named <name>-gpios. It even lists examples such as
enable-gpios = <&gpio2 2>;
I thought this was a hard rule, and I seem to recall requests to change
something-gpio to something-spios, but I may be wrong.
Yeah, I'm aware of that. I talked about that in #armlinux yesterday, and
Mark Brown (added to Cc:) said:
Well, I'd prefer to change the standard TBH and allow singular.
This keeps coming up and causing confusion for no good reason.
Sounds sensible in my ears.
Makes sense to me, but I'd like to see that done first.
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
