From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.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: Sat, 15 Jun 2013 23:52:59 +0000 [thread overview]
Message-ID: <1422045.RvRkWGR9K7@avalon> (raw)
In-Reply-To: <CACRpkdYi=ekV8okmz68HZ8Ydv9hTrHnHvQh0HYMs5SfURd9mdA@mail.gmail.com>
Hi Linus,
On Sunday 16 June 2013 01:51:32 Linus Walleij wrote:
> On Sun, Jun 16, 2013 at 1:35 AM, Laurent Pinchart wrote:
> > On Saturday 15 June 2013 22:16:13 Heiko Stübner wrote:
> >> Am Samstag, 15. Juni 2013, 21:56:05 schrieb Linus Walleij:
> >>
> >> 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 ?
>
> In this specific case I think yes, but not on all options.
>
> As dicussed earlier this was designed for systems where
> you could set the pull-up resistance, like
>
> bias-pull-up = <600000>;
>
> would give 600kOhm pull up.
>
> In most existing systems that is silly, as they can't specify it, so they
> should be able to do just:
>
> bias-pull-up;
>
> as that is all they can do. If we have to cut one way, we should cut the
> former until such a system appears.
I'm fine with bias-pull-up = <1>; vs bias-pull-up;. What bothers me a bit is
bias-pull-up = <0>; vs bias-disable;.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.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:52:59 +0200 [thread overview]
Message-ID: <1422045.RvRkWGR9K7@avalon> (raw)
In-Reply-To: <CACRpkdYi=ekV8okmz68HZ8Ydv9hTrHnHvQh0HYMs5SfURd9mdA@mail.gmail.com>
Hi Linus,
On Sunday 16 June 2013 01:51:32 Linus Walleij wrote:
> On Sun, Jun 16, 2013 at 1:35 AM, Laurent Pinchart wrote:
> > On Saturday 15 June 2013 22:16:13 Heiko Stübner wrote:
> >> Am Samstag, 15. Juni 2013, 21:56:05 schrieb Linus Walleij:
> >>
> >> 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 ?
>
> In this specific case I think yes, but not on all options.
>
> As dicussed earlier this was designed for systems where
> you could set the pull-up resistance, like
>
> bias-pull-up = <600000>;
>
> would give 600kOhm pull up.
>
> In most existing systems that is silly, as they can't specify it, so they
> should be able to do just:
>
> bias-pull-up;
>
> as that is all they can do. If we have to cut one way, we should cut the
> former until such a system appears.
I'm fine with bias-pull-up = <1>; vs bias-pull-up;. What bothers me a bit is
bias-pull-up = <0>; vs bias-disable;.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-06-15 23:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 22:03 [RFC] pinctrl: generic: Add DT bindings Laurent Pinchart
2013-06-11 22:03 ` Laurent Pinchart
2013-06-12 12:48 ` Grant Likely
2013-06-12 12:48 ` Grant Likely
2013-06-13 22:39 ` Laurent Pinchart
2013-06-13 22:39 ` Laurent Pinchart
2013-06-15 19:56 ` Linus Walleij
2013-06-15 19:56 ` Linus Walleij
2013-06-15 20:16 ` Heiko Stübner
2013-06-15 20:16 ` Heiko Stübner
2013-06-15 23:35 ` Laurent Pinchart
2013-06-15 23:35 ` Laurent Pinchart
2013-06-15 23:51 ` Linus Walleij
2013-06-15 23:51 ` Linus Walleij
2013-06-15 23:52 ` Laurent Pinchart [this message]
2013-06-15 23:52 ` Laurent Pinchart
2013-06-16 0:04 ` Linus Walleij
2013-06-16 0:04 ` Linus Walleij
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-19 21:52 ` Stephen Warren
2013-06-19 21:52 ` Stephen Warren
2013-06-12 14:36 ` James Hogan
2013-06-12 14:36 ` James Hogan
2013-06-12 14:36 ` James Hogan
2013-06-13 22:46 ` Laurent Pinchart
2013-06-13 22:46 ` Laurent Pinchart
2013-06-19 21:58 ` Stephen Warren
2013-06-19 21:58 ` Stephen Warren
2013-06-24 9:43 ` Linus Walleij
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=1422045.RvRkWGR9K7@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 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.