[alsa-devel] [PATCH] ASoC: rt5640: change widgetsequencefordepop

[Bard Liao]

> -----Original Message-----
> From: Lars-Peter Clausen [mailto:lars at metafoo.de]
> Sent: Wednesday, August 07, 2013 4:27 PM
> To: Bard Liao
> Cc: Mark Brown; Oder Chiou; alsa-devel at alsa-project.org;
> swarren at nvidia.com; swarren at wwwdotorg.org; lgirdwood at gmail.com; Flove
> Subject: Re: [alsa-devel] [PATCH] ASoC: rt5640: change
> widgetsequencefordepop
> 
> On 08/07/2013 10:03 AM, Bard Liao wrote:
> >> -----Original Message-----
> >> From: Lars-Peter Clausen [mailto:lars at metafoo.de]
> >> Sent: Wednesday, August 07, 2013 3:45 PM
> >> To: Bard Liao
> >> Cc: Mark Brown; Oder Chiou; alsa-devel at alsa-project.org;
> >> swarren at nvidia.com; swarren at wwwdotorg.org; lgirdwood at gmail.com;
> Flove
> >> Subject: Re: [alsa-devel] [PATCH] ASoC: rt5640: change
> >> widgetsequencefordepop
> >>
> >> On 08/07/2013 07:40 AM, Bard Liao wrote:
> >>> Is there any way to run an event when power up/down a
> >> snd_soc_dapm_kcontrol type widgt?
> >>> Because we need to do something with mute/unmute headphone.
> >>> e.g.
> >>> rt5640_pmu_depop is what we need when unmute headphone.
> >>> We need to set something before and after set the hp mute bit.
> >>>
> >>> If there is an event to do that, it will be easier to implement that.
> >>
> >> You can setup a event for the SND_SOC_DAPM_SWITCH, but this will run
> >> after setting the mute bit and before clearing the mute bit.
> >
> > It seems not to be suitable for me.
> > For me, It is better to run before setting the mute bit and after clearing the
> mute bit, too.
> 
> That isn't really supported right now. If muting and unmuting the control is
> such a complex sequence maybe it is better to stay with you previous solution,
> without autodisable.

That's fine.
I will check with our HW engineer to see if there is a simple sequence for headphone muting and unmuting.

Thanks.

> 
> - Lars
> 
> 
> ------Please consider the environment before printing this e-mail.