From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/4] mmc: sdhci-imx-esdhc: convert to use pinctrl subsystem
Date: Fri, 27 Apr 2012 10:31:42 +0200 [thread overview]
Message-ID: <20120427083142.GY17184@pengutronix.de> (raw)
In-Reply-To: <20120427082930.GC826@shlinux2.ap.freescale.net>
On Fri, Apr 27, 2012 at 04:29:31PM +0800, Dong Aisheng wrote:
> mach-imx27ipcam.c mach-mx31ads.c mach-mx51_babbage.o mach-pca100.c
> mach-imx27lite.c mach-mx31ads.o mach-mx51_efikamx.c mach-pcm037.c
>
> Some of them i'm not familiar and i don't know whether they may use pinctrl
> so i just patched the affected ones.
>
> One lazy method may be just patch all board files without pinctrl support
> and it will not cause any error.
>
> What's your suggestion?
>
> > pinctrl. Let's add the provide_dummies call to the SoCs instead which
> > do not have pinctrl yet.
> >
> You meant add provide_dummies call in imx*_soc_init call?
> We could do it but there might be a case that some boards are converted
> to use pinctrl while others still not but they're based on the same soc.
> For examples, 4 mx53 boards and we may not be able to convert them all at
> the same time.
My point is that none of the mx5 boards have pinctrl since there is no
SoC driver for it.
For DT based boards pinctrl should be mandatory once the SoC has pinctrl
support. All non DT boards probably won't get pinctrl anyway.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-04-27 8:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 14:40 [PATCH v4 1/4] dt: add of_get_child_count helper function Dong Aisheng
2012-04-26 14:40 ` [PATCH v3 2/4] pinctrl: pinctrl-imx: add imx pinctrl core driver Dong Aisheng
2012-04-26 14:44 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-26 15:15 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-27 5:48 ` Shawn Guo
2012-04-27 6:28 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-27 7:25 ` Shawn Guo
2012-04-27 7:11 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-27 8:11 ` Shawn Guo
2012-04-27 9:29 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-27 3:48 ` Dong Aisheng
2012-04-27 6:31 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-27 7:30 ` Sascha Hauer
2012-04-26 14:44 ` Dong Aisheng
2012-04-27 5:30 ` Shawn Guo
2012-04-27 8:54 ` Shawn Guo
2012-04-27 11:24 ` Dong Aisheng
2012-04-26 14:40 ` [PATCH v3 4/4] mmc: sdhci-imx-esdhc: convert to use pinctrl subsystem Dong Aisheng
2012-04-26 16:32 ` Stephen Warren
2012-04-27 7:35 ` Sascha Hauer
2012-04-27 8:29 ` Dong Aisheng
2012-04-27 8:26 ` Shawn Guo
2012-04-27 8:31 ` Sascha Hauer [this message]
2012-04-27 8:54 ` Dong Aisheng
2012-04-27 8:47 ` Sascha Hauer
2012-04-27 9:13 ` Dong Aisheng
2012-04-26 16:24 ` [PATCH v4 1/4] dt: add of_get_child_count helper function Stephen Warren
2012-04-27 3:28 ` Dong Aisheng
2012-04-27 3:36 ` [PATCH v5 1/1] " Dong Aisheng
2012-04-27 15:25 ` Stephen Warren
2012-05-01 23:05 ` Linus Walleij
[not found] ` <1335451227-27709-3-git-send-email-b29396@freescale.com>
2012-04-27 5:35 ` [PATCH v3 3/4] pinctrl: pinctrl-imx: add imx6q pinctrl driver Shawn Guo
2012-04-27 6:45 ` Sascha Hauer
2012-04-27 7:16 ` Dong Aisheng
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=20120427083142.GY17184@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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 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).