From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <broonie@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: [PATCH v2 0/3] ASOC: cs42l42: Add support for system suspend
Date: Fri, 21 Jan 2022 12:04:09 +0000 [thread overview]
Message-ID: <20220121120412.672284-1-rf@opensource.cirrus.com> (raw)
Add system suspend and resume handlers so that the cs42l42 is cleanly
put into power-off state during system suspend and the registers are
restored in resume.
The first two patches separate out two small changes that can stand
alone and are needed to enable the system suspend implementation:
1) Don't rely on there being a jack unplug IRQ before a plug IRQ.
There won't be if the unplug and plug happened while in system suspend.
2) Put a mutex around the entire IRQ handling so that the suspend can
ensure the last run of the IRQ handler has completed before it powers
down.
Changes since V1:
- Hold irq_lock mutex while restoring registers
Richard Fitzgerald (3):
ASoC: cs42l42: Report full jack status when plug is detected
ASoC: cs42l42: Change jack_detect_mutex to a lock of all IRQ handling
ASoC: cs42l42: Handle system suspend
sound/soc/codecs/cs42l42.c | 166 ++++++++++++++++++++++++++++++++++++++++++---
sound/soc/codecs/cs42l42.h | 7 +-
2 files changed, 163 insertions(+), 10 deletions(-)
--
2.11.0
next reply other threads:[~2022-01-21 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 12:04 Richard Fitzgerald [this message]
2022-01-21 12:04 ` [PATCH v2 1/3] ASoC: cs42l42: Report full jack status when plug is detected Richard Fitzgerald
2022-01-21 12:04 ` [PATCH v2 2/3] ASoC: cs42l42: Change jack_detect_mutex to a lock of all IRQ handling Richard Fitzgerald
2022-01-21 12:04 ` [PATCH v2 3/3] ASoC: cs42l42: Handle system suspend Richard Fitzgerald
2022-01-25 10:20 ` [PATCH v2 0/3] ASOC: cs42l42: Add support for " Mark Brown
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=20220121120412.672284-1-rf@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.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
Powered by JetHome