From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
Benoit Cousson <b-cousson@ti.com>,
Misael Lopez Cruz <misael.lopez@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH 1/5] ASoC: omap-dmic: Add device tree bindings
Date: Fri, 2 Dec 2011 13:02:42 +0000 [thread overview]
Message-ID: <20111202130242.GO8245@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4ED8C57B.2000503@ti.com>
On Fri, Dec 02, 2011 at 02:32:59PM +0200, Peter Ujfalusi wrote:
> As of now we receive all these information via OMAP hwmod.
> All the properties (addresses, irq, etc) of the HW IP will be coming
> from DT as soon as I can remove the ti,hwmod property.
Oh, right. We should really be churning the device tree like this - the
idea is that the device tree should be stable and independant of kernel
versions. It would be better if we were able to go straight to the one
without hwmod, especially if Benoit is able to get the underlying
changes done soon (which sounded like it might be the case). Could we
define and implement the "real" version now (it should be reasonable to
code blind except possibly for the DMA channel as it's such a direct
mapping) with hwmod left in there as something that's legacy for old
kernels?
next prev parent reply other threads:[~2011-12-02 13:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 9:52 [PATCH 0/5] ASoC: OMAP4: Device tree support for DMIC, McPDM Peter Ujfalusi
2011-12-02 9:52 ` [PATCH 1/5] ASoC: omap-dmic: Add device tree bindings Peter Ujfalusi
2011-12-02 12:25 ` Mark Brown
2011-12-02 12:29 ` Cousson, Benoit
2011-12-02 12:32 ` Peter Ujfalusi
2011-12-02 13:02 ` Mark Brown [this message]
2011-12-02 13:31 ` Cousson, Benoit
2011-12-02 14:00 ` Mark Brown
2011-12-02 14:59 ` Cousson, Benoit
2011-12-02 15:29 ` Mark Brown
2011-12-03 11:22 ` Mark Brown
2011-12-05 13:45 ` Peter Ujfalusi
2011-12-05 15:46 ` Mark Brown
2011-12-07 8:45 ` Peter Ujfalusi
2011-12-11 3:20 ` Mark Brown
2011-12-02 9:52 ` [PATCH 2/5] ASoC: omap-mcpdm: " Peter Ujfalusi
2011-12-02 9:52 ` [PATCH 3/5] OMAP4: devices: Do not create dmic device if the dtb has been provided Peter Ujfalusi
2011-12-02 9:52 ` [PATCH 4/5] OMAP4: devices: Do not create mcpdm " Peter Ujfalusi
2011-12-02 9:53 ` [PATCH 5/5] ARM: OMAP4: DTS: Support for dmic, and McPDM in device tree Peter Ujfalusi
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=20111202130242.GO8245@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.com \
--cc=peter.ujfalusi@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).