devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: OMAP: Configuring CONTROL_DEVCONF0 register via DT with pinctrl
Date: Wed, 08 Aug 2012 14:53:16 +0300	[thread overview]
Message-ID: <5022532C.9060804@ti.com> (raw)
In-Reply-To: <20120807111041.GY11011@atomide.com>

On 08/07/2012 02:10 PM, Tony Lindgren wrote:
> You need to also consider that CONTROL_DEVCONF0 has the MMC/SDIO module input
> clock selection. So pinctrl-single binding would have to be expanded to also
> support one-bit-per-mux type registers in addition to one-register-per-mux
> registers. And then this could also be used for the MMC/SDIO module input clock.

Or if the clock selection for MMC/SDIO also static on a board we can just do
the mux config once, configuring McBSP1 and MMC/SDIO at the same time?

>> In .dtsi file of the SoC:
>>
>> control_devconf0: pinmux@48002274 {
>> 	compatible = "pinctrl-single";
>> 	reg = <0x48002274 4>;	/* Single register */
>> 	#address-cells = <1>;
>> 	#size-cells = <0>;
>> 	pinctrl-single,register-width = <32>;
>> 	pinctrl-single,function-mask = <0x5F>;
>> };
> 
> The pinctrl-single,function-mask is for all the registers in the range,
> we also need something to specify the device specific mux bits.

Yes, I understand that.
I think this all depends if we want to change the mux configurations runtime,
on the fly as well. If it is only done once at boot time why not just set up
the register (mux) as the board design dictates?

>> In the .dts file of the board which needs to change the CLKR/FSR configuration:
>>
>> &control_devconf0 {
>> 	pinctrl-names = "default";
>> 	pinctrl-0 = <&mcbsp1_pins>;
>>
>> 	mcbsp1_pins: pinmux_mcbsp1_pins {
>> 		pinctrl-single,pins = <0x00 0x18>; /* CLKR/FSR from CLKX/FSX
>> 						    * pin */
>> 	};
>>
>> };
> 
> I think adding support for one-bit-per-mux would require adding something
> like this for the binding:
> 
>  	mcbsp1_pins: pinmux_mcbsp1_pins {
> 		/*                   offset bits mask */
>  		pinctrl-single,bits = <0x00 0x18 0x18>;
> 	};
> 
> As otherwise you would not know which bits to clear for alternative
> named modes. Or got any better ideas?

I was also thought that this type of feature might be useful at some point in
pinctrl.
However if we have static mux configuration on a boards vendors can set up the
mux for their devices using the currently available bindings.


-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-08-08 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27  9:43 OMAP: Configuring CONTROL_DEVCONF0 register via DT with pinctrl Peter Ujfalusi
2012-08-07 11:10 ` Tony Lindgren
2012-08-08 11:53   ` Peter Ujfalusi [this message]
2012-08-09  6:36     ` Tony Lindgren

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=5022532C.9060804@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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).