All of lore.kernel.org
 help / color / mirror / Atom feed
From: Caesar Wang <wxt@rock-chips.com>
To: Anish Kumar <Anish.Kumar@maximintegrated.com>,
	Jianqun <xjq@rock-chips.com>,
	Matthew Mowdy <Matthew.Mowdy@maximintegrated.com>,
	"zhengxing@rock-chips.com" <zhengxing@rock-chips.com>,
	Nitin Mittal <nitin.mittal@maximintegrated.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"broonie@kernel.org" <broonie@kernel.org>
Subject: Re: [PATCH] ASoC: max98090: add shutdown callback for max98090
Date: Thu, 16 Apr 2015 10:19:30 +0800	[thread overview]
Message-ID: <552F1C32.8050407@rock-chips.com> (raw)
In-Reply-To: <B03A893ADFE80748942D13AFAF28451924E4BADE53@ITSVLEX06.it.maxim-ic.internal>

在 2015年04月16日 05:14, Anish Kumar 写道:
> 在 04/10/2015 03:38 AM, Anish Kumar 写道:
>>> To fix pop noise when shutdown,the pop noise during shutdown
>>> is the pmic cutoff power of codec without any notice.
>> Is the power turned off without any intimation to the codec driver?
>> Or is it physically removed? Can you describe the probelm
>> better?
>> When device is shutdown with playing music, the origin driver does nothing for shutdown operation,
>> as a result, pmic will cut off the power of codec IC, thus cause a pop noise from speaker and headphone.
>> So the patch added a shutdown callback for driver, enable volume smoothing and disable zero cross,
>> this is referenced from mic_input which does the samething before mic switch.
>> I'm very happy if some suggestion from maximintegrate . :-)
> Please let me know if the patch worked for you.

Yes, the patch can work for me.
We had tested on chromiumos.

>> +static void max98090_i2c_shutdown(struct i2c_client *i2c)
>> +{
>> +       struct max98090_priv *max98090 = dev_get_drvdata(&i2c->dev);
>> +
>> +       dev_info(&i2c->dev, "shut down device\n");
>> +
>> +       /* Enable volume smoothing, disable zero cross.  This will cause
>> +        * a quick 40ms ramp to mute on shutdown.
>> +        */
>> +       regmap_write(max98090->regmap,
>> +               M98090_REG_LEVEL_CONTROL, M98090_VSENN_MASK);
>> +       regmap_write(max98090->regmap,
>> +               M98090_REG_DEVICE_SHUTDOWN, 0x00);
>> +       msleep(40);
>> +}
>> +
>>
>>
>
>
>
>

-- 
**************************************************************************************
王晓腾    Caesar Wang
Product R&D Dept.III
Fuzhou Rockchip Electronics Co.Ltd
Addr:  NO.18 Building, A District, Fuzhou Software Park,Gulou District,Fuzhou, Fujian,China(Fuzhou Headquarters)
               21F,Malata Building,Kejizhongyi Avenue,Nanshan District,Shenzhen  (Shenzhen Office)
Tel:+86-591-83991906/07 - 8221
Mobile:+86 15059456742
E-mail : wxt@rock-chips.com
***************************************************************************************
***************************************************************************************
IMPORTANT NOTICE: This email is from Fuzhou Rockchip Electronics Co., Ltd .The contents of this email and any attachments may
contain information that is privileged, confidential and/or exempt from disclosure under applicable law and relevant NDA.
If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the
information is STRICTLY PROHIBITED. Please immediately contact the sender as soon as possible and destroy the material
in its entirety in any format. Thank you.
***************************************************************************************


_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2015-04-16  2:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2466.1428559383.807.alsa-devel@alsa-project.org>
     [not found] ` <CAK7N6vow0D8i6jQdjGbZ5L+VdyOtmSWSFdpyiE5JRH7SGtv=Dw@mail.gmail.com>
     [not found]   ` <B03A893ADFE80748942D13AFAF28451924E3198860@ITSVLEX06.it.maxim-ic.internal>
2015-04-10  0:46     ` [PATCH] ASoC: max98090: add shutdown callback for max98090 Jianqun
     [not found]       ` <B03A893ADFE80748942D13AFAF28451924E4BADE53@ITSVLEX06.it.maxim-ic.internal>
2015-04-16  2:19         ` Caesar Wang [this message]
     [not found]           ` <B03A893ADFE80748942D13AFAF28451924E4BADE55@ITSVLEX06.it.maxim-ic.internal>
2015-04-16  3:40             ` Caesar Wang
     [not found]               ` <B03A893ADFE80748942D13AFAF28451924E4BADE57@ITSVLEX06.it.maxim-ic.internal>
2015-04-17  7:22                 ` Caesar Wang
2015-04-08  8:52 [PATCH 0/1] " Caesar Wang
     [not found] ` <1428483128-23498-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-04-08  8:52   ` [PATCH] " Caesar Wang
2015-04-08  8:52     ` Caesar Wang
2015-04-08  8:52     ` Caesar Wang
2015-04-08  9:25     ` Heiko Stübner
2015-04-08  9:25       ` Heiko Stübner
2015-04-08  9:25       ` Heiko Stübner
2015-04-08 10:14       ` Caesar Wang
2015-04-08 10:14         ` Caesar Wang
2015-04-08  9:50     ` Mark Brown
2015-04-08  9:50       ` Mark Brown
2015-04-08 10:15       ` Caesar Wang
2015-04-08 10:15         ` Caesar Wang

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=552F1C32.8050407@rock-chips.com \
    --to=wxt@rock-chips.com \
    --cc=Anish.Kumar@maximintegrated.com \
    --cc=Matthew.Mowdy@maximintegrated.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=nitin.mittal@maximintegrated.com \
    --cc=xjq@rock-chips.com \
    --cc=zhengxing@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.