From: Stefan Binding <sbinding@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com,
Stefan Binding <sbinding@opensource.cirrus.com>
Subject: [PATCH v2 0/3] ASoC: cs35l56: Fixes for CS35L63 for production silicon
Date: Wed, 20 Aug 2025 13:50:33 +0100 [thread overview]
Message-ID: <20250820125045.117740-1-sbinding@opensource.cirrus.com> (raw)
Production silicon for CS36L63 has some small differences compared to
pre-production silicon. This requires small fixes in driver.
Update firmware addresses, tuning algorithm IDs and remove soundwire
clock workaround as no longer necessary.
No product was ever released using pre-production silicon, therefore
there is no need to keep support for it.
Changes since V1:
- Split V1 patch into 3 separate patches
Richard Fitzgerald (1):
ASoC: cs35l56: Handle new algorithms IDs for CS35L63
Stefan Binding (2):
ASoC: cs35l56: Update Firmware Addresses for CS35L63 for production
silicon
ASoC: cs35l56: Remove SoundWire Clock Divider workaround for CS35L63
include/sound/cs35l56.h | 5 ++-
sound/soc/codecs/cs35l56-sdw.c | 69 -------------------------------
sound/soc/codecs/cs35l56-shared.c | 29 +++++++++++--
sound/soc/codecs/cs35l56.c | 2 +-
sound/soc/codecs/cs35l56.h | 3 --
5 files changed, 30 insertions(+), 78 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-20 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 12:50 Stefan Binding [this message]
2025-08-20 12:50 ` [PATCH v2 1/3] ASoC: cs35l56: Update Firmware Addresses " Stefan Binding
2025-08-20 12:50 ` [PATCH v2 2/3] ASoC: cs35l56: Handle new algorithms IDs for CS35L63 Stefan Binding
2025-08-20 12:50 ` [PATCH v2 3/3] ASoC: cs35l56: Remove SoundWire Clock Divider workaround " Stefan Binding
2025-08-20 14:08 ` Mark Brown
2025-08-20 22:17 ` [PATCH v2 0/3] ASoC: cs35l56: Fixes for CS35L63 for production silicon 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=20250820125045.117740-1-sbinding@opensource.cirrus.com \
--to=sbinding@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@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
all inboxes | Powered by JetHome®