From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Alexander Morozov
<etesial-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: Proposed bindings for a GPIO watchdog drivers
Date: Tue, 16 Apr 2013 07:51:26 +0100 [thread overview]
Message-ID: <20130416065126.5FEBB3E14C0@localhost> (raw)
In-Reply-To: <CALRpspn7UN4EVwQz8gt1S3Hg=bNR6MMuz=844XSpt=syQO6r-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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.
prev parent reply other threads:[~2013-04-16 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130416065126.5FEBB3E14C0@localhost \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=etesial-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).