From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: broonie@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: [PATCH 0/3] ASoC: cs35l56: More support for new Dell laptops
Date: Thu, 5 Feb 2026 16:48:35 +0000 [thread overview]
Message-ID: <20260205164838.1611295-1-rf@opensource.cirrus.com> (raw)
Some new Dell models use spare pins on the amp as a binary integer
value to indicate the speaker type. The driver must use this to
select the correct firmware files for the hardware.
Patch #1 is the new support.
The other patches are for KUnit testing.
Richard Fitzgerald (3):
ASoC: cs35l56: Support for reading speaker ID from on-chip GPIOs
ASoC: cs35l56-shared: KUnit tests for onchip speaker ID gpios
ASoC: cs35l56: KUnit tests for parsing and using onchip GPIOs
include/sound/cs35l56.h | 37 ++
sound/soc/codecs/Kconfig | 14 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/cs35l56-shared-test.c | 680 +++++++++++++++++++++++++
sound/soc/codecs/cs35l56-shared.c | 172 +++++++
sound/soc/codecs/cs35l56-test.c | 273 ++++++++++
sound/soc/codecs/cs35l56.c | 141 ++++-
sound/soc/codecs/cs35l56.h | 2 +
8 files changed, 1317 insertions(+), 4 deletions(-)
create mode 100644 sound/soc/codecs/cs35l56-shared-test.c
--
2.47.3
next reply other threads:[~2026-02-05 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 16:48 Richard Fitzgerald [this message]
2026-02-05 16:48 ` [PATCH 1/3] ASoC: cs35l56: Support for reading speaker ID from on-chip GPIOs Richard Fitzgerald
2026-02-05 16:48 ` [PATCH 2/3] ASoC: cs35l56-shared: KUnit tests for onchip speaker ID gpios Richard Fitzgerald
2026-02-05 16:48 ` [PATCH 3/3] ASoC: cs35l56: KUnit tests for parsing and using onchip GPIOs Richard Fitzgerald
2026-02-06 0:28 ` [PATCH 0/3] ASoC: cs35l56: More support for new Dell laptops 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=20260205164838.1611295-1-rf@opensource.cirrus.com \
--to=rf@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