Re: [REGRESSION] mt8183-kukui: dts: changes in dts caused display to no longer initialize - Was: Re: mt8183-kukui: drm/mediatek: dts: Invalid display hw pipeline when probing mediatek-drm
From: Thorsten Leemhuis
Date: Fri Feb 13 2026 - 04:28:46 EST
On 2/9/26 12:42, AngeloGioacchino Del Regno wrote:
> Il 06/02/26 17:58, Denis Gessert ha scritto:
>> Thanks for the quick response. I compiled 6.18.9 with this patch
>> (without reverting the previous commit) and it boots successfully.
>
> Well, I missed all those replies to this thread, and sent a redundant reply
> saying .. well, the same as Thorsten (hey, thanks for being faster than
> me!).
Happens. :-D
> Happy to see further confirmation that the patch that we both mentioned is
> actually fixing the issue.
The big question remains: Now that this landed in mainline, should we as
the stable team to pick this up for 6.18.y and 6.19.y to get it resolved
there quickly? They might pick it up on their own due to the Fixes tag,
but that is not guaranteed.
Ciao, Thorsten
>> Am Fr., 6. Feb. 2026 um 15:55 Uhr schrieb Thorsten Leemhuis
>> <regressions@xxxxxxxxxxxxx>:
>>>
>>> On 2/6/26 12:33, Denis Gessert wrote:
>>>>
>>>> I found this email chain while troubleshooting why my Levovo Duet
>>>> (with the MT8183 chip) would not boot using any 6.18.* kernel.
>>>>
>>>> I can confirm that on my device the current stable 6.18.8 does not
>>>> boot unless I revert the commit
>>>>
>>>> commit e72d63fa0563f8a6e98c10fed3a9ce74dc0536e6 (HEAD)
>>>> Author: AngeloGioacchino Del Regno
>>>> <angelogioacchino.delregno@xxxxxxxxxxxxx>
>>>> Date: Thu Jul 24 10:39:08 2025 +0200
>>>>
>>>> arm64: dts: mediatek: mt8183: Migrate to display controller OF
>>>> graph
>>>>
>>>> mentioned below. With the reverted commit the device boots as intended.
>>>
>>> There is a fix for it from Otto here that I guess should help
>>> https://lore.kernel.org/lkml/20260106-mt8183-display-graph-v2-1-
>>> e7e56054eef5@xxxxxxxxx/
>>>
>>> Side note: lacks a stable tag and maybe should have been merged this
>>> cycle instead of the next. But given that 6.19 is immanent it might be
>>> good if this could be backported to 6.19.y once it landed in mainline.
>>>
>>>> PS: Apologies for the potential double-mail.
>>> No worries, happens.
>>>
>>> Ciao, Thortsten
>
>
>