From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: broonie@kernel.org, linux-sound@vger.kernel.org,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v2] spi: cs42l43: Workaround for wrong speaker ID on Dell XPS 13 DX13260
Date: Thu, 1 Oct 2026 11:17:28 +0100 [thread overview]
Message-ID: <ar4zOK/IDogYqa31@opensource.cirrus.com> (raw)
In-Reply-To: <20261001085830.4014291-1-rf@opensource.cirrus.com>
On Thu, Oct 01, 2026 at 09:58:30AM +0100, Richard Fitzgerald wrote:
> On Dell XPS 13 DX13260 create an acpi_gpio_mapping with exactly two
> GPIO entries to point at the two pins in the GpioIo(). Use this to
> read the speaker ID GPIOs.
>
> This fixes problems on Dell XPS 13 DX13260:
>
> - No speaker audio
> - The wrong firmware was loaded so the speaker protection did not match
> the speaker characteristics.
>
> The Dell XPS 13 DX13260 has two speaker ID GPIOs, to form a 2-bit ID. The
> ACPI GpioIo() has both pins but the Linux-specific spk-id-gpios property
> only has a mapping to the first pin. This meant that the speaker ID was
> wrong in most cases, and that would lead to the codec driver loading the
> wrong amp firmware, or not finding a firmware (as 0 is not a valid ID on
> this laptop).
>
> Assisted-by: Codex:gpt-6-sol
> Reported-by: Wiza Jalakasi <wjalakasi@gmail.com>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221956
> Tested-by: Wiza Jalakasi <wjalakasi@gmail.com>
> Fixes: f3c605147741e ("spi: cs42l43: Add GPIO speaker id support to the bridge configuration")
> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
> ---
Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
prev parent reply other threads:[~2026-10-01 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 8:58 Richard Fitzgerald
2026-10-01 10:17 ` Charles Keepax [this message]
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=ar4zOK/IDogYqa31@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@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®