From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@opensource.wolfsonmicro.com (Mark Brown) Date: Mon, 13 Feb 2012 22:06:28 -0800 Subject: [PATCH v2 6/9] ARM: mx31ads: add audmux device In-Reply-To: <20120214013506.GA3276@b20223-02.ap.freescale.net> References: <1328148728-32258-7-git-send-email-richard.zhao@linaro.org> <20120202085521.GB9773@S2101-09.ap.freescale.net> <20120202091132.GD9773@S2101-09.ap.freescale.net> <20120202092427.GB32403@b20223-02.ap.freescale.net> <20120202130901.GE9773@S2101-09.ap.freescale.net> <20120202135805.GB3015@richard-laptop> <20120203021554.GE32403@b20223-02.ap.freescale.net> <20120203133240.GB12915@S2101-09.ap.freescale.net> <20120214013506.GA3276@b20223-02.ap.freescale.net> Message-ID: <20120214060627.GB13456@opensource.wolfsonmicro.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Feb 14, 2012 at 09:35:07AM +0800, Richard Zhao wrote: > On Sun, Feb 05, 2012 at 12:50:15PM +0800, Richard Zhao wrote: > > no, it is asoc machine driver to have machine specific code. > > the machine driver do not correspond to any hw device, which cause hard > > to bind dt or create platform device. > I'll have to keep audmux driver in arch/, till ASOC machine driver > has a way to get platfrom parameters. Machine drivers can easily get platform data, they're just regular drivers of whatever type so can get platform data in the same way that any other driver for their bus can. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: