From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>,
Maciej Strozek <mstrozek@opensource.cirrus.com>
Subject: Re: [PATCH 2/2] ASoC: cs35l56: Read firmware uuid from a device property instead of _SUB
Date: Wed, 16 Aug 2023 18:09:52 +0100 [thread overview]
Message-ID: <b244708a-414e-1f56-61a0-7c183f8ff45e@opensource.cirrus.com> (raw)
In-Reply-To: <c3e42efc-9ddc-4788-85f7-cfa350d75d43@sirena.org.uk>
On 16/8/23 18:03, Mark Brown wrote:
> On Wed, Aug 16, 2023 at 05:49:06PM +0100, Richard Fitzgerald wrote:
>> From: Maciej Strozek <mstrozek@opensource.cirrus.com>
>>
>> Use a device property "cirrus,firmware-uid" to get the unique firmware
>> identifier instead of using ACPI _SUB.
>>
>> There will not usually be a _SUB in Soundwire nodes. The ACPI can use a
>> _DSD section for custom properties.
>>
>> There is also a need to support instantiating this driver using software
>> nodes. This is for systems where the CS35L56 is a back-end device and the
>> ACPI refers only to the front-end audio device - there will not be any ACPI
>> references to CS35L56.
>
> Are there any existing systems (or might there be given that the driver
> is in released kernels already) which rely on _SUB?
No. Nothing has been released with CS35L56.
next prev parent reply other threads:[~2023-08-16 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 16:49 [PATCH 0/2] ASoC: cs35l56: Update ACPI HID and property Richard Fitzgerald
2023-08-16 16:49 ` [PATCH 1/2] ASoC: cs35l56: Add an ACPI match table Richard Fitzgerald
2023-08-16 16:49 ` [PATCH 2/2] ASoC: cs35l56: Read firmware uuid from a device property instead of _SUB Richard Fitzgerald
2023-08-16 17:03 ` Mark Brown
2023-08-16 17:09 ` Richard Fitzgerald [this message]
2023-08-16 17:23 ` Mark Brown
2023-08-17 22:36 ` [PATCH 0/2] ASoC: cs35l56: Update ACPI HID and property 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=b244708a-414e-1f56-61a0-7c183f8ff45e@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mstrozek@opensource.cirrus.com \
--cc=patches@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®