From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH v2] ASoC: omap: convert per-board modules to platform drivers Date: Sat, 10 Sep 2011 22:43:44 +0100 Message-ID: <20110910214343.GB21361@opensource.wolfsonmicro.com> References: <3110288.bQbb0H2ME1@wuerfel> <20110909193010.GA2993@opensource.wolfsonmicro.com> <20110909205645.GA16355@n2100.arm.linux.org.uk> <201109102237.15193.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 1F61C103810 for ; Sat, 10 Sep 2011 23:43:46 +0200 (CEST) Content-Disposition: inline In-Reply-To: <201109102237.15193.arnd@arndb.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Arnd Bergmann Cc: alsa-devel@alsa-project.org, Russell King - ARM Linux , Tony Lindgren , Jassi Brar , linux-kernel@vger.kernel.org, Mans Rullgard , Grant Likely , Takashi Iwai , linaro-dev@lists.linaro.org, linux-omap@vger.kernel.org, Liam Girdwood , linux-arm-kernel@lists.infradead.org List-Id: alsa-devel@alsa-project.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@opensource.wolfsonmicro.com (Mark Brown) Date: Sat, 10 Sep 2011 22:43:44 +0100 Subject: [PATCH v2] ASoC: omap: convert per-board modules to platform drivers In-Reply-To: <201109102237.15193.arnd@arndb.de> References: <3110288.bQbb0H2ME1@wuerfel> <20110909193010.GA2993@opensource.wolfsonmicro.com> <20110909205645.GA16355@n2100.arm.linux.org.uk> <201109102237.15193.arnd@arndb.de> Message-ID: <20110910214343.GB21361@opensource.wolfsonmicro.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934123Ab1IJVnr (ORCPT ); Sat, 10 Sep 2011 17:43:47 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:46755 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933810Ab1IJVnq (ORCPT ); Sat, 10 Sep 2011 17:43:46 -0400 Date: Sat, 10 Sep 2011 22:43:44 +0100 From: Mark Brown To: Arnd Bergmann Cc: Russell King - ARM Linux , Grant Likely , alsa-devel@alsa-project.org, Liam Girdwood , Tony Lindgren , Jassi Brar , linux-kernel@vger.kernel.org, Jaroslav Kysela , Takashi Iwai , Jarkko Nikula , linaro-dev@lists.linaro.org, linux-omap@vger.kernel.org, Mans Rullgard , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2] ASoC: omap: convert per-board modules to platform drivers Message-ID: <20110910214343.GB21361@opensource.wolfsonmicro.com> References: <3110288.bQbb0H2ME1@wuerfel> <20110909193010.GA2993@opensource.wolfsonmicro.com> <20110909205645.GA16355@n2100.arm.linux.org.uk> <201109102237.15193.arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201109102237.15193.arnd@arndb.de> X-Cookie: You will outgrow your usefulness. User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.