From: Chris Ruehl <chris.ruehl-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
To: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Dong Aisheng
<dong.aisheng-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: IMX27: How to do 22k pull-up with the pinctrl ?
Date: Wed, 13 Nov 2013 13:50:24 +0800 [thread overview]
Message-ID: <52831320.8000903@gtsys.com.hk> (raw)
In-Reply-To: <CACRpkdatZfGDn-K-PRxCz53AKF+Q4CAwAbA+ufSKnXapZQkPyw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Monday, November 11, 2013 10:29 PM, Linus Walleij wrote:
> On Mon, Nov 11, 2013 at 1:03 PM, Mark Rutland<mark.rutland-5wv7dgnIgG8@public.gmane.org> wrote:
>> On Mon, Nov 11, 2013 at 10:45:30AM +0000, Chris Ruehl wrote:
>
>>> while I port the static code to the DT I step into the problem to
>>> set the PSCR for the sdhc2 ports to 22k pull-up
>>> I look for something like described in
>>> pinctrl/fsl,imx-pinctrl.txt
>>>
>>> the fsl,imx27-pinctrl only say 0/1 dis/enable pull up but not the strength.
>
> So in the generic pin configuration, which we nowadays recommend new
> platforms to use, there is this (include/linux/pinctrl/pinconf-generic):
>
> * @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 total, i.e. the pin is connected to VDD.
> * @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 total, i.e. the pin is connected to GROUND.
>
> The idea was to extend that with an argument for the number of
> Ohms the day it was needed and supported by some platform.
>
> We would then use the bindings from
> Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> by adding something like this:
>
> (...)
> bias-pull-up-ohms =<22000>;
> (...)
>
> So in the generic world it can be accomodated in a quite
> straight-forward way.
>
> When the i.MX pin control was added in v3.5 the generic
> pin config was available but it was opted to use another
> pattern. One way to solve this is to migrate i.MX to use the
> generic pin config, which is going to be hard work. But as
> a subsystem maintainer that is still what I would recommend.
>
> Yours,
> Linus Walleij
Hi Linus,
Thank you for that very interesting comment!
I agree with your idea to move the IMX code to that more generic solution, there
are already different ways to setup the DT for imx27 vs. imx3x or imx6 etc. and
its not going to be better, my guess!
Chris
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-13 5:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 10:45 IMX27: How to do 22k pull-up with the pinctrl ? Chris Ruehl
[not found] ` <5280B54A.1050503-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
2013-11-11 12:03 ` Mark Rutland
[not found] ` <20131111120357.GE21201-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-11-11 14:26 ` Shawn Guo
[not found] ` <20131111142639.GC11083-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2013-11-11 16:21 ` Markus Pargmann
[not found] ` <20131111162138.GB30263-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-11-13 5:57 ` Chris Ruehl
2013-11-13 4:43 ` Chris Ruehl
2013-11-11 14:29 ` Linus Walleij
[not found] ` <CACRpkdatZfGDn-K-PRxCz53AKF+Q4CAwAbA+ufSKnXapZQkPyw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-13 5:50 ` Chris Ruehl [this message]
2013-11-13 4:38 ` Chris Ruehl
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=52831320.8000903@gtsys.com.hk \
--to=chris.ruehl-cr359r9tudpxpf5rlphj1q@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dong.aisheng-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).