[PATCH] ASoC: cs35l41: Add support for CLSA3541 ACPI device ID
Add support for the CLSA3541 ACPI device ID used on Valve's Steam Deck. The driver is fully compatible with the indicated hardware, hence no additional changes are required.
Signed-off-by: Cristian Ciocaltea cristian.ciocaltea@collabora.com --- sound/soc/codecs/cs35l41-spi.c | 1 + 1 file changed, 1 insertion(+)
diff --git a/sound/soc/codecs/cs35l41-spi.c b/sound/soc/codecs/cs35l41-spi.c index 9e19c946a66b..5c8bb24909eb 100644 --- a/sound/soc/codecs/cs35l41-spi.c +++ b/sound/soc/codecs/cs35l41-spi.c @@ -74,6 +74,7 @@ MODULE_DEVICE_TABLE(of, cs35l41_of_match); #ifdef CONFIG_ACPI static const struct acpi_device_id cs35l41_acpi_match[] = { { "CSC3541", 0 }, /* Cirrus Logic PnP ID + part ID */ + { "CLSA3541", 0 }, /* Cirrus Logic PnP ID + part ID */ {}, }; MODULE_DEVICE_TABLE(acpi, cs35l41_acpi_match); -- 2.36.1
On 6/21/22 16:38, Cristian Ciocaltea wrote:
Add support for the CLSA3541 ACPI device ID used on Valve's Steam Deck. The driver is fully compatible with the indicated hardware, hence no additional changes are required.
Signed-off-by: Cristian Ciocaltea cristian.ciocaltea@collabora.com
This is the ID for CS35L41 on the Steam Deck, which uses the CS35L41 ASoC driver and the acp5x machine driver. Cirrus is aware that this is not a compliant ID (Cirrus does not own vendor ID CLSA), but similarly to the Lenovo devices that use CLSA0100, the ACPI entries were created before the driver was upstreamed.
Acked-by: David Rhodes drhodes@opensource.cirrus.com
Thanks, David
On Wed, 22 Jun 2022 00:38:19 +0300, Cristian Ciocaltea wrote:
Add support for the CLSA3541 ACPI device ID used on Valve's Steam Deck. The driver is fully compatible with the indicated hardware, hence no additional changes are required.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: cs35l41: Add support for CLSA3541 ACPI device ID commit: 658e95953075ca781ef8712d0a3203e485888c7f
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks, Mark
participants (3)
-
Cristian Ciocaltea -
David Rhodes -
Mark Brown