From: Scott Wood <scottwood@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] GPIO-Watchdog in devicetree
Date: Thu, 25 Sep 2008 13:21:23 -0500 [thread overview]
Message-ID: <48DBD6A3.7070102@freescale.com> (raw)
In-Reply-To: <fa686aa40809251110t1493e74bucd142f10c242f004@mail.gmail.com>
Grant Likely wrote:
> On Thu, Sep 25, 2008 at 11:59 AM, Scott Wood <scottwood@freescale.com> wrote:
>> On Tue, Sep 23, 2008 at 09:02:56AM -0600, Grant Likely wrote:
>>> For example:
>>> / {
>>> model = "pengutronix,super-sexy-board";
>>> #address-cells = <1>;
>>> #size-cells = <1>;
>>> super-sexy-board,watchdog-gpio = <&gpio_simple 19 0>;
>>> ...
>>> }
>> Why as a property of the root node, and not as a node with a very
>> specific compatible property?
>
> Because the root node is the only logical board-level node we have
> right now. However, I'm not deeply committed to this approach. The
> only question I have about putting it in another node is choosing the
> parent node. I don't think it fits to make it a child of the SoC node
> or any other bus node.
A child of the gpio controller node seems most logical, though a child
of the root node would be OK. It was the freefloating property that
struck me as a little odd.
-Scott
next prev parent reply other threads:[~2008-09-25 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 19:43 [RFC] GPIO-Watchdog in devicetree Wolfram Sang
2008-09-23 15:02 ` Grant Likely
2008-09-25 17:59 ` Scott Wood
2008-09-25 18:10 ` Grant Likely
2008-09-25 18:21 ` Scott Wood [this message]
2008-09-26 1:15 ` David Gibson
2008-09-26 1:15 ` David Gibson
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=48DBD6A3.7070102@freescale.com \
--to=scottwood@freescale.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.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 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.