From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Benoit Cousson <b-cousson@ti.com>
Subject: Re: Re: Re: [PATCH v3 2/5] ASoC: OMAP4: omap-dmic: Initial support for OMAP DMIC
Date: Mon, 28 Nov 2011 15:39:08 +0200 [thread overview]
Message-ID: <1395094.13m9Q8WstL@barack> (raw)
In-Reply-To: <20111128114404.GE2934@opensource.wolfsonmicro.com>
On Monday 28 November 2011 11:44:05 Mark Brown wrote:
> Only if the user is using the same machine driver as you. If the user
> wants a fixed clock rate for the DMIC and sets it on init rather than
> resetting it every time hw_params() is called then this will break.
Ah, true. Will send the update soon.
--
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
next prev parent reply other threads:[~2011-11-28 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 12:20 [PATCH v3 0/5] Support for OMAP4 Digital Microphone interface Peter Ujfalusi
2011-11-25 12:20 ` [PATCH v3 1/5] OMAP4: hwmod: Add names for DMIC memory address space Peter Ujfalusi
2011-11-25 12:20 ` [PATCH v3 2/5] ASoC: OMAP4: omap-dmic: Initial support for OMAP DMIC Peter Ujfalusi
2011-11-27 19:50 ` Mark Brown
2011-11-28 7:49 ` Péter Ujfalusi
2011-11-28 11:44 ` Mark Brown
2011-11-28 13:39 ` Péter Ujfalusi [this message]
2011-11-25 12:20 ` [PATCH v3 3/5] OMAP4: devices: Register OMAP4 DMIC platform device Peter Ujfalusi
2011-11-25 12:20 ` [PATCH v3 4/5] OMAP4: board-4430sdp: Register platform device for digimic codec Peter Ujfalusi
2011-11-25 12:20 ` [PATCH v3 5/5] ASoC: sdp4430: Add support for digital microphones 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=1395094.13m9Q8WstL@barack \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.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 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.