alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Lambert, David" <dlambert@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
	Paul Walmsley <paul@pwsan.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/5] ASoC: DMIC: Adding the OMAP DMIC driver
Date: Wed, 5 Jan 2011 14:03:26 +0000	[thread overview]
Message-ID: <20110105140325.GB746@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTi=k981bx0jjWhJdZmxY8-Uyt=KSB4v0E-uKQ_pL@mail.gmail.com>

On Wed, Jan 05, 2011 at 07:56:13AM -0600, Lambert, David wrote:
> On Tue, Dec 28, 2010 at 8:18 AM, Mark Brown

> > A comment explaining why we don't actually do anything with the request
> > would be helpful.  Given that we're ignoring the event it'd seem better
> > to just leave it masked and not take the interrupt in the first place.

> Since the IRQ handler isn't really doing anything in this driver,
> would it better
> to just not have one?

Possibly, if the hardware doesn't care.

> >> +             dmic->clk_freq = freq;
> >> +             break;
> >> +     default:
> >> +             dev_err(dai->dev, "clk freq not supported %d\n", freq);
> >> +             ret = -EINVAL;
> >> +             goto err_freq;
> >> +     }

> > Can't you ask the parent clock what rate it's set to?

> Didn't really think there was a need for that on the audio driver.
> There are clock API's available
> to query that already.

That's my point - you're requiring that the user pass in the rate rather
than querying the clock API.

  reply	other threads:[~2011-01-05 14:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28  4:17 [PATCH 0/5] Adding OMAP DMIC driver to kernel David Lambert
2010-12-28  4:17 ` [PATCH 1/5] ASoC: DMIC: Adding the OMAP DMIC driver David Lambert
2010-12-28 11:14   ` Felipe Balbi
2010-12-29  1:13     ` Lambert, David
2010-12-29  9:47       ` Felipe Balbi
2010-12-29 10:35         ` Liam Girdwood
2010-12-29 10:44           ` Felipe Balbi
2010-12-29 11:52             ` Liam Girdwood
2010-12-29 11:56               ` Mark Brown
2010-12-29 11:59                 ` Felipe Balbi
2010-12-29 12:11                   ` Mark Brown
2010-12-29 12:04               ` Felipe Balbi
2010-12-29 13:00                 ` Liam Girdwood
2010-12-29 13:07                   ` Felipe Balbi
2010-12-28 14:18   ` Mark Brown
2011-01-05 13:56     ` Lambert, David
2011-01-05 14:03       ` Mark Brown [this message]
2010-12-28  4:17 ` [PATCH 2/5] ASoC: DMIC codec: Adding a generic DMIC codec David Lambert
2010-12-28 14:29   ` Mark Brown
2010-12-28  4:17 ` [PATCH 3/5] ASoC: DMIC: Adding OMAP DMIC driver to build David Lambert
2010-12-28 11:40   ` Mark Brown
2010-12-29  2:21     ` Lambert, David
2010-12-28  4:17 ` [PATCH 4/5] OMAP4: hwmod: add entries for DMIC driver David Lambert
2010-12-28  4:17 ` [PATCH 5/5] MAP4: DMIC: Add DMIC codec platform devices David Lambert
2010-12-28 11:23   ` Felipe Balbi

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=20110105140325.GB746@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dlambert@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=paul@pwsan.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).