From: David Rhodes <drhodes@opensource.cirrus.com>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
James Schulman <james.schulman@cirrus.com>,
David Rhodes <david.rhodes@cirrus.com>,
"Lucas Tanure" <tanureal@opensource.cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: <patches@opensource.cirrus.com>, <alsa-devel@alsa-project.org>,
<kernel@collabora.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: cs35l41: Add support for CLSA3541 ACPI device ID
Date: Thu, 23 Jun 2022 19:01:57 -0500 [thread overview]
Message-ID: <e85bad57-a2b5-1729-858d-19e3a2fa1245@opensource.cirrus.com> (raw)
In-Reply-To: <20220621213819.262537-1-cristian.ciocaltea@collabora.com>
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
next prev parent reply other threads:[~2022-06-24 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 21:38 [PATCH] ASoC: cs35l41: Add support for CLSA3541 ACPI device ID Cristian Ciocaltea
2022-06-24 0:01 ` David Rhodes [this message]
2022-06-24 14:35 ` Mark Brown
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=e85bad57-a2b5-1729-858d-19e3a2fa1245@opensource.cirrus.com \
--to=drhodes@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=david.rhodes@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=kernel@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=tanureal@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).