devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Ruehl <chris.ruehl-CR359r9tUDPXPF5Rlphj1Q@public.gmane.org>
To: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Markus Pargmann <mpa-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linus Walleij
	<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org
Subject: Re: IMX27: How to do 22k pull-up with the pinctrl ?
Date: Wed, 13 Nov 2013 12:43:31 +0800	[thread overview]
Message-ID: <52830373.5060806@gtsys.com.hk> (raw)
In-Reply-To: <20131111142639.GC11083-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>



On Monday, November 11, 2013 10:26 PM, Shawn Guo wrote:
> Copy Markus who is working on imx27 pinctrl driver.
>
> On Mon, Nov 11, 2013 at 12:03:57PM +0000, Mark Rutland wrote:
>> On Mon, Nov 11, 2013 at 10:45:30AM +0000, Chris Ruehl wrote:
>>> Hi,
>>
>> Hi,
>>
>> While this does involve device tree, it's not strictly a device tree
>> problem, and the people best placed to answer your question don't seem
>> to be on Cc. You'd get better responses if you used get_maintainer.pl,
>> or looked at the commit history of the driver or binding to find people
>> likely to be able to help.
>>
>> I've added Dong Aisheng, Shawn Guo, and Linus Walleij to Cc, as they had
>> signed-off-bys on the binding document.
>
> Thanks, Mark.
>
> <snip>
>
>>> 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
>
> Is the code from mainline kernel or private tree?  I'm asking because I
> do not see non-DT imx27 iomux-v1 driver has interface for setting up
> DSCR or PSCR in SYSCTRL block.  That's probably why Markus did not
> support that in the imx27 pinctrl driver, I guess.
>
> Shawn

Hi Shawn,

I work on a private tree using the 3.12-next source as my base. Mainboard is a 
new design using for RFID integrated readers. I include almost all available
features from the imx27.
OTG, USB2, SPI, I2C, MMC, DM9000 ..

To set the pull-strength would be a great thing.

Chris

>
>>> 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.
>>>
>>>
>>> pinctrl_sdhc2_1: sdhc2-1 {
>>>                           fsl,pins =<
>>>                                   MX27_PAD_SD2_D0__SD2_D0  0x1
>>>                                   MX27_PAD_SD2_D1__SD2_D1  0x1
>>>                                   MX27_PAD_SD2_D2__SD2_D2  0x1
>>>                                   MX27_PAD_SD2_D3__SD2_D3  0x1
>>>                                   MX27_PAD_SD2_CLK__SD2_CLK  0x1
>>>                                   MX27_PAD_SD2_CMD__SD2_CMD  0x1
>>>                           >;
>>>                   };
>>>
>>> its setup in board specific c-file
>>>
>>> /* 22k pull-up for sd2 pins  */
>>>           reg = __raw_readw(MX27_IO_ADDRESS(MX27_SYSCTRL_BASE_ADDR + MX27_SYS_PSCR));
>>>           reg&= ~0xfff0;
>>>           reg |= 0xfff0;
>>>           __raw_writew(reg, MX27_IO_ADDRESS(MX27_SYSCTRL_BASE_ADDR + MX27_SYS_PSCR));
>>>
>>>
>>> Any successions?
>>>
>>> Regards
>>> 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
>>>
>

--
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

  parent reply	other threads:[~2013-11-13  4:43 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 [this message]
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
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=52830373.5060806@gtsys.com.hk \
    --to=chris.ruehl-cr359r9tudpxpf5rlphj1q@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=mpa-bIcnvbaLZ9MEGnE8C9+IrQ@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).