From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Heiko Stübner" <heiko@sntech.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Grant Likely <grant.likely@secretlab.ca>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
James Hogan <james.hogan@imgtec.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [RFC] pinctrl: generic: Add DT bindings
Date: Sun, 16 Jun 2013 01:35:34 +0200 [thread overview]
Message-ID: <1795038.rqcr6GWLdP@avalon> (raw)
In-Reply-To: <201306152216.14252.heiko@sntech.de>
Hi Heiko,
On Saturday 15 June 2013 22:16:13 Heiko Stübner wrote:
> Am Samstag, 15. Juni 2013, 21:56:05 schrieb Linus Walleij:
> > On Fri, Jun 14, 2013 at 12:39 AM, Laurent Pinchart wrote:
> > > mmcif_pins: mmcif {
> > > mux {
> > > renesas,groups = "mmc0_data8_0", "mmc0_ctrl_0";
> > > renesas,function = "mmc0";
> > > };
> > > cfg {
> > > renesas,groups = "mmc0_data8_0";
> > > renesas,pins = "PORT279";
> > > bias-pull-up = <1>;
> >
> > If I understood your code correctly that last statement can *optionally*
> >
> > be written like just:
> > bias-pull-up;
> >
> > Without the parameter?
> >
> > I think that Heiko's implementation does this anyway.
>
> Yep, with the fixes-series from yesterday the bias-pull-* now have a better
> default value of <1>.
>
> so you can do
> bias-pull-up;
> which is then identical to the
> bias-pull-up = <1>;
> above (both are valid of course).
My patch used bias-pull-up = <1>; as the current version of Heiko's DT parser
didn't support bias-pull-up; correctly at that time. It's fixed now, and my
prefered is then bias-pull-up;.
> Disable would the be either
> bias-disable;
> or
> bias-pull-up = <0>;
>
> A driver should probably handle both, as both are valid pinconf options or
> this.
I feel a bit uneasy about that. Do we really need to support two different
ways to achieve the same result ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-06-15 23:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 22:03 [RFC] pinctrl: generic: Add DT bindings Laurent Pinchart
2013-06-12 12:48 ` Grant Likely
2013-06-13 22:39 ` Laurent Pinchart
2013-06-15 19:56 ` Linus Walleij
2013-06-15 20:16 ` Heiko Stübner
2013-06-15 23:35 ` Laurent Pinchart [this message]
2013-06-15 23:51 ` Linus Walleij
2013-06-15 23:52 ` Laurent Pinchart
2013-06-16 0:04 ` Linus Walleij
[not found] ` <201306152216.14252.heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2013-06-19 21:52 ` Stephen Warren
2013-06-12 14:36 ` James Hogan
2013-06-13 22:46 ` Laurent Pinchart
2013-06-19 21:58 ` Stephen Warren
2013-06-24 9:43 ` Linus Walleij
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=1795038.rqcr6GWLdP@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=heiko@sntech.de \
--cc=james.hogan@imgtec.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.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).