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>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Benoit Cousson <b-cousson@ti.com>
Subject: Re: [PATCH 2/5] ASoC: OMAP4: omap-dmic: Initial support for OMAP DMIC
Date: Tue, 22 Nov 2011 16:01:05 +0000 [thread overview]
Message-ID: <20111122160105.GC30583@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1321970520-8909-3-git-send-email-peter.ujfalusi@ti.com>
On Tue, Nov 22, 2011 at 04:01:57PM +0200, Peter Ujfalusi wrote:
> + switch (params_rate(params)) {
> + case 96000:
> + case 192000:
> + break;
Why doesn't the driver need to tell the hardware what sample rate to run
at?
> + dmic_clk = clk_get(dmic->dev, "dmic_fck");
> + if (IS_ERR(dmic_clk)) {
> + dev_err(dmic->dev, "cant get dmic_fck\n");
> + return -ENODEV;
> + }
Why aren't we getting and holding a reference to the clock over the
entire lifetime of the driver?
> + /* disable clock while reparenting */
> + pm_runtime_put_sync(dmic->dev);
> + ret = clk_set_parent(dmic_clk, parent_clk);
> + pm_runtime_get_sync(dmic->dev);
Since we're only allowing reclocking while idle shouldn't the clock
already be disabled? Seems like it ought to be good for power if
nothing else...
> +static int omap_dmic_set_clkdiv(struct snd_soc_dai *dai,
> + int div_id, int div)
> +{
DMIC clocking is usually fairly simple so it seems surprising that the
driver isn't able to figure this out for itself.
next prev parent reply other threads:[~2011-11-22 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 14:01 [PATCH 0/5] Support for OMAP4 Digital Microphone interface Peter Ujfalusi
2011-11-22 14:01 ` [PATCH 1/5] OMAP4: hwmod: Add names for DMIC memory address space Peter Ujfalusi
2011-11-22 14:01 ` [PATCH 2/5] ASoC: OMAP4: omap-dmic: Initial support for OMAP DMIC Peter Ujfalusi
2011-11-22 16:01 ` Mark Brown [this message]
2011-11-23 8:48 ` Péter Ujfalusi
2011-11-23 10:58 ` Mark Brown
2011-11-23 14:00 ` Péter Ujfalusi
2011-11-23 14:30 ` Mark Brown
2011-11-23 15:24 ` Péter Ujfalusi
2011-11-23 15:28 ` Mark Brown
2011-11-22 14:01 ` [PATCH 3/5] OMAP4: devices: Register OMAP4 DMIC platform device Peter Ujfalusi
2011-11-22 14:01 ` [PATCH 4/5] OMAP4: board-4430sdp: Register platform device for digimic codec Peter Ujfalusi
2011-11-22 14:02 ` [PATCH 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=20111122160105.GC30583@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@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