devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <b-cousson@ti.com>
Cc: 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: [PATCH 5/5] ARM: OMAP4: DTS: Support for dmic, and McPDM in device tree
Date: Fri,  2 Dec 2011 11:53:00 +0200	[thread overview]
Message-ID: <1322819580-7424-6-git-send-email-peter.ujfalusi@ti.com> (raw)
In-Reply-To: <1322819580-7424-1-git-send-email-peter.ujfalusi@ti.com>

Add DT support for dmic, and McPDM on OMAP4 platforms.
Panda board does not have DMIC lines accessable, so
disable the dmic on panda.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
---
 arch/arm/boot/dts/omap4-panda.dts |    4 ++++
 arch/arm/boot/dts/omap4.dtsi      |    9 +++++++++
 2 files changed, 13 insertions(+), 0 deletions(-)

diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
index c702657..b73b641 100644
--- a/arch/arm/boot/dts/omap4-panda.dts
+++ b/arch/arm/boot/dts/omap4-panda.dts
@@ -27,3 +27,7 @@
 		reg = <0x80000000 0x40000000>; /* 1 GB */
 	};
 };
+
+&dmic_dai {
+	status = "disabled";
+};
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 4c61c82..00cfb73 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -99,5 +99,14 @@
 			reg = <0x48241000 0x1000>,
 			      <0x48240100 0x0100>;
 		};
+
+		dmic_dai: dmic@4012e000 {
+			compatible = "ti,omap4-dmic";
+			ti,hwmods = "dmic";
+		};
+		mcpdm_dai: mcpdm@40132000 {
+			compatible = "ti,omap4-mcpdm";
+			ti,hwmods = "mcpdm";
+		};
 	};
 };
-- 
1.7.8.rc4


      parent reply	other threads:[~2011-12-02  9:53 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
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 ` 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=1322819580-7424-6-git-send-email-peter.ujfalusi@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 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).