linux-kernel - Re: [PATCH 2/2] ASoC: cs35l56: Read firmware uuid from a device property instead of

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 16 Aug 2023 18:03:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com,
        Maciej Strozek <mstrozek@...nsource.cirrus.com>
Subject: Re: [PATCH 2/2] ASoC: cs35l56: Read firmware uuid from a device
 property instead of _SUB

On Wed, Aug 16, 2023 at 05:49:06PM +0100, Richard Fitzgerald wrote:
> From: Maciej Strozek <mstrozek@...nsource.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?

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)