From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Ujfalusi Subject: Re: [PATCH] ASoC: twl6040: Support for DT Date: Tue, 15 May 2012 10:41:53 +0300 Message-ID: <4FB208C1.2080503@ti.com> References: <20120509133511.GQ3955@opensource.wolfsonmicro.com> <4FACF1C2.7050008@ti.com> <20120511130816.GB3960@opensource.wolfsonmicro.com> <20120514153414.GM5140@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20120514153414.GM5140@atomide.com> 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: Tony Lindgren Cc: alsa-devel@alsa-project.org, "Cousson, Benoit" , "devicetree-discuss@lists.ozlabs.org" , Mark Brown , Misael Lopez Cruz , Liam Girdwood , Samuel Ortiz List-Id: devicetree@vger.kernel.org On 05/14/2012 06:34 PM, Tony Lindgren wrote: > I agree we should not omit the register ranges from DT. That is > hardware specific information that other operating systems possibly > need, and they don't have hwmod. I was considering to do that for the omap-mcpdm, omap-dmic. I think the reason I did not done it is that none of the other dt sections for OMAP devices have this information (most probably for a reason). -- = P=E9ter