devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.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, 8 Aug 2012 23:36:13 -0700	[thread overview]
Message-ID: <20120809063612.GL11011@atomide.com> (raw)
In-Reply-To: <5022532C.9060804@ti.com>

* Peter Ujfalusi <peter.ujfalusi@ti.com> [120808 04:53]:
> 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?

Although the DEVCONF0 and 1 seem static, at least with pinctrl framework we
can keep it dynamic if needed and we're not relying on buggy bootloaders to
set it up.

Regards,

Tony

      reply	other threads:[~2012-08-09  6:36 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
2012-08-09  6:36     ` Tony Lindgren [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=20120809063612.GL11011@atomide.com \
    --to=tony@atomide.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@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).