* Proposed bindings for a GPIO watchdog drivers
@ 2013-03-26 16:04 Alexander Morozov
[not found] ` <CALRpspn7UN4EVwQz8gt1S3Hg=bNR6MMuz=844XSpt=syQO6r-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 2+ messages in thread
From: Alexander Morozov @ 2013-03-26 16:04 UTC (permalink / raw)
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ
Hello,
I've written a watchdog driver for simple chips that are connected via
GPIO. Driver can be used with chips from different manufacturers.
Should "compatible" property be set to "gpio-wdt" or
"generic,gpio-wdt"? Are there any other problems with following
bindings?
---------
Required properties:
- compatible: must be "generic,gpio-wdt".
- gpios: gpio pin to use
- ping-sec: how often to ping the watchdog before userspace watchdog
daemon is started,
- timeout-sec: watchdog timeout that is reported to userspace.
Example:
max6369 {
compatible = "generic,gpio-wdt";
gpios = <&pioB 13 0>;
ping-sec = <5>;
timeout-sec = <60>;
};
Regards,
Alexander Morozov.
^ permalink raw reply [flat|nested] 2+ messages in thread[parent not found: <CALRpspn7UN4EVwQz8gt1S3Hg=bNR6MMuz=844XSpt=syQO6r-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Proposed bindings for a GPIO watchdog drivers [not found] ` <CALRpspn7UN4EVwQz8gt1S3Hg=bNR6MMuz=844XSpt=syQO6r-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2013-04-16 6:51 ` Grant Likely 0 siblings, 0 replies; 2+ messages in thread From: Grant Likely @ 2013-04-16 6:51 UTC (permalink / raw) To: Alexander Morozov, devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ On Tue, 26 Mar 2013 20:04:30 +0400, Alexander Morozov <etesial-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > Hello, > > I've written a watchdog driver for simple chips that are connected via > GPIO. Driver can be used with chips from different manufacturers. > Should "compatible" property be set to "gpio-wdt" or > "generic,gpio-wdt"? Are there any other problems with following > bindings? The trick with things like 'simple' gpio connections are that they may not be very simple at all, and there are many different ways that the interface can be designed to work. The most important thing here is that you document exactly the protocol used by this hardware. So, not just that is uses a GPIO pin, but /how/ the gpio pin is used. Is it a pulse? Is it edge or level sensitive? etc. g. > > --------- > > Required properties: > - compatible: must be "generic,gpio-wdt". > - gpios: gpio pin to use > - ping-sec: how often to ping the watchdog before userspace watchdog > daemon is started, > - timeout-sec: watchdog timeout that is reported to userspace. > > Example: > > max6369 { > compatible = "generic,gpio-wdt"; > gpios = <&pioB 13 0>; > ping-sec = <5>; > timeout-sec = <60>; > }; > > Regards, > Alexander Morozov. > _______________________________________________ > devicetree-discuss mailing list > devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org > https://lists.ozlabs.org/listinfo/devicetree-discuss -- Grant Likely, B.Sc, P.Eng. Secret Lab Technologies, Ltd. ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-04-16 6:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-03-26 16:04 Proposed bindings for a GPIO watchdog drivers Alexander Morozov
[not found] ` <CALRpspn7UN4EVwQz8gt1S3Hg=bNR6MMuz=844XSpt=syQO6r-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-16 6:51 ` Grant Likely
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.