devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Liam Girdwood <lrg@ti.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Tony Lindgren <tony@atomide.com>,
	peter.ujfalusi@ti.com, alsa-devel@alsa-project.org,
	Benoit Cousson <b-cousson@ti.com>,
	devicetree-discuss@lists.ozlabs.org
Subject: [PATCH v2 0/2] ASoC: OMAP4 DMIC, McPDM device tree support
Date: Wed, 16 May 2012 14:29:54 +0300	[thread overview]
Message-ID: <1337167796-8632-1-git-send-email-peter.ujfalusi@ti.com> (raw)

Hello,

Add DT support and the binding documentation for OMAP4+ DMIC, and McPDM ASoC dai
drivers.

Changes since v1:
- Ducumentation update: add properties for register address/size, interrupt
  number (as Suggested by Mark and Tony).

I have not added Mark's acked-by since I think the changes are big enough from
v1.

Regards,
Peter
---
Peter Ujfalusi (2):
  ASoC: omap-mcpdm: Add device tree bindings
  ASoC: omap-dmic: Add device tree bindings

 .../devicetree/bindings/sound/omap-dmic.txt        |   21 ++++++++++++++++++++
 .../devicetree/bindings/sound/omap-mcpdm.txt       |   21 ++++++++++++++++++++
 sound/soc/omap/omap-dmic.c                         |    8 +++++++
 sound/soc/omap/omap-mcpdm.c                        |    8 +++++++
 4 files changed, 58 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/sound/omap-dmic.txt
 create mode 100644 Documentation/devicetree/bindings/sound/omap-mcpdm.txt

-- 
1.7.8.6

             reply	other threads:[~2012-05-16 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 11:29 Peter Ujfalusi [this message]
2012-05-16 11:29 ` [PATCH v2 1/2] ASoC: omap-mcpdm: Add device tree bindings Peter Ujfalusi
2012-05-16 11:45   ` Mark Brown
2012-05-16 11:29 ` [PATCH v2 2/2] ASoC: omap-dmic: " Peter Ujfalusi
2012-05-16 11:47   ` Mark Brown

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=1337167796-8632-1-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=lrg@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).