[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201109102237.15193.arnd@arndb.de>
Date: Sat, 10 Sep 2011 22:37:15 +0200
From: Arnd Bergmann <arnd@...db.de>
To: "Russell King - ARM Linux" <linux@....linux.org.uk>
Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
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 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
> the point of having this special ASoC code look up the platform compatible
> property in a table of strings to find a different string to manually
> create a device with. Why not just add the bloody device to the DT
> file in the first place? That's partly what DT is there for - to create
> platform specific struct devices.
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.
Arnd
--
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