From: KaiChieh Chuang <kaichieh.chuang@mediatek.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, garlic.tseng@mediatek.com,
linux-mediatek@lists.infradead.org, chipeng.chang@mediatek.com,
wsd_upstream@mediatek.com
Subject: Re: [PATCH v2 1/5] ASoC: add mt6351 codec driver
Date: Sat, 21 Apr 2018 07:49:24 +0800 [thread overview]
Message-ID: <1524268164.3290.31.camel@mtksdaap41> (raw)
In-Reply-To: <20180418164040.GG10061@sirena.org.uk>
sorry for replying this early comment now,
i have to study on tlv first.
> > +/* dl pga gain */
> > +static const char *const dl_pga_gain[] = {
> > + "8Db", "7Db", "6Db", "5Db", "4Db",
> > + "3Db", "2Db", "1Db", "0Db", "-1Db",
> > + "-2Db", "-3Db", "-4Db", "-5Db", "-6Db",
> > + "-7Db", "-8Db", "-9Db", "-10Db", "-40Db",
> > +};
>
> These gains should be put in TLVs rather than an enum so userspace can
> handle them (also it should be dB not Db). You can handle irregular
> step sizes like these with DECLARE_TLV_DB_SCALE(), there's several
> examples in the code already.
We declare this enum for user space to operate on enum directly,
unlike alsa-lib, we use tinyalsa in Android, if declared in tlv,
the mixer control just become a integer control, which is not
informative for user space.
> > +static int dl_pga_get(struct snd_kcontrol *kcontrol,
> > + struct snd_ctl_elem_value *ucontrol)
> > +{
> > + struct snd_soc_codec *codec = snd_soc_kcontrol_codec(kcontrol);
> > + struct mt6351_priv *priv = snd_soc_codec_get_drvdata(codec);
> > +
> > + ucontrol->value.integer.value[0] = priv->ana_gain[kcontrol->id.device];
> > +
> > + if (ucontrol->value.integer.value[0] == 0x1f) /* reg idx for -40dB*/
> > + ucontrol->value.integer.value[0] = ARRAY_SIZE(dl_pga_gain) - 1;
>
> Why do this rewriting?
A little awkward gain register here,
the range is for 8dB ~ -10dB and -40dB, corresponding to reg index 0 ~
18 and 31.
00000: +8dB.
00001: +7dB.
10010: -10dB
11111: -40dB(Mute).
and where 19 ~ 30 is not defined, and shouldn't be set.
i think tlv not yet support this kind of gain control?
Maybe i'll just declare 8dB ~ -10dB for now.
next prev parent reply other threads:[~2018-04-20 23:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 0:32 [PATCH v2 0/5] ASoC: mediatek: add support for mt6797 SoC KaiChieh Chuang
[not found] ` <20180416003252.4177-1-kaichieh.chuang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-04-16 0:32 ` [PATCH v2 1/5] ASoC: add mt6351 codec driver KaiChieh Chuang
2018-04-18 16:40 ` Mark Brown
2018-04-19 1:58 ` KaiChieh Chuang
2018-04-19 14:41 ` Mark Brown
2018-04-20 6:54 ` KaiChieh Chuang
2018-04-20 23:49 ` KaiChieh Chuang [this message]
2018-04-23 11:39 ` Mark Brown
2018-04-16 0:32 ` [PATCH v2 2/5] ASoC: mt6797: add structure define and clock control function for 6797 KaiChieh Chuang
2018-04-16 0:32 ` [PATCH v2 3/5] ASoC: mt6797: add mt6797 platform driver KaiChieh Chuang
2018-04-18 16:46 ` Mark Brown
2018-04-19 1:51 ` KaiChieh Chuang
2018-04-19 11:29 ` Mark Brown
2018-04-16 0:32 ` [PATCH v2 4/5] ASoC: add mt6797-mt6351 driver and config option KaiChieh Chuang
2018-04-16 0:32 ` [PATCH v2 5/5] ASoC: mediatek: add documents for mt6797 KaiChieh Chuang
2018-04-18 16:46 ` [PATCH v2 0/5] ASoC: mediatek: add support for mt6797 SoC Mark Brown
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=1524268164.3290.31.camel@mtksdaap41 \
--to=kaichieh.chuang@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chipeng.chang@mediatek.com \
--cc=garlic.tseng@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=wsd_upstream@mediatek.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