From: "Heiko Stübner" <heiko@sntech.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Stephen Warren <swarren@wwwdotorg.org>,
James Hogan <james.hogan@imgtec.com>,
Linus Walleij <linus.walleij@stericsson.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Stephen Warren <swarren@nvidia.com>,
Anmar Oueja <anmar.oueja@linaro.org>
Subject: Re: [PATCH] pinctrl: establish pull-up/pull-down terminology
Date: Mon, 24 Jun 2013 14:39:05 +0200 [thread overview]
Message-ID: <201306241439.05875.heiko@sntech.de> (raw)
In-Reply-To: <CACRpkdYMe+q2GUXooSeVVua3-AHDJFfWQu21bn45b_omsA7FAQ@mail.gmail.com>
Am Montag, 24. Juni 2013, 14:24:12 schrieb Linus Walleij:
> On Sat, Jun 22, 2013 at 1:39 AM, Heiko Stübner <heiko@sntech.de> wrote:
> > Am Samstag, 22. Juni 2013, 01:30:18 schrieb Laurent Pinchart:
> >> [Stephen]
> >>
> >> > 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.
> >
> > Yep that was the original intent ... to handle hardware that hides the
> > complete logic from the software and you only get to turn it on or off,
> > while the direction and other params are determined internally for
> > example by the pin function.
>
> Heiko, can you send a documentation patch to clarify this so we
> don't get any misunderstandings?
>
> Maybe it'd be useful for software purposes as well, but let's save
> that for when it gets used like that.
will try to get this (and the changes from the other mail) done today
Heiko
next prev parent reply other threads:[~2013-06-24 12:39 UTC|newest]
Thread overview: 13+ 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 14:39 ` Heiko Stübner
2013-06-17 2:53 ` Laurent Pinchart
2013-06-17 4:38 ` Tony Prisk
[not found] ` <20926.42315.907448.451620@ipc1.ka-ro>
2013-06-17 15:51 ` Linus Walleij
2013-06-19 22:03 ` Stephen Warren
2013-06-20 12:38 ` James Hogan
2013-06-21 19:06 ` Stephen Warren
2013-06-21 23:30 ` Laurent Pinchart
2013-06-21 23:39 ` Heiko Stübner
2013-06-24 12:24 ` Linus Walleij
2013-06-24 12:39 ` Heiko Stübner [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=201306241439.05875.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=anmar.oueja@linaro.org \
--cc=james.hogan@imgtec.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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).