From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: establish pull-up/pull-down terminology
Date: Mon, 24 Jun 2013 12:04:41 -0600 [thread overview]
Message-ID: <51C88A39.3040201@wwwdotorg.org> (raw)
In-Reply-To: <3185376.o7RqphCDfQ@avalon>
On 06/21/2013 05:30 PM, Laurent Pinchart wrote:
> Hi Stephen,
>
> On Friday 21 June 2013 13:06:47 Stephen Warren wrote:
...
>> IIRC the idea of the PULL_PIN_DEFAULT was to avoid having to specify
>> UP/DOWN for each pin/group, but could just say "default", which would
>> then reduce the number of pinctrl mapping table entries or pinctrl DT
>> property entries.
>
> I may be mistaken, but I've understood the PULL_PIN_DEFAULT option as a way to
> select the default bias configuration when the default value is hardware-
> controlled, not as a pure software option.
That's my understanding too.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "James Hogan" <james.hogan@imgtec.com>,
"Linus Walleij" <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Stephen Warren" <swarren@nvidia.com>, � <heiko@sntech.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Anmar Oueja" <anmar.oueja@linaro.org>
Subject: Re: [PATCH] pinctrl: establish pull-up/pull-down terminology
Date: Mon, 24 Jun 2013 12:04:41 -0600 [thread overview]
Message-ID: <51C88A39.3040201@wwwdotorg.org> (raw)
In-Reply-To: <3185376.o7RqphCDfQ@avalon>
On 06/21/2013 05:30 PM, Laurent Pinchart wrote:
> Hi Stephen,
>
> On Friday 21 June 2013 13:06:47 Stephen Warren wrote:
...
>> IIRC the idea of the PULL_PIN_DEFAULT was to avoid having to specify
>> UP/DOWN for each pin/group, but could just say "default", which would
>> then reduce the number of pinctrl mapping table entries or pinctrl DT
>> property entries.
>
> I may be mistaken, but I've understood the PULL_PIN_DEFAULT option as a way to
> select the default bias configuration when the default value is hardware-
> controlled, not as a pure software option.
That's my understanding too.
next prev parent reply other threads:[~2013-06-24 18:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 10:45 [PATCH] pinctrl: establish pull-up/pull-down terminology Linus Walleij
2013-06-16 10:45 ` Linus Walleij
2013-06-16 14:39 ` Heiko Stübner
2013-06-16 14:39 ` Heiko Stübner
2013-06-17 2:53 ` Laurent Pinchart
2013-06-17 2:53 ` Laurent Pinchart
2013-06-17 4:38 ` Tony Prisk
2013-06-17 4:38 ` Tony Prisk
2013-06-17 5:57 ` Lothar Waßmann
2013-06-17 15:51 ` Linus Walleij
2013-06-17 15:51 ` Linus Walleij
2013-06-19 22:03 ` Stephen Warren
2013-06-19 22:03 ` Stephen Warren
2013-06-20 12:38 ` James Hogan
2013-06-20 12:38 ` James Hogan
2013-06-21 19:06 ` Stephen Warren
2013-06-21 19:06 ` Stephen Warren
2013-06-21 23:30 ` Laurent Pinchart
2013-06-21 23:30 ` Laurent Pinchart
2013-06-21 23:39 ` Heiko Stübner
2013-06-21 23:39 ` Heiko Stübner
2013-06-24 12:24 ` Linus Walleij
2013-06-24 12:24 ` Linus Walleij
2013-06-24 12:39 ` Heiko Stübner
2013-06-24 12:39 ` Heiko Stübner
2013-06-24 18:04 ` Stephen Warren [this message]
2013-06-24 18:04 ` 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=51C88A39.3040201@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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.