From: Lucas Tanure <lucas.tanure@collabora.com>
To: David Rhodes <david.rhodes@cirrus.com>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
kernel@collabora.com, Lucas Tanure <lucas.tanure@collabora.com>
Subject: [PATCH 0/2] Add CS35L41 shared boost feature
Date: Tue, 7 Feb 2023 10:40:19 +0000 [thread overview]
Message-ID: <20230207104021.2842-1-lucas.tanure@collabora.com> (raw)
Valve's Steam Deck uses CS35L41 in shared boost mode,
where both speakers share the boost circuit.
Add this support in the shared lib, but for now,
shared boost is not supported in HDA systems as
would require BIOS changes.
Lucas Tanure (2):
ALSA: cs35l41: Add shared boost feature
Documentation: cs35l41: Shared boost properties
.../bindings/sound/cirrus,cs35l41.yaml | 11 +++-
include/sound/cs35l41.h | 10 +++-
sound/pci/hda/cs35l41_hda.c | 6 +-
sound/soc/codecs/cs35l41-lib.c | 56 ++++++++++++++++++-
sound/soc/codecs/cs35l41.c | 21 ++++++-
sound/soc/codecs/cs35l41.h | 1 +
6 files changed, 97 insertions(+), 8 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-07 10:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 10:40 Lucas Tanure [this message]
2023-02-07 10:40 ` [PATCH 1/2] ALSA: cs35l41: Add " Lucas Tanure
2023-02-07 11:48 ` Charles Keepax
2023-02-07 15:49 ` Lucas Tanure
2023-02-08 11:46 ` kernel test robot
2023-02-07 10:40 ` [PATCH 2/2] Documentation: cs35l41: Shared boost properties Lucas Tanure
2023-02-07 10:42 ` Krzysztof Kozlowski
2023-02-07 15:46 ` Lucas Tanure
2023-02-07 16:13 ` Krzysztof Kozlowski
2023-02-07 16:34 ` Lucas Tanure
2023-02-07 16:48 ` Krzysztof Kozlowski
2023-02-07 17:03 ` lucas.tanure
2023-02-08 10:23 ` Krzysztof Kozlowski
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=20230207104021.2842-1-lucas.tanure@collabora.com \
--to=lucas.tanure@collabora.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=david.rhodes@cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--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
all inboxes | Powered by JetHome®