From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Limonciello, Mario" <Mario.Limonciello@dell.com>,
Mark Brown <broonie@kernel.org>
Cc: "oder_chiou@realtek.com" <oder_chiou@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"Yuan, Perry" <Perry.Yuan@dell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tiwai@suse.com" <tiwai@suse.com>
Subject: Re: [PATCH] ASoC: rt715:add Mic Mute LED control support
Date: Tue, 3 Nov 2020 12:35:42 -0600 [thread overview]
Message-ID: <15ed949b-0313-168c-bfc5-3e71d9548e3f@linux.intel.com> (raw)
In-Reply-To: <DM6PR19MB26368B60076D049F009B75A3FA110@DM6PR19MB2636.namprd19.prod.outlook.com>
> I don't think it came through in the commit message, but I wanted to mention
> in the system that prompted this software does not control the LED. The LED
> is actually controlled by hardware, but has circuitry to delay the hardware
> mute until software mute is complete to avoid any "popping noises".
>
> This patch along with the platform/x86 patch:
> https://patchwork.kernel.org/project/platform-driver-x86/patch/20201103125542.8572-1-Perry_Yuan@Dell.com/
> complete that loop.
>
> The flow is:
> User presses mute key, dell-wmi receives event, passes to dell-privacy-wmi.
> This emits to userspace as KEY_MICMUTE. Userspace processes it and via UCM
> switches get toggled. The codec driver (or subsystem perhaps) will use LED
> trigger to notify to change LED. This gets picked up by dell-privacy-acpi.
>
> dell-privacy-acpi doesn't actually change LED, but notifies that SW mute was
> done.
>
> If none of that flow was used the LED and mute function still work, but there
> might be the popping noise.
Side note that the existing UCM config for RT715 does not do what I
suggested, it seems we are using an incorrect configuration for
CaptureSwitch and CaptureVolume:
CaptureSwitch "PGA5.0 5 Master Capture Switch"
CaptureVolume "PGA5.0 5 Master Capture Volume"
CaptureVolume "PGA5.0 5 Master Capture Volume"
That should be an RT715 control, not an SOF one. This was brought to our
attention this morning. Probably a copy-paste from the DMIC case, likely
needs to be changed for both RT715 and RT715-sdca cases.
https://github.com/thesofproject/linux/issues/2544#issuecomment-721231103
next prev parent reply other threads:[~2020-11-03 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 12:58 [PATCH] ASoC: rt715:add Mic Mute LED control support Perry Yuan
2020-11-03 13:12 ` Mark Brown
2020-11-03 16:13 ` Pierre-Louis Bossart
2020-11-03 17:51 ` Limonciello, Mario
2020-11-03 17:59 ` Mark Brown
2020-11-03 18:04 ` Limonciello, Mario
2020-11-03 18:31 ` Mark Brown
2020-11-03 19:01 ` Limonciello, Mario
2020-11-03 18:35 ` Pierre-Louis Bossart [this message]
2020-11-03 19:03 ` kernel test robot
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=15ed949b-0313-168c-bfc5-3e71d9548e3f@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=Mario.Limonciello@dell.com \
--cc=Perry.Yuan@dell.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.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).