alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Mack <zonque@gmail.com>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: [PATCH] ALSA: ASoC: Add codec driver for AK5386
Date: Fri, 8 Mar 2013 19:51:39 +0800	[thread overview]
Message-ID: <20130308115137.GG28481@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1362740848-15752-1-git-send-email-zonque@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1006 bytes --]

On Fri, Mar 08, 2013 at 12:07:28PM +0100, Daniel Mack wrote:
> Adds a driver for Asahi Kasei's AK5386 Single-ended 24-Bit 192kHz
> delta-sigma ADC. The device has no control port interface but an
> optional RESET/PDN GPIO pin.

Applied, thanks.  One possible update...

> +	/*
> +	 * From the datasheet:
> +	 *
> +	 * All external clocks (MCLK, SCLK and LRCK) must be present unless
> +	 * PDN pin = “L”. If these clocks are not provided, the AK5386 may
> +	 * draw excess current due to its use of internal dynamically
> +	 * refreshed logic. If the external clocks are not present, place
> +	 * the AK5386 in power-down mode (PDN pin = “L”).
> +	 */
> +
> +	if (gpio_is_valid(priv->reset_gpio))
> +		gpio_set_value(priv->reset_gpio, 1);

I think that mute_stream() which was recently added and I mentioned in
my review of your previous patch would do what you want here
idiomatically - the effect is about the same as a mute and it should be
called bat the right moments.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2013-03-08 11:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 11:07 [PATCH] ALSA: ASoC: Add codec driver for AK5386 Daniel Mack
2013-03-08 11:51 ` Mark Brown [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=20130308115137.GG28481@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=zonque@gmail.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).