* 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 [not found] ` <86e2d0f9-5c25-4cce-b4a8-68fb569f987d@collabora.com> @ 2026-02-17 8:18 ` Thorsten Leemhuis 2026-02-17 10:32 ` Greg KH 0 siblings, 1 reply; 2+ messages in thread From: Thorsten Leemhuis @ 2026-02-17 8:18 UTC (permalink / raw) To: Greg KH, stable@vger.kernel.org, Sasha Levin Cc: Evans Jahja, Matthias Brugger, linux-mediatek, linux-kernel, regressions, Otto Pflüger, Denis Gessert, AngeloGioacchino Del Regno On 2/16/26 11:46, AngeloGioacchino Del Regno wrote: > Il 13/02/26 10:27, Thorsten Leemhuis ha scritto: >> 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. >>> 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. > Yes, please, that'd be great. Hi stable team! Could you please pick up be0b304eeb8c5f ("arm64: dts: mediatek: mt8183: Add missing endpoint IDs to display graph") [merged v6.19-post, committed by Angelo, who ACKed this request; see quote above] for 6.18.y and 6.19.y? It fixes a regression in e72d63fa0563 ("arm64: dts: mediatek: mt8183: Migrate to display controller OF graph"). tia! Ciao, Thorsten >>>> Am Fr., 6. Feb. 2026 um 15:55 Uhr schrieb Thorsten Leemhuis >>>> <regressions@leemhuis.info>: >>>>> >>>>> 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@collabora.com> >>>>>> 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@abscue.de/ >>>>> >>>>> 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 >>> >>> >>> >> > > > ^ permalink raw reply [flat|nested] 2+ messages in thread
* 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 2026-02-17 8:18 ` [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 Thorsten Leemhuis @ 2026-02-17 10:32 ` Greg KH 0 siblings, 0 replies; 2+ messages in thread From: Greg KH @ 2026-02-17 10:32 UTC (permalink / raw) To: Thorsten Leemhuis Cc: stable@vger.kernel.org, Sasha Levin, Evans Jahja, Matthias Brugger, linux-mediatek, linux-kernel, regressions, Otto Pflüger, Denis Gessert, AngeloGioacchino Del Regno On Tue, Feb 17, 2026 at 09:18:00AM +0100, Thorsten Leemhuis wrote: > On 2/16/26 11:46, AngeloGioacchino Del Regno wrote: > > Il 13/02/26 10:27, Thorsten Leemhuis ha scritto: > >> 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. > >>> 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. > > Yes, please, that'd be great. > > Hi stable team! Could you please pick up be0b304eeb8c5f ("arm64: dts: > mediatek: mt8183: Add missing endpoint IDs to display graph") [merged > v6.19-post, committed by Angelo, who ACKed this request; see quote > above] for 6.18.y and 6.19.y? It fixes a regression in e72d63fa0563 > ("arm64: dts: mediatek: mt8183: Migrate to display controller OF > graph"). tia! Ciao, Thorsten Now queued up, thanks. greg k-h ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-02-17 10:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAFLVeg9hwH3PbKu5rPWZWqq6yz5mRRoB9oqxDkxNRdEDLGbVBw@mail.gmail.com>
[not found] ` <CAFLVeg_soeYV4tOYKMo6TMYOtuWWU4TFCjUTxUrVEyGcRwMz7A@mail.gmail.com>
[not found] ` <df6fcd73-fe0a-42fc-97ce-7e458c340553@leemhuis.info>
[not found] ` <CAFLVeg-qeWu4ntgyqotsgjogPEyhqrMGG=UDWuZe+-D3K8YPTA@mail.gmail.com>
[not found] ` <908f3c03-a8b0-4535-9cfa-294c6ade8152@collabora.com>
[not found] ` <96e7f0fc-65f4-4613-b556-3a2d869dabb4@leemhuis.info>
[not found] ` <86e2d0f9-5c25-4cce-b4a8-68fb569f987d@collabora.com>
2026-02-17 8:18 ` [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 Thorsten Leemhuis
2026-02-17 10:32 ` Greg KH
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox