linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "jeff_chang(張世佳)" <jeff_chang@richtek.com>
To: Jaroslav Kysela <perex@perex.cz>,
	Jeff Chang <richtek.jeff.chang@gmail.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
	"tiwai@suse.com" <tiwai@suse.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ASoC: Add MediaTek MT6660 Speaker Amp Driver
Date: Thu, 12 Dec 2019 11:05:13 +0000	[thread overview]
Message-ID: <33393c67cee243a59fb0043a276f4e4a@ex1.rt.l> (raw)
In-Reply-To: <02c25504-dec5-4026-6e2b-d3763e70663a@perex.cz>

Dear Jarsolav:

Thanks for your reply.

I will send a new patch later.


Thanks & BRs
Jeff Chang
Tel 886-3-5526789 Ext 2357
14F, No. 8, Taiyuen 1st st., Zhubei City,
Hsinchu County, Taiwan 30288



-----Original Message-----
From: Jaroslav Kysela [mailto:perex@perex.cz]
Sent: Thursday, December 12, 2019 6:36 PM
To: Jeff Chang <richtek.jeff.chang@gmail.com>; lgirdwood@gmail.com
Cc: broonie@kernel.org; tiwai@suse.com; matthias.bgg@gmail.com; alsa-devel@alsa-project.org; linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org; jeff_chang(張世佳) <jeff_chang@richtek.com>
Subject: Re: [PATCH] ASoC: Add MediaTek MT6660 Speaker Amp Driver

Dne 12. 12. 19 v 10:12 Jeff Chang napsal(a):
> +static const struct snd_kcontrol_new mt6660_component_snd_controls[] = {
> +SOC_SINGLE_EXT_TLV("Digital Volume", MT6660_REG_VOL_CTRL, 0, 255,
> +   1, snd_soc_get_volsw, mt6660_component_put_volsw,
> +   vol_ctl_tlv),
> +SOC_SINGLE_EXT("WDT Switch", MT6660_REG_WDT_CTRL, 7, 1, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("Hard_Clip Switch", MT6660_REG_HCLIP_CTRL, 8, 1, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("Clip Switch", MT6660_REG_SPS_CTRL, 0, 1, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("BoostMode", MT6660_REG_BST_CTRL, 0, 3, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("DRE Switch", MT6660_REG_DRE_CTRL, 0, 1, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("DC_Protect Switch",
> +MT6660_REG_DC_PROTECT_CTRL, 3, 1, 0,
> +snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("audio input selection", MT6660_REG_DATAO_SEL, 6, 3, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("Data Output Left Channel Selection",
> +       MT6660_REG_DATAO_SEL, 3, 7, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("Data Output Right Channel Selection",
> +       MT6660_REG_DATAO_SEL, 0, 7, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +/* for debug purpose */
> +SOC_SINGLE_EXT("HPF_AUD_IN Switch", MT6660_REG_HPF_CTRL, 0, 1, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("AUD_LOOP_BACK Switch", MT6660_REG_PATH_BYPASS, 4, 1, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("Mute Switch", MT6660_REG_SYSTEM_CTRL, 1, 1, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("Bypass CS Comp Switch", MT6660_REG_PATH_BYPASS, 2, 1, 0,
> +       snd_soc_get_volsw, mt6660_component_put_volsw),
> +SOC_SINGLE_EXT("T0_SEL", MT6660_REG_CALI_T0, 0, 7, 0,
> +       snd_soc_get_volsw, NULL),
> +SOC_SINGLE_EXT("Chip_Rev", SND_SOC_NOPM, 0, 16, 0,
> +       mt6660_component_get_volsw, NULL),

The control names looks really strange like always for the ASoC tree. We should talk about a standardization here. At least unify spaces, underscores and such characters and abbreviations.

Thanks,
Jaroslav

--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
************* Email Confidentiality Notice ********************

The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you!

  reply	other threads:[~2019-12-12 11:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12  9:12 [PATCH] ASoC: Add MediaTek MT6660 Speaker Amp Driver Jeff Chang
2019-12-12 10:36 ` Jaroslav Kysela
2019-12-12 11:05   ` jeff_chang(張世佳) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-20 10:15 Jeff Chang
2019-12-20 12:11 ` Mark Brown
2019-12-23  2:10   ` jeff_chang(張世佳)
2019-12-24 23:51     ` Mark Brown
2019-12-25  1:45       ` jeff_chang(張世佳)
2019-12-25 17:45         ` Mark Brown
2019-12-12 12:12 Jeff Chang
2019-12-12 14:53 ` Mark Brown
     [not found]   ` <b0f4c1afd1d341b49b87b7b5cda5ea4d@ex1.rt.l>
2019-12-13 11:32     ` Mark Brown
2019-12-12 11:08 Jeff Chang
2019-12-12 11:57 ` Matthias Brugger
2019-12-12 12:06 ` Mark Brown
2019-12-17 15:17 ` Greg KH
2019-12-12  8:29 [PATCH] ASoC: add " Jeff Chang
2019-12-12  8:52 ` Matthias Brugger
2019-12-12  6:58 Jeff Chang

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=33393c67cee243a59fb0043a276f4e4a@ex1.rt.l \
    --to=jeff_chang@richtek.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=perex@perex.cz \
    --cc=richtek.jeff.chang@gmail.com \
    --cc=tiwai@suse.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).