From: "Heiko Stübner" <heiko@sntech.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
James Hogan <james.hogan@imgtec.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 1/5] pinctrl: update the documentation for some pinconfig params
Date: Sun, 16 Jun 2013 12:45:29 +0200 [thread overview]
Message-ID: <201306161245.30465.heiko@sntech.de> (raw)
In-Reply-To: <CACRpkdaV78wXxGPFWVffEfnqrmhq1rsdVYdSKNx5mWaOcYOWrQ@mail.gmail.com>
Am Sonntag, 16. Juni 2013, 12:26:38 schrieb Linus Walleij:
> On Fri, Jun 14, 2013 at 5:42 PM, Heiko Stübner <heiko@sntech.de> wrote:
> > The BIAS_DISABLE and BIAS_HIGH_IMPEDANCE generic pinconfig options were
> > missing information about their argument - which should be ignored.
> >
> > Also the BIAS_PULL_* options may have the pull strength as argument
> > when they are activated, while simpler hardware can use any
> > non-0 value for it.
> >
> > Update the kerneldoc to reflect this.
> >
> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
>
> I'm holding this patch off.
>
> > * @PIN_CONFIG_BIAS_PULL_UP: the pin will be pulled up (usually with
> > high
> >
> > - * impedance to VDD). If the argument is != 0 pull-up is enabled,
> > - * if it is 0, pull-up is disabled.
> > + * impedance to VDD). If the argument is != 0 pull-up is enabled. On
> > + * hardware supporting this, the argument should contain the
> > strength of + * the pull in Ohm. If it is 0, pull-up is disabled.
>
> As noted by Laurent, a pull-up of 0 Ohm is a short-circuit (bascially the
> TOTAL pull-up) and it is pretty counter-intuitive to have that mean
> "disable pull-up". Can we avoid this?
>
> > * @PIN_CONFIG_BIAS_PULL_DOWN: the pin will be pulled down (usually with
> > high
> >
> > - * impedance to GROUND). If the argument is != 0 pull-down is
> > enabled, - * if it is 0, pull-down is disabled.
> > + * impedance to GROUND). If the argument is != 0 pull-down is
> > enabled. On + * hardware supporting this, the argument should
> > contain the strength of + * the pull in Ohm. If it is 0, pull-down
> > is disabled.
>
> Dito.
>
> > * @PIN_CONFIG_BIAS_PULL_PIN_DEFAULT: the pin will be pulled up or down
> > based * on embedded knowledge of the controller, like current mux
> > function.
> >
> > - * If the argument is != 0 pull up/down is enabled, if it is 0,
> > - * the pull is disabled.
> > + * If the argument is != 0 pull up/down is enabled. On hardware
> > supporting + * this, the argument should contain the strength of the
> > pull in Ohm. + * If it is 0, pull is disabled.
>
> Dito.
>
> Can't we rely on PIN_CONFIG_BIAS_DISABLE for all this?
you're the boss on this, I'll do whatever you say :-)
I was going after the existing documentation of "bias-pull-X = <0>" being
there to turn off this specific bias. So when reading the existing doc I was
assuming somebody had needed this in the past.
Actually I'm too more comfortable with only using bias-disable.
So I'll redo this patch to remove the disabling of a pull via this method, if
that's the right way to go.
Same with the rockchip driver.
Heiko
next prev parent reply other threads:[~2013-06-16 10:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 15:41 [PATCH 0/5] pinctrl: fix some issues with new pinconfig dt parsing Heiko Stübner
2013-06-14 15:42 ` [PATCH 1/5] pinctrl: update the documentation for some pinconfig params Heiko Stübner
2013-06-16 10:26 ` Linus Walleij
2013-06-16 10:45 ` Heiko Stübner [this message]
2013-06-16 12:26 ` Linus Walleij
2013-06-14 15:42 ` [PATCH 2/5] pinctrl: clarify some dt pinconfig options Heiko Stübner
2013-06-16 10:28 ` Linus Walleij
2013-06-19 22:10 ` Stephen Warren
2013-06-24 9:51 ` Linus Walleij
2013-06-14 15:43 ` [PATCH 3/5] pinctrl: handle zero found dt pinconfig properties better Heiko Stübner
2013-06-16 10:29 ` Linus Walleij
2013-06-14 15:43 ` [PATCH 4/5] pinctrl: dynamically alloc temp array when parsing dt pinconf options Heiko Stübner
2013-06-16 10:31 ` Linus Walleij
2013-06-14 15:44 ` [PATCH 5/5] pinctrl: rockchip: correctly handle arguments of " Heiko Stübner
2013-06-16 10:35 ` Linus Walleij
2013-06-16 11:02 ` Heiko Stübner
2013-06-16 12:35 ` Linus Walleij
2013-06-16 15:41 ` [PATCH v2] " Heiko Stübner
2013-06-17 15:48 ` Linus Walleij
2013-06-14 15:53 ` [PATCH 0/5] pinctrl: fix some issues with new pinconfig dt parsing James Hogan
2013-06-17 3:03 ` Laurent Pinchart
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=201306161245.30465.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=james.hogan@imgtec.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
/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