From: Pascal Huerst <pascal.huerst@gmail.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Preferred way to keep mixer mute in sync with digital_mute callback
Date: Mon, 10 Oct 2016 17:34:56 +0200 [thread overview]
Message-ID: <bcca4c6a-e69a-28fa-1b35-ac4fb8eef8af@gmail.com> (raw)
Hey everyone,
I'm currently having an issue with cs4271. The codec plays back, even if
mute is activated in alsa mixer. This is caused by the digital_mute
callback, that does not care about the current mute status in alsa
mixer. As a user, I would expect, that if mute is set in alsa mixer, I
don't get any output if I play something back. (But probably I'm wrong?).
On the other hand, wm8350 codec uses a flag in the driver struct, that
stores the current state of mute in alsa mixer, which is taken into
consideration in the digital_mute callback. But to make this possible,
one can not just use:
SOC_*()
for example, but has to create a put-function using:
SOC_*_EXT()
only to get and store that flag. Is this really the way to go, or did I
miss something?
Thanks,
Pascal
reply other threads:[~2016-10-10 15:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bcca4c6a-e69a-28fa-1b35-ac4fb8eef8af@gmail.com \
--to=pascal.huerst@gmail.com \
--cc=alsa-devel@alsa-project.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).