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 for Android: free password hash cracker in your pocket

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

Message-ID: <b244708a-414e-1f56-61a0-7c183f8ff45e@opensource.cirrus.com>
Date:   Wed, 16 Aug 2023 18:09:52 +0100
From:   Richard Fitzgerald <rf@...nsource.cirrus.com>
To:     Mark Brown <broonie@...nel.org>
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 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@...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?

No. Nothing has been released with CS35L56.