All of lore.kernel.org
 help / color / mirror / Atom feed
From: mikedunn@newsguy.com (Mike Dunn)
To: linux-arm-kernel@lists.infradead.org
Subject: pxa27x and pinctrl-single
Date: Fri, 07 Jun 2013 10:41:15 -0700	[thread overview]
Message-ID: <51B21B3B.8050604@newsguy.com> (raw)
In-Reply-To: <CAD6h2NStRcXm_X=0ib=RtKqVhmsfGo4z=_jzL1hUo_MLcfyBZw@mail.gmail.com>

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

 * Note that this binding currently supports only sets of one register + value.

I am still learning pinctrl and devicetree and studying the driver, so I am not
adament about anything at this point.  Guidance appreciated!

Thanks,
Mike

WARNING: multiple messages have this Message-ID (diff)
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: Fri, 07 Jun 2013 10:41:15 -0700	[thread overview]
Message-ID: <51B21B3B.8050604@newsguy.com> (raw)
In-Reply-To: <CAD6h2NStRcXm_X=0ib=RtKqVhmsfGo4z=_jzL1hUo_MLcfyBZw@mail.gmail.com>

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

 * Note that this binding currently supports only sets of one register + value.

I am still learning pinctrl and devicetree and studying the driver, so I am not
adament about anything at this point.  Guidance appreciated!

Thanks,
Mike

  reply	other threads:[~2013-06-07 17:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 17:23 pxa27x and pinctrl-single Mike Dunn
2013-06-05 17:23 ` Mike Dunn
2013-06-06  0:43 ` Haojian Zhuang
2013-06-06  0:43   ` Haojian Zhuang
2013-06-06 17:33   ` Mike Dunn
2013-06-06 17:33     ` Mike Dunn
2013-06-06 23:58     ` Haojian Zhuang
2013-06-06 23:58       ` Haojian Zhuang
2013-06-07  0:48       ` Mike Dunn
2013-06-07  0:48         ` Mike Dunn
2013-06-07  1:21         ` Haojian Zhuang
2013-06-07  1:21           ` Haojian Zhuang
2013-06-07 14:50           ` Mike Dunn
2013-06-07 14:50             ` Mike Dunn
2013-06-07 15:16             ` Haojian Zhuang
2013-06-07 15:16               ` Haojian Zhuang
2013-06-07 17:41               ` Mike Dunn [this message]
2013-06-07 17:41                 ` Mike Dunn
2013-06-08  1:20                 ` Haojian Zhuang
2013-06-08  1:20                   ` Haojian Zhuang
2013-06-09 18:05                   ` Mike Dunn
2013-06-09 18:05                     ` Mike Dunn

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=51B21B3B.8050604@newsguy.com \
    --to=mikedunn@newsguy.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.