[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110910214343.GB21361@opensource.wolfsonmicro.com>
Date: Sat, 10 Sep 2011 22:43:44 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Grant Likely <grant.likely@...retlab.ca>,
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 Sat, Sep 10, 2011 at 10:37:15PM +0200, Arnd Bergmann wrote:
> On Friday 09 September 2011, Russell King - ARM Linux wrote:
> > That's just twisted and utterly insane - adding more code for precisely
> > zero benefit what so ever. Think about it - the device tree is already
> > creating platform devices for entries in the device tree file. What's
> Exactly. No driver or (worse) user program should ever need to look at
> the top-level compatible property. When you want information about a
> localized part of the system (e.g. the ASoC components), you should
> look up the information for that component.
Right, and this is the state of the art right now. I can see why people
find this inelegant and want to come up with a way of automatically
generating all these different devices to describe boards especially
with the non-device tree systems, though, so if people want to work on
that stuff I don't see a problem with it.
--
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