[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZePYMHFMOc0WEy73vqix9uRFyedS66sKcyP_D_Kq+nQg@mail.gmail.com>
Date: Sun, 16 Jun 2013 02:04:45 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: Heiko Stübner <heiko@...ech.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Grant Likely <grant.likely@...retlab.ca>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
James Hogan <james.hogan@...tec.com>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>
Subject: Re: [RFC] pinctrl: generic: Add DT bindings
On Sun, Jun 16, 2013 at 1:52 AM, Laurent Pinchart
<laurent.pinchart@...asonboard.com> wrote:
> Hi Linus,
> On Sunday 16 June 2013 01:51:32 Linus Walleij wrote:
>> 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;.
Oh yeah OK you got a point there for sure.
Setting bias-pull-up = <0>; would be equal to short-circuit
so it does not make any kind of sense.
Let's keep an eye on this.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists