From: Takashi Iwai <tiwai@suse.de>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: tiwai@suse.com, anthony.won@canonical.com,
"Jaroslav Kysela" <perex@perex.cz>,
"Libin Yang" <libin.yang@intel.com>,
"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Kailang Yang" <kailang@realtek.com>,
"Hui Wang" <hui.wang@canonical.com>,
"Jian-Hong Pan" <jian-hong@endlessm.com>,
"Tomas Espeleta" <tomas.espeleta@gmail.com>,
"Thomas Hebb" <tommyhebb@gmail.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
alsa-devel@alsa-project.org (moderated list:SOUND),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH] ALSA: hda/realtek: Serialize setting GPIO LED
Date: Wed, 01 Jul 2020 08:46:26 +0200 [thread overview]
Message-ID: <s5hh7urg2bh.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200701052138.6378-1-kai.heng.feng@canonical.com>
On Wed, 01 Jul 2020 07:21:35 +0200,
Kai-Heng Feng wrote:
>
> If a system has two GPIO controlled LED, one for mute and another one
> for micmute, and both of them are on before system suspend, sometimes
> one of them won't be turned off by system suspend.
>
> The codec doesn't seem to be able to control multiple GPIO LEDs at the
> same time, so introduce a new mutex to serialize setting the LED, to
> prevent the issue from happening.
>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
> include/sound/hda_codec.h | 1 +
> sound/pci/hda/hda_codec.c | 1 +
> sound/pci/hda/patch_realtek.c | 3 +++
> 3 files changed, 5 insertions(+)
>
> diff --git a/include/sound/hda_codec.h b/include/sound/hda_codec.h
> index d16a4229209b..3a1792bbb7ac 100644
> --- a/include/sound/hda_codec.h
> +++ b/include/sound/hda_codec.h
> @@ -206,6 +206,7 @@ struct hda_codec {
>
> struct mutex spdif_mutex;
> struct mutex control_mutex;
> + struct mutex led_mutex;
Since it's only for Realtek codec, can it be better in alc_spec
instead?
thanks,
Takashi
next prev parent reply other threads:[~2020-07-01 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 5:21 Kai-Heng Feng
2020-07-01 6:46 ` Takashi Iwai [this message]
2020-07-01 8:00 ` Kai-Heng Feng
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=s5hh7urg2bh.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=anthony.won@canonical.com \
--cc=gustavo@embeddedor.com \
--cc=hui.wang@canonical.com \
--cc=jian-hong@endlessm.com \
--cc=kai.heng.feng@canonical.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kailang@realtek.com \
--cc=libin.yang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=tomas.espeleta@gmail.com \
--cc=tommyhebb@gmail.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
all inboxes | Powered by JetHome®