alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ASoC: ak4642: Add Playback Volume control
Date: Mon, 28 Jun 2010 12:07:05 +0900 (JST)	[thread overview]
Message-ID: <w3pfx07svmu.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <w3piq54roby.wl%kuninori.morimoto.gx@renesas.com>


Dear Liam, Mark

> > Is this for the "Master Playback Volume" ? If so, It should be "Master
> > Playback Volume"

Now I'm creating V2 patch.
And I have 2 questions

1) name

Manual said this register name is "Digital Volume Control".
In this case, should I use "Digital Playback Volume" ?
or "Master Playback Volume" ?

2) settings

This chip is

> +/*
> + * Playback Volume (table 39)
> + *
> + * max : 0x00 : +12.0 dB
> + *       ( 0.5 dB step )
> + * min : 0xFE : -115.0 dB
> + * mute: 0xFF
> + */

min is 0xFE (-115.0 dB)
and last 0xFF mean "mute".
and DECLARE_TLV_DB_SCALE have "mute" flag.

In this case,

> +static const DECLARE_TLV_DB_SCALE(out_tlv, -11500, 50, 1);

Is this -11500 correct ?
it should be -11550 ?

> +static const struct snd_kcontrol_new ak4642_snd_controls[] = {
> +
> +	SOC_DOUBLE_R_TLV("Playback Volume", L_DVC, R_DVC,
> +			 0, 0xFF, 1, out_tlv),

And here, Is 0xFF correct here ?
Is it 0xFE ?

I asked because I noticed amixer's output seems not correct.
There is 0.5db difference between register and amixer's output.

Best regards
--
Kuninori Morimoto

  reply	other threads:[~2010-06-28  3:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25  7:57 [PATCH] ASoC: ak4642: Add Playback Volume control Kuninori Morimoto
2010-06-25 10:50 ` Liam Girdwood
2010-06-28  0:30   ` Kuninori Morimoto
2010-06-28  3:07     ` Kuninori Morimoto [this message]
2010-06-28  8:47       ` Mark Brown
2010-06-28  3:10     ` Kuninori Morimoto

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=w3pfx07svmu.wl%kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    /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).