devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Dunn <mikedunn@newsguy.com>
To: Haojian Zhuang <haojian.zhuang@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Manjunathappa, Prakash" <prakash.pm@ti.com>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: pxa27x and pinctrl-single
Date: Sun, 09 Jun 2013 11:05:14 -0700	[thread overview]
Message-ID: <51B4C3DA.2000403@newsguy.com> (raw)
In-Reply-To: <CAD6h2NSewh=uodiRGNOVHTiJqMrYg25hMW56rUSPPviTTb_9Ng@mail.gmail.com>

On 06/07/2013 06:20 PM, Haojian Zhuang wrote:
> On 8 June 2013 01:41, Mike Dunn <mikedunn@newsguy.com> wrote:
>> On 06/07/2013 08:16 AM, Haojian Zhuang wrote:
>>>
>>
>> [...]
>>
>>
>>> Since you need to configure both GPDRx and GAFRx. If we are talking
>>> pinctrl-single
>>> as reference, we can make it work by this way.
>>>
>>> We need to define two pinmux controllers. One is for GPDRx, and the
>>> other is for GAFRx.
>>> Both of them need to support pinctrl-single,bits property. For any
>>> alternate pins in DTS,
>>> we could include these two pins from two pinmux controllers. What's
>>> your opinion?
>>
>>
>> Are you are suggesting that the dts file can be defined such that the desired
>> values are written to GAFR and GPDR, without having to make any changes to the
>> pinctrl-single driver code?  If I understand correctly, we would be defining two
>> "pins" in the device tree for each actual pin.  That seems very ugly.
>>
>> I was thinking that pinctrl-single could be modified to support multiple
>> reg/value/mask pairs for each pin listed in the pinctrl-single,bits property.
>> There is a comment at the top of pcs_parse_one_pinctrl_entry() that seems to
>> suggest the possibility...
> 
> We only support continuous register offset in pinctrl-single driver.
> GPDRx is in range of 0x40e0000c~0x40e0010c, GAFRx is in range of
> 0x40e00054~0x40e00070.


Ah, I see...


> 
> So I suggest you to split them as two pinmux controller. If you define them into
> one pinmux controler, it's also OK. But they are still two pins in the on pinmux
> controller. And you should avoid to access those spare pins in the middle.


I'm still not smart enough to parse this.  Do you mean create a separate driver,
or two instances of pinctrl-single?


> 
> I don't suggest you to support multiple reg/value/mask pairs for each pin in
> pinctrl-single driver. It's too complex. It already exceeds the design scope
> of the pinctrl-single driver.


Yes, this I understand.  BTW, I see there are more patches for pinctrl-single
coming in.

Thanks for the advice Haojian.

Mike

      reply	other threads:[~2013-06-09 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 17:23 pxa27x and pinctrl-single Mike Dunn
     [not found] ` <51AF7404.3090003-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-06  0:43   ` Haojian Zhuang
2013-06-06 17:33     ` Mike Dunn
     [not found]       ` <51B0C7E8.5090308-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-06 23:58         ` Haojian Zhuang
2013-06-07  0:48           ` Mike Dunn
     [not found]             ` <51B12DE9.9040908-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-07  1:21               ` Haojian Zhuang
2013-06-07 14:50                 ` Mike Dunn
     [not found]                   ` <51B1F330.9080007-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-07 15:16                     ` Haojian Zhuang
2013-06-07 17:41                       ` Mike Dunn
     [not found]                         ` <51B21B3B.8050604-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-08  1:20                           ` Haojian Zhuang
2013-06-09 18:05                             ` Mike Dunn [this message]

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=51B4C3DA.2000403@newsguy.com \
    --to=mikedunn@newsguy.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=haojian.zhuang@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=prakash.pm@ti.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;
as well as URLs for NNTP newsgroup(s).