From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Warren <swarren@wwwdotorg.org>,
Rob Herring <rob.herring@calxeda.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@stericsson.com>,
B29396@freescale.com, s.hauer@pengutronix.de, dongas86@gmail.com,
shawn.guo@linaro.org, thomas.abraham@linaro.org,
tony@atomide.com, Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [PATCH] dt: pinctrl: Document device tree binding
Date: Mon, 12 Mar 2012 22:12:48 -0600 [thread overview]
Message-ID: <20120313041248.C470C3E0536@localhost> (raw)
In-Reply-To: <1331316873-20052-1-git-send-email-swarren@wwwdotorg.org>
On Fri, 9 Mar 2012 11:14:33 -0700, Stephen Warren <swarren@wwwdotorg.org> wrote:
> The core pin controller bindings define:
> * The fact that pin controllers expose pin configurations as nodes in
> device tree.
> * That the bindings for those pin configuration nodes is defined by the
> individual pin controller drivers.
> * A standardized set of properties for client devices to define numbered
> or named pin configuration states, each referring to some number of the
> afore-mentioned pin configuration nodes.
> * That the bindings for the client devices determines the set of numbered
> or named states that must exist.
>
> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Not reviewed this version deeply, but this looks good to me. Feel free
to merge it if both you and Linus are happy with it.
g.
next prev parent reply other threads:[~2012-03-13 4:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 18:14 [PATCH] dt: pinctrl: Document device tree binding Stephen Warren
2012-03-12 3:21 ` Randy Dunlap
2012-03-12 13:06 ` Shawn Guo
2012-03-12 14:34 ` Dong Aisheng
2012-03-12 17:16 ` Stephen Warren
2012-03-13 3:20 ` Dong Aisheng
2012-03-13 19:27 ` Stephen Warren
2012-03-15 3:32 ` Dong Aisheng
2012-03-15 17:18 ` Stephen Warren
2012-03-13 4:12 ` Grant Likely [this message]
2012-03-13 9:14 ` Linus Walleij
2012-03-13 19:34 ` Stephen Warren
2012-03-14 21:26 ` Tony Lindgren
2012-03-15 16:51 ` Linus Walleij
2012-03-15 17:12 ` Stephen Warren
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=20120313041248.C470C3E0536@localhost \
--to=grant.likely@secretlab.ca \
--cc=B29396@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dongas86@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=thomas.abraham@linaro.org \
--cc=tony@atomide.com \
/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