From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Khalil <khalilst@gmail.com>, "Mark Brown" <broonie@kernel.org>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: patches@opensource.cirrus.com, Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-spi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Khalil <khalil@rentman.nl>
Subject: Re: [PATCH v3 0/3] Fix CS35L56 amplifier on Intel LPSS SPI with broken ACPI cs-gpios
Date: Thu, 3 Sep 2026 10:21:03 +0100 [thread overview]
Message-ID: <dad5e839-4932-4ae3-86d8-a3c2f4ce07d7@opensource.cirrus.com> (raw)
In-Reply-To: <20260901192625.1497791-1-khalil@rentman.nl>
On 01/09/2026 8:26 pm, Khalil wrote:
> v3 of the patch series fixing dual CS35L56 amplifiers on HP laptops
> with Intel Lunar Lake and broken ACPI cs-gpios.
HP told us they have a BIOS with the cs-gpios fixed, and they can make
that available early if you post a support request for it.
Can you test that new BIOS? It would avoid the messy SPI workarounds.
next prev parent reply other threads:[~2026-09-03 9:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 19:26 Khalil
2026-09-01 19:26 ` [PATCH v3 1/3] spi: Preserve preset cs_gpiod in __spi_add_device() Khalil
2026-09-01 19:26 ` [PATCH v3 2/3] platform/x86: serial-multi-instantiate: Fix SPI chip select on platforms with incomplete ACPI cs-gpios Khalil
2026-09-16 21:24 ` Juan Jimenez Carrero
2026-09-01 19:26 ` [PATCH v3 3/3] spi: pxa2xx: Handle clock gating for GPIO chip select devices Khalil
2026-09-16 21:24 ` Juan Jimenez Carrero
2026-09-03 9:21 ` Richard Fitzgerald [this message]
2026-09-11 9:10 ` [PATCH v3 0/3] Fix CS35L56 amplifier on Intel LPSS SPI with broken ACPI cs-gpios Juan Jimenez Carrero
2026-09-16 21:23 ` Juan Jimenez Carrero
2026-09-17 13:42 ` Richard Fitzgerald
2026-09-18 11:52 ` Juan Jimenez Carrero
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=dad5e839-4932-4ae3-86d8-a3c2f4ce07d7@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=hansg@kernel.org \
--cc=haojian.zhuang@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=khalil@rentman.nl \
--cc=khalilst@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
/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®