linux-kernel - Re: [PATCH] ALSA: hda: intel-dsp-config: Fix Azulle Access 4 quirk detection

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: Fri, 21 Jun 2024 10:35:31 +0200
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Amadeusz Sławiński
 <amadeuszx.slawinski@...ux.intel.com>, Allen Ballway <ballway@...omium.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
 Brady Norander <bradynorander@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
 Takashi Iwai <tiwai@...e.com>,
 Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
 Mark Brown <broonie@...nel.org>, linux-sound@...r.kernel.org,
 Mark Hasemeyer <markhas@...omium.org>,
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 Cezary Rojewski <cezary.rojewski@...el.com>
Subject: Re: [PATCH] ALSA: hda: intel-dsp-config: Fix Azulle Access 4 quirk
 detection

On 6/21/24 08:15, Amadeusz Sławiński wrote:
> On 6/20/2024 9:27 PM, Allen Ballway wrote:
>> I filed a bug and after sharing the requested information it looks
>> like this device won't work on SOF without vendor support. Given this,
>> would the original patch returning this device to using HDAudio be
>> reasonable, or is there an preferred alternative to force this device
>> into using HDAudio?
>>
> 
> And can you share link to the issue on mailing list, so someone reading
> this thread in the future doesn't have to guess where it is? ;)

https://github.com/thesofproject/linux/issues/4981

I don't know what to do with this configuration.
We added a quirk to force SOF to be used for ES8336 devices. It worked
for some, but not for others. Now we have quite a few ES8336-based
platforms that are broken with zero support from the vendor, with
obscure I2C/GPIO/clk issues.
Are we going to tag each one of them and say 'not supported, use HDMI only'?
That's pushing a bit the notion of quirk...It would generate an endless
stream of patches. The alternative is to do nothing and ask that those
platforms revert to HDMI audio only with a kernel parameter. That latter
alternative has my vote.