From: Stefan Binding <sbinding@opensource.cirrus.com>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>,
Stefan Binding <sbinding@opensource.cirrus.com>
Subject: [PATCH v3 0/2] Support mute notifications for CS35L41 HDA
Date: Tue, 19 Sep 2023 15:22:38 +0100 [thread overview]
Message-ID: <20230919142240.467682-1-sbinding@opensource.cirrus.com> (raw)
Some systems use a special keyboard shortcut to mute speaker audio.
On systems using CS35L41 HDA which have this shortcut, add a
mechanism which uses ACPI notifications to determine when the
shortcut is pressed, and then mute the amps inside the driver.
Since this is not a normal mute mechanism, it does not go through
userspace. To allow userspace to be able to track this special
state, add an ALSA control which tracks the state of this forced
mute
Changes since v2:
- Fixed compile issue when CONFIG_ACPI is missing
Stefan Binding (1):
ALSA: hda: cs35l41: Add read-only ALSA control for forced mute
Vitaly Rodionov (1):
ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA
sound/pci/hda/cs35l41_hda.c | 132 ++++++++++++++++++++++++++++++----
sound/pci/hda/cs35l41_hda.h | 3 +
sound/pci/hda/hda_component.h | 4 ++
sound/pci/hda/patch_realtek.c | 85 +++++++++++++++++++++-
4 files changed, 210 insertions(+), 14 deletions(-)
--
2.34.1
next reply other threads:[~2023-09-19 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 14:22 Stefan Binding [this message]
2023-09-19 14:22 ` [PATCH v3 1/2] ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA Stefan Binding
2023-09-19 18:18 ` kernel test robot
2023-09-20 6:58 ` Takashi Iwai
2023-09-19 14:22 ` [PATCH v3 2/2] ALSA: hda: cs35l41: Add read-only ALSA control for forced mute Stefan Binding
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=20230919142240.467682-1-sbinding@opensource.cirrus.com \
--to=sbinding@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--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