From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: alsa-devel@alsa-project.org, "Cousson, Benoit" <b-cousson@ti.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Misael Lopez Cruz <misael.lopez@ti.com>,
Liam Girdwood <lrg@ti.com>, Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH] ASoC: twl6040: Support for DT
Date: Tue, 15 May 2012 10:41:53 +0300 [thread overview]
Message-ID: <4FB208C1.2080503@ti.com> (raw)
In-Reply-To: <20120514153414.GM5140@atomide.com>
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éter
prev parent reply other threads:[~2012-05-15 7:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 11:52 [PATCH] ASoC: twl6040: Support for DT Peter Ujfalusi
2012-05-08 12:26 ` Mark Brown
2012-05-08 12:42 ` Peter Ujfalusi
2012-05-08 13:41 ` Mark Brown
2012-05-09 12:01 ` Peter Ujfalusi
2012-05-09 13:35 ` Mark Brown
2012-05-10 12:55 ` Peter Ujfalusi
2012-05-11 14:05 ` Mark Brown
[not found] ` <20120509133511.GQ3955-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-05-11 11:02 ` Cousson, Benoit
2012-05-11 13:08 ` Mark Brown
[not found] ` <20120511130816.GB3960-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-05-11 15:44 ` Cousson, Benoit
2012-05-11 20:34 ` Mark Brown
2012-05-14 11:38 ` Peter Ujfalusi
2012-05-14 12:11 ` Mark Brown
2012-05-15 8:00 ` Peter Ujfalusi
2012-05-14 15:34 ` Tony Lindgren
2012-05-15 7:41 ` Peter Ujfalusi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB208C1.2080503@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.com \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.