From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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, 02 Dec 2011 14:32:59 +0200 [thread overview]
Message-ID: <4ED8C57B.2000503@ti.com> (raw)
In-Reply-To: <20111202122558.GM8245@opensource.wolfsonmicro.com>
On 12/02/2011 02:25 PM, Mark Brown wrote:
> On Fri, Dec 02, 2011 at 11:52:56AM +0200, Peter Ujfalusi wrote:
>
>> +Required properties:
>> + - compatible : "ti,omap4-dmic"
>> + - ti,hwmods : List of hwmod names associated with DMIC, in most case
>> + it is "dmic".
>
> Shouldn't there also be a regs property giving the register window?
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.
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ASoC: omap-dmic: Add device tree bindings
Date: Fri, 02 Dec 2011 14:32:59 +0200 [thread overview]
Message-ID: <4ED8C57B.2000503@ti.com> (raw)
In-Reply-To: <20111202122558.GM8245@opensource.wolfsonmicro.com>
On 12/02/2011 02:25 PM, Mark Brown wrote:
> On Fri, Dec 02, 2011 at 11:52:56AM +0200, Peter Ujfalusi wrote:
>
>> +Required properties:
>> + - compatible : "ti,omap4-dmic"
>> + - ti,hwmods : List of hwmod names associated with DMIC, in most case
>> + it is "dmic".
>
> Shouldn't there also be a regs property giving the register window?
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.
--
P?ter
next prev parent reply other threads:[~2011-12-02 12:32 UTC|newest]
Thread overview: 38+ 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 ` Peter Ujfalusi
2011-12-02 9:52 ` [PATCH 1/5] ASoC: omap-dmic: Add device tree bindings Peter Ujfalusi
2011-12-02 9:52 ` Peter Ujfalusi
2011-12-02 12:25 ` Mark Brown
2011-12-02 12:25 ` Mark Brown
2011-12-02 12:29 ` Cousson, Benoit
2011-12-02 12:29 ` Cousson, Benoit
2011-12-02 12:32 ` Peter Ujfalusi [this message]
2011-12-02 12:32 ` Peter Ujfalusi
2011-12-02 13:02 ` Mark Brown
2011-12-02 13:02 ` Mark Brown
2011-12-02 13:31 ` Cousson, Benoit
2011-12-02 13:31 ` Cousson, Benoit
2011-12-02 14:00 ` Mark Brown
2011-12-02 14:00 ` Mark Brown
2011-12-02 14:59 ` Cousson, Benoit
2011-12-02 14:59 ` Cousson, Benoit
2011-12-02 15:29 ` Mark Brown
2011-12-02 15:29 ` Mark Brown
2011-12-03 11:22 ` Mark Brown
2011-12-03 11:22 ` Mark Brown
2011-12-05 13:45 ` Peter Ujfalusi
2011-12-05 13:45 ` Peter Ujfalusi
2011-12-05 15:46 ` Mark Brown
2011-12-05 15:46 ` Mark Brown
2011-12-07 8:45 ` Peter Ujfalusi
2011-12-07 8:45 ` Peter Ujfalusi
2011-12-11 3:20 ` Mark Brown
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 ` 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 ` Peter Ujfalusi
2011-12-02 9:52 ` [PATCH 4/5] OMAP4: devices: Do not create mcpdm " Peter Ujfalusi
2011-12-02 9:52 ` Peter Ujfalusi
2011-12-02 9:53 ` [PATCH 5/5] ARM: OMAP4: DTS: Support for dmic, and McPDM in device tree Peter Ujfalusi
2011-12-02 9:53 ` 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=4ED8C57B.2000503@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=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=misael.lopez@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 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.