On 2024-02-26 12:09 PM, Takashi Iwai wrote:
On Fri, 23 Feb 2024 18:09:59 +0100,
Cezary Rojewski wrote:
On 2024-02-23 3:44 PM, Takashi Iwai wrote:
On Fri, 23 Feb 2024 12:46:24 +0100,
Cezary Rojewski wrote:
If i915 does not support given platform but the hardware i.e.: HDAudio
codec is still t
On Fri, 23 Feb 2024 18:09:59 +0100,
Cezary Rojewski wrote:
>
> On 2024-02-23 3:44 PM, Takashi Iwai wrote:
> > On Fri, 23 Feb 2024 12:46:24 +0100,
> > Cezary Rojewski wrote:
> >>
> >> If i915 does not support given platform but the hardware i.e.: HDAudio
> >> codec is still there, the codec-probin
On 2024-02-23 3:44 PM, Takashi Iwai wrote:
On Fri, 23 Feb 2024 12:46:24 +0100,
Cezary Rojewski wrote:
If i915 does not support given platform but the hardware i.e.: HDAudio
codec is still there, the codec-probing procedure will succeed for such
device but the follow up initialization will alway
On Fri, 23 Feb 2024 12:46:24 +0100,
Cezary Rojewski wrote:
>
> If i915 does not support given platform but the hardware i.e.: HDAudio
> codec is still there, the codec-probing procedure will succeed for such
> device but the follow up initialization will always end up with -ENODEV.
>
> While bus
If i915 does not support given platform but the hardware i.e.: HDAudio
codec is still there, the codec-probing procedure will succeed for such
device but the follow up initialization will always end up with -ENODEV.
While bus could filter out address '2' which Intel's HDMI/DP codecs
always enumera
