public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Dong Aisheng <b29396@freescale.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org,
	linus.walleij@stericsson.com, s.hauer@pengutronix.de,
	shawn.guo@freescale.com, kernel@pengutronix.de,
	grant.likely@secretlab.ca, rob.herring@calxeda.com
Subject: Re: [PATCH 2/3] pinctrl: pinctrl-imx: add imx6q pinctrl driver
Date: Tue, 17 Apr 2012 14:12:50 -0600	[thread overview]
Message-ID: <4F8DCEC2.2060800@wwwdotorg.org> (raw)
In-Reply-To: <1334333915-1174-2-git-send-email-b29396@freescale.com>

On 04/13/2012 10:18 AM, Dong Aisheng wrote:
> From: Dong Aisheng <dong.aisheng@linaro.org>
> 
> Signed-off-by: Dong Aisheng <dong.aisheng@linaro.org>

> diff --git a/drivers/pinctrl/pinctrl-imx.c b/drivers/pinctrl/pinctrl-imx.c

>  static const struct of_device_id imx_pmx_dt_ids[] = {
> +#ifdef CONFIG_PINCTRL_IMX6Q
> +	{ .compatible = "fsl,imx6q-iomuxc", .data = (void *) &imx6q_pinctrl_info, },
> +#endif
>  	{ /* sentinel */ }
>  };
>  MODULE_DEVICE_TABLE(of, imx_pmx_dt_ids);

Sorry for the slow review.

Based on SPEAr pinctrl review comments, we shouldn't have a single
driver that knows about all the different SoCs that it could support,
but rather one driver per SoC, with each of those calling into some
utility code in the core driver to do all the probe/remove work.

For more details, see commit a4c0738 "pinctrl: tegra: refactor probe
handling" in
git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git
(in branch for-3.5/gpio-pinmux).

  reply	other threads:[~2012-04-17 20:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 16:18 [PATCH 1/3] pinctrl: pinctrl-imx: add imx pinctrl core driver Dong Aisheng
2012-04-13 16:18 ` [PATCH 2/3] pinctrl: pinctrl-imx: add imx6q pinctrl driver Dong Aisheng
2012-04-17 20:12   ` Stephen Warren [this message]
2012-04-18  3:40     ` Dong Aisheng
2012-04-13 16:18 ` [PATCH 3/3] ARM: imx6q: switch to use " Dong Aisheng
2012-04-14 13:53   ` Sascha Hauer
2012-04-15  4:03     ` Dong Aisheng
2012-04-15  7:37       ` Shawn Guo
2012-04-16  3:35         ` Dong Aisheng
2012-04-20  1:08           ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-24  8:23           ` Linus Walleij
2012-04-24  8:46             ` Dong Aisheng
2012-04-17 20:23   ` Stephen Warren
2012-04-13 18:17 ` [PATCH 1/3] pinctrl: pinctrl-imx: add imx pinctrl core driver Dong Aisheng
2012-04-14 13:48 ` Sascha Hauer
2012-04-15  3:49   ` Dong Aisheng
2012-04-15 14:17     ` Shawn Guo
2012-04-15 14:45       ` Sascha Hauer
2012-04-15 17:29       ` Sascha Hauer
2012-04-16  1:47         ` Shawn Guo
2012-04-16 18:01           ` Stephen Warren
2012-04-16  3:47       ` Dong Aisheng
2012-04-16  3:46         ` Shawn Guo
2012-04-17  9:57           ` Dong Aisheng
2012-04-17 12:30             ` Sascha Hauer
2012-04-18  3:38               ` Dong Aisheng
2012-04-17 20:58 ` Stephen Warren
2012-04-18  7:19   ` Dong Aisheng
2012-04-18 18:06     ` Stephen Warren
2012-04-19 15:28 ` Shawn Guo

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=4F8DCEC2.2060800@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=b29396@freescale.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawn.guo@freescale.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