Hi, On 14/12/2025 13:14, Linus Walleij wrote: > On Fri, Dec 12, 2025 at 3:21 PM Tomi Valkeinen > <[email protected]> wrote: >> On 05/12/2025 11:51, Tomi Valkeinen wrote: >>> Changing the enable/disable sequence in commit c9b1150a68d9 >>> ("drm/atomic-helper: Re-order bridge chain pre-enable and post-disable") >>> has caused regressions on multiple platforms: R-Car, MCDE, Rockchip. >>> >>> This is an alternate series to Linus' series: >>> >>> https://lore.kernel.org/all/20251202-mcde-drm-regression-thirdfix-v6-0-f1bffd4ec0fa%40kernel.org/ >>> >>> This series first reverts the original commit and reverts a fix for >>> mediatek which is no longer needed. It then exposes helper functions >>> from DRM core, and finally implements the new sequence only in the tidss >>> driver. >>> >>> There is one more fix in upstream for the original commit, commit >>> 5d91394f2361 ("drm/exynos: fimd: Guard display clock control with >>> runtime PM calls"), but I have not reverted that one as it looks like a >>> valid patch in its own. >>> >>> I added Cc stable v6.17+ to all patches, but I didn't add Fixes tags, as >>> I wasn't sure what should they point to. But I could perhaps add Fixes: >>> <original commit> to all of these. > >> There has been no comments, so I assume this is the way to go. >> >> Should we merge this series as a fix for 6.18 rcs? > > Too late now, so let's merge it as a fix for v6.19 rcs! Ah, right. Indeed, I meant v6.19 rcs.
Tomi
