From: Shawn Guo <shawn.guo@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dong Aisheng <b29396@freescale.com>,
linus.walleij@stericsson.com,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
kernel@pengutronix.de, s.hauer@pengutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 4/4] mmc: sdhci-imx-esdhc: convert to use pinctrl subsystem
Date: Wed, 2 May 2012 09:51:26 +0800 [thread overview]
Message-ID: <20120502015124.GP2194@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <CACRpkdbE=fFhTr=MyD-2dgV=W07Kb-T+ax4dgdjZ8ONzoz3K7A@mail.gmail.com>
On Wed, May 02, 2012 at 01:12:58AM +0200, Linus Walleij wrote:
> If I cannot apply it there are two ways to proceed:
> 1. Wait for next merge window
> 2. Pull pinctrl into i.MX tree
>
Yes, if we would not wait for next merge window, I prefer to ask Arnd,
Olof to pull pinctrl into arm-soc as a dependency and we convert imx
drivers to the subsystem in there.
BTW, this patch should be split into two. Adding dummy pinctrl for
imx should be one patch, and sdhci-imx-esdhc should be separate one.
And we may want to come up a series to convert all outstanding imx
driver to use pinctrl API, one patch for one driver with subsystem
maintainer Cc on the corresponding driver patch.
--
Regards,
Shawn
next prev parent reply other threads:[~2012-05-02 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 12:26 [PATCH v5 1/4] dt: add of_get_child_count helper function Dong Aisheng
2012-04-27 12:26 ` [PATCH v4 2/4] pinctrl: pinctrl-imx: add imx pinctrl core driver Dong Aisheng
2012-05-01 23:07 ` Linus Walleij
2012-04-27 12:26 ` [PATCH v4 3/4] pinctrl: pinctrl-imx: add imx6q pinctrl driver Dong Aisheng
2012-04-27 12:26 ` [PATCH v4 4/4] mmc: sdhci-imx-esdhc: convert to use pinctrl subsystem Dong Aisheng
2012-05-01 23:12 ` Linus Walleij
2012-05-02 1:51 ` Shawn Guo [this message]
2012-05-02 3:27 ` Dong Aisheng
2012-05-02 3: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=20120502015124.GP2194@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--cc=b29396@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--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 \
/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®