linux-kernel - Re: [PATCH v4 4/4] mmc: sdhci-imx-esdhc: convert to use pinctrl subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120502032707.GA1708@shlinux2.ap.freescale.net>
Date:	Wed, 2 May 2012 11:27:08 +0800
From:	Dong Aisheng <aisheng.dong@...escale.com>
To:	Shawn Guo <shawn.guo@...aro.org>
CC:	Linus Walleij <linus.walleij@...aro.org>,
	Dong Aisheng-B29396 <B29396@...escale.com>,
	"linus.walleij@...ricsson.com" <linus.walleij@...ricsson.com>,
	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
	"kernel@...gutronix.de" <kernel@...gutronix.de>,
	"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v4 4/4] mmc: sdhci-imx-esdhc: convert to use pinctrl
 subsystem

On Wed, May 02, 2012 at 09:51:26AM +0800, Shawn Guo wrote:
> 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.
> 
I can split it.
One question is that will driver convert patch go via subsystem tree
or soc tree?
If adding dummy pinctrl for imx goes via soc tree but sdhci-imx-esdhc
goes via mmc driver, the next one may break.

Regards
Dong Aisheng

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/