alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: bardliao@realtek.com
Cc: oder_chiou@realtek.com, alsa-devel@alsa-project.org,
	swarren@nvidia.com, swarren@wwwdotorg.org, lgirdwood@gmail.com,
	broonie@kernel.org, flove@realtek.com
Subject: Re: [PATCH] ASoC: rt5640: change widget sequence for depop
Date: Mon, 05 Aug 2013 19:19:32 +0200	[thread overview]
Message-ID: <51FFDEA4.2020606@metafoo.de> (raw)
In-Reply-To: <1375676343-13891-1-git-send-email-bardliao@realtek.com>

On 08/05/2013 06:19 AM, bardliao@realtek.com wrote:
> From: Bard Liao <bardliao@realtek.com>
> 
> Add mute/unmute control in widget event and modify the power on/off sequence to avoid pop noise.
> 
> Signed-off-by: Bard Liao <bardliao@realtek.com>
> ---
> Please ignore the previous patch.
> I have tested speaker and headphone playback on this patch.
> ---
>  sound/soc/codecs/rt5640.c | 389 +++++++++++++++++++++++++++++++++++++++-------
>  sound/soc/codecs/rt5640.h |  15 ++
>  2 files changed, 352 insertions(+), 52 deletions(-)
> 
> diff --git a/sound/soc/codecs/rt5640.c b/sound/soc/codecs/rt5640.c
> index 4db7314..cae3f46 100644
> --- a/sound/soc/codecs/rt5640.c
> +++ b/sound/soc/codecs/rt5640.c
> @@ -50,8 +50,6 @@ static const struct regmap_range_cfg rt5640_ranges[] = {
>  
>  static struct reg_default init_list[] = {
>  	{RT5640_PR_BASE + 0x3d,	0x3600},
> -	{RT5640_PR_BASE + 0x1c,	0x0D21},
> -	{RT5640_PR_BASE + 0x1b,	0x0000},
>  	{RT5640_PR_BASE + 0x12,	0x0aa8},
>  	{RT5640_PR_BASE + 0x14,	0x0aaa},
>  	{RT5640_PR_BASE + 0x20,	0x6110},
> @@ -378,21 +376,119 @@ static const SOC_ENUM_SINGLE_DECL(rt5640_if2_adc_enum, RT5640_DIG_INF_DATA,
>  static const char * const rt5640_clsd_spk_ratio[] = {"1.66x", "1.83x", "1.94x",
>  	"2x", "2.11x", "2.22x", "2.33x", "2.44x", "2.55x", "2.66x", "2.77x"};
>  
> +static const char * const rt5640_mute_mode[] = {"mute", "unmute"};
> +
> +static const SOC_ENUM_SINGLE_DECL(rt5640_hp_enum, 0, 0, rt5640_mute_mode);
> +static const SOC_ENUM_SINGLE_DECL(rt5640_spo_enum, 0, 0, rt5640_mute_mode);
> +

These enums seem to be unused. (And switches should be used for mutes and enums)

- Lars

  parent reply	other threads:[~2013-08-05 17:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05  4:19 [PATCH] ASoC: rt5640: change widget sequence for depop bardliao
2013-08-05 14:48 ` Mark Brown
2013-08-05 17:21   ` Lars-Peter Clausen
2013-08-05 17:58     ` Mark Brown
2013-08-06  8:07     ` [PATCH] ASoC: rt5640: change widget sequencefordepop Bard Liao
2013-08-06  8:45       ` Lars-Peter Clausen
2013-08-06  9:13         ` [PATCH] ASoC: rt5640: change widgetsequencefordepop Bard Liao
2013-08-06  9:35           ` Lars-Peter Clausen
2013-08-06 10:07             ` Bard Liao
2013-08-06 10:16               ` Lars-Peter Clausen
2013-08-06 11:04                 ` Bard Liao
2013-08-06 11:31                   ` Lars-Peter Clausen
2013-08-07  1:32                     ` Bard Liao
2013-08-07  5:40                     ` Bard Liao
2013-08-07  7:45                       ` Lars-Peter Clausen
2013-08-07  8:03                         ` Bard Liao
2013-08-07  8:26                           ` Lars-Peter Clausen
2013-08-07  8:31                             ` Bard Liao
2013-08-07  9:36                             ` Mark Brown
2013-08-07 10:47                               ` Lars-Peter Clausen
2013-08-07 13:05                                 ` Mark Brown
2013-08-09  9:05                                 ` Bard Liao
2013-08-09 13:37                                   ` Lars-Peter Clausen
2013-08-09 14:58                                     ` Mark Brown
2013-08-12  7:27                                       ` Bard Liao
2013-08-05 17:17 ` [PATCH] ASoC: rt5640: change widget sequence for depop Stephen Warren
2013-08-05 17:19 ` Lars-Peter Clausen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-19 12:18 bardliao
2013-08-19 17:29 ` Stephen Warren
2013-08-20  2:36   ` Bard Liao
2013-08-20 16:15     ` Stephen Warren
2013-08-21 19:56       ` Lars-Peter Clausen
2013-08-02  2:38 bardliao
2013-08-02 15:53 ` Stephen Warren
2013-08-05  3:34   ` Bard Liao

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=51FFDEA4.2020606@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=flove@realtek.com \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.org \
    /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).