From: Stefan Binding <sbinding@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>,
Uday M Bhat <uday.m.bhat@intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>,
Stefan Binding <sbinding@opensource.cirrus.com>
Subject: [PATCH v1 0/3] ASoC: cs42l42: Fix handling of hard reset
Date: Wed, 13 Sep 2023 16:00:09 +0100 [thread overview]
Message-ID: <20230913150012.604775-1-sbinding@opensource.cirrus.com> (raw)
These patches fix 3 problems with hard reset:
1. Ensure a minimum reset pulse width
2. Deal with ACPI overriding the requested default GPIO state
3. Avoid a race condition when hard-resetting a SoundWire peripheral
that is already enumerated
Richard Fitzgerald (3):
ASoC: cs42l42: Ensure a reset pulse meets minimum pulse width.
ASoC: cs42l42: Don't rely on GPIOD_OUT_LOW to set RESET initially low
ASoC: cs42l42: Avoid stale SoundWire ATTACH after hard reset
sound/soc/codecs/cs42l42-sdw.c | 20 ++++++++++++++++++++
sound/soc/codecs/cs42l42.c | 21 ++++++++++++++++++++-
sound/soc/codecs/cs42l42.h | 1 +
3 files changed, 41 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2023-09-13 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 15:00 Stefan Binding [this message]
2023-09-13 15:00 ` [PATCH v1 1/3] ASoC: cs42l42: Ensure a reset pulse meets minimum pulse width Stefan Binding
2023-09-13 15:00 ` [PATCH v1 2/3] ASoC: cs42l42: Don't rely on GPIOD_OUT_LOW to set RESET initially low Stefan Binding
2023-09-13 15:00 ` [PATCH v1 3/3] ASoC: cs42l42: Avoid stale SoundWire ATTACH after hard reset Stefan Binding
2023-09-14 11:19 ` [PATCH v1 0/3] ASoC: cs42l42: Fix handling of " 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=20230913150012.604775-1-sbinding@opensource.cirrus.com \
--to=sbinding@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=uday.m.bhat@intel.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