From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Allen Ballway" <ballway@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
"Brady Norander" <bradynorander@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
"Mark Brown" <broonie@kernel.org>,
linux-sound@vger.kernel.org,
"Mark Hasemeyer" <markhas@chromium.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Cezary Rojewski" <cezary.rojewski@intel.com>
Subject: Re: [PATCH] ALSA: hda: intel-dsp-config: Fix Azulle Access 4 quirk detection
Date: Wed, 26 Jun 2024 15:30:35 +0200 [thread overview]
Message-ID: <437a6141-33e0-4075-be22-b2b364787b6a@linux.intel.com> (raw)
In-Reply-To: <7bbf1688-4dfd-4a6f-90f2-ee235027c701@roeck-us.net>
On 6/26/24 15:09, Guenter Roeck wrote:
> On 6/26/24 00:04, Pierre-Louis Bossart wrote:
>>
>>
>> On 6/25/24 23:37, Guenter Roeck wrote:
>>> On Fri, Jun 21, 2024 at 10:35:31AM +0200, Pierre-Louis Bossart wrote:
>>>>
>>>>
>>>> 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.
>>>>
>>>
>>> Given that this apparently does not work for many ES8336 devices,
>>> would it make more sense to disable SOF support for those by default
>>> and _enable_ them with a kernel parameter ?
>>
>> Some configurations work, so we would break them.
>>
>
> Yes, but for others it is a regression, so arguably the change to
> force-enable
> SOF caused a regression and should either be reverted or fixed such that
> all
> previously working configurations still work (even more so since fixing
> the problem one-by-one as affected systems are found is being rejected).
If you disable SOF, all you get with snd-hda-intel is HDMI outputs.
There is no alternative if you want local speakers, mic and jack
support, or extensions based on I2S.
Some of my Intel colleagues have an ES8336-based platform that works for
them, they successfully modified the sof_es8336 machine driver to add
HDMI support, so why would we disable a working config?
I would really err on the side of "if you contributed a working config,
or helped enable a working config, it will be maintained in the kernel".
next prev parent reply other threads:[~2024-06-26 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 21:28 [PATCH] ALSA: hda: intel-dsp-config: Fix Azulle Access 4 quirk detection Allen Ballway
2024-04-30 21:46 ` Pierre-Louis Bossart
2024-05-06 16:39 ` Allen Ballway
2024-05-06 18:02 ` Pierre-Louis Bossart
2024-06-20 19:27 ` Allen Ballway
2024-06-21 6:15 ` Amadeusz Sławiński
2024-06-21 8:35 ` Pierre-Louis Bossart
2024-06-25 21:37 ` Guenter Roeck
2024-06-26 7:04 ` Pierre-Louis Bossart
2024-06-26 13:09 ` Guenter Roeck
2024-06-26 13:30 ` Pierre-Louis Bossart [this message]
2024-06-26 13:37 ` Takashi Iwai
2024-06-26 14:09 ` Guenter Roeck
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=437a6141-33e0-4075-be22-b2b364787b6a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ballway@chromium.org \
--cc=bradynorander@gmail.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=markhas@chromium.org \
--cc=perex@perex.cz \
--cc=ranjani.sridharan@linux.intel.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