[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110908224731.GB5201@opensource.wolfsonmicro.com>
Date: Thu, 8 Sep 2011 15:47:31 -0700
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Arnd Bergmann <arnd@...db.de>, alsa-devel@...a-project.org,
Liam Girdwood <lrg@...com>, Tony Lindgren <tony@...mide.com>,
Jassi Brar <jassisinghbrar@...il.com>,
linux-kernel@...r.kernel.org, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.de>,
Jarkko Nikula <jhnikula@...il.com>,
linaro-dev@...ts.linaro.org, linux-omap@...r.kernel.org,
Mans Rullgard <mans.rullgard@...aro.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] ASoC: omap: convert per-board modules to platform
drivers
On Thu, Sep 08, 2011 at 11:37:20PM +0100, Russell King - ARM Linux wrote:
> With DT of course, all devices get instantiated from the device tree,
> so there should not be any more platform specific chunks of code in
> these locations (ha, it couldn't be solved with platform data so I
> suspect it will continue to persist, forever unsolved.)
That's not the case at all for audio, the PCB schematic for the audio
subsystem on a device like a smartphone is a sufficiently interesting
piece of hardware to be a device with a driver in its own right. The
ASoC machine drivers aren't about instantiating devices, they are about
controlling the interrelationships between the various devices in the
audio subsystem.
What will happen for device tree is that there will be a device in the
device tree for the ASoC board.
--
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/
Powered by blists - more mailing lists