mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@freescale.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH] [RFC] pinctrl: add a driver for Energy Micro's efm32 SoCs
Date: Fri, 9 Dec 2011 09:01:48 +0800	[thread overview]
Message-ID: <20111209010147.GH7913@S2100-06.ap.freescale.net> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF1750B77BD8@HQMAIL01.nvidia.com>

On Thu, Dec 08, 2011 at 03:14:40PM -0800, Stephen Warren wrote:
> Presumably, the set of pins, groups, and functions is determined by the
> SoC HW. Platform data is usually board-specific rather than SoC specific.
> You have two choices here: You could either parse this data from device
> tree as Arnd suggested (and I think as the TI OMAP pinctrl driver will),
> or do what I've done in the Tegra pinctrl driver, and simply put each
> SoC's data into the driver and select which one to use based on the DT
> compatible flag; I didn't see the point of putting data in to the DT that
> was identical for every board using a given SoC.
> 
I'm not sure about tegra, but for imx, it's very difficult to enumerate
all these data and list them in pinctrl driver.  Sascha gave a few
examples when we discussed about it in another thread.  The TX and RX
pin of UART has 4 options each.  SD could possibly have 1, 4, and 8
data lines.  Display interface could have 16, 24, 32 data lines, etc.
All these options are chosen by board design for given soc pinmux
design.  So putting this data into device tree makes sense for imx too.

-- 
Regards,
Shawn


  reply	other threads:[~2011-12-09  0:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 22:40 Uwe Kleine-König
2011-12-08 22:55 ` Arnd Bergmann
2011-12-09  9:23   ` Uwe Kleine-König
2011-12-09 13:55     ` Arnd Bergmann
2011-12-09 14:15       ` Uwe Kleine-König
2011-12-08 23:14 ` Stephen Warren
2011-12-09  1:01   ` Shawn Guo [this message]
2011-12-09  3:44     ` Stephen Warren
2011-12-09  4:32       ` Shawn Guo
2011-12-09  4:47         ` Stephen Warren
2011-12-09  5:14           ` Shawn Guo
2011-12-09 11:08             ` Sascha Hauer
2011-12-09 13:01               ` Uwe Kleine-König
2011-12-10  0:18               ` Linus Walleij
2011-12-12 14:37                 ` Sascha Hauer
2011-12-12 15:29                   ` Uwe Kleine-König
2011-12-13  0:41                   ` Linus Walleij
2011-12-09 16:53             ` Stephen Warren
2011-12-09 15:03           ` Dong Aisheng
2011-12-09 16:49             ` Stephen Warren
2011-12-09 17:24               ` Tony Lindgren
2011-12-09 17:53                 ` Tony Lindgren
2011-12-10  0:14                   ` Stephen Warren
2011-12-11 19:34                     ` Tony Lindgren
2011-12-09  9:31   ` Uwe Kleine-König
2011-12-10  0:04   ` Linus Walleij

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=20111209010147.GH7913@S2100-06.ap.freescale.net \
    --to=shawn.guo@freescale.com \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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

all inboxes | Powered by JetHome®