From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <tiwai@suse.com>
Cc: <alsa-devel@alsa-project.org>, <patches@opensource.cirrus.com>,
<linux-kernel@vger.kernel.org>,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: [PATCH 0/2] ALSA: hda: cs35l56: Handle speaker id GPIOs
Date: Mon, 18 Sep 2023 10:51:27 +0100 [thread overview]
Message-ID: <20230918095129.440-1-rf@opensource.cirrus.com> (raw)
Some manufacturers use multiple sources of speakers. Motherboard
GPIOs are set to indicate which type of speaker is fitted so that
the correct tunings can be loaded. Patch #1 adds support for this
and patch #2 adds a KUnit test for the new code.
Richard Fitzgerald (2):
ALSA: hda: cs35l56: Add support for speaker id
ALSA: hda: cirrus_scodec: Add KUnit test
MAINTAINERS | 1 +
sound/pci/hda/Kconfig | 17 ++
sound/pci/hda/Makefile | 4 +
sound/pci/hda/cirrus_scodec.c | 73 ++++++
sound/pci/hda/cirrus_scodec.h | 13 +
sound/pci/hda/cirrus_scodec_test.c | 370 +++++++++++++++++++++++++++++
sound/pci/hda/cs35l56_hda.c | 24 +-
7 files changed, 501 insertions(+), 1 deletion(-)
create mode 100644 sound/pci/hda/cirrus_scodec.c
create mode 100644 sound/pci/hda/cirrus_scodec.h
create mode 100644 sound/pci/hda/cirrus_scodec_test.c
--
2.30.2
next reply other threads:[~2023-09-18 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 9:51 Richard Fitzgerald [this message]
2023-09-18 9:51 ` [PATCH 1/2] ALSA: hda: cs35l56: Add support for speaker id Richard Fitzgerald
2023-09-18 9:51 ` [PATCH 2/2] ALSA: hda: cirrus_scodec: Add KUnit test Richard Fitzgerald
2023-09-19 20:44 ` Nick Desaulniers
2023-09-20 6:51 ` Takashi Iwai
2023-09-20 8:27 ` Richard Fitzgerald
2023-09-20 8:42 ` Takashi Iwai
2023-09-20 15:19 ` Andy Shevchenko
2023-09-18 15:50 ` [PATCH 0/2] ALSA: hda: cs35l56: Handle speaker id GPIOs Takashi Iwai
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=20230918095129.440-1-rf@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).