Hi Tomi, On Tue, Nov 17, 2026 at 05:17:42PM +0200, Tomi Valkeinen wrote: > On 06/11/2026 15:14, Maxime Ripard wrote: > > Here's a series that implement what i915 calls "fastboot", ie, > > initializing the initial KMS state from the hardware state at boot, to > > skip the first modeset if the firmware already set up the display. > > > > This series creates the infrastructure in KMS to create that state by > > relying on driver specific hooks. It also implements some infrastructure > > to check during non-blocking commits that the readout helpers work > > properly by reading out the state that was just committed and comparing > > it to what was supposed to be committed. > > > > This relies on another set of driver hooks to compare the entities > > states, with helpers providing the default implementation. > > > > It then implements the readout support in the TIDSS driver, and was > > tested with the SK-AM62 board. This board in particular is pretty > > interesting, since it relies on an DPI to HDMI bridge, and uses the > > drm_bridge_connector infrastructure. > > > > So the readout works with the current state of the art on embedded-ish > > platforms. > > > > Unlike the earlier RFCs, it now works fine: the state is picked up > > properly, doesn't trigger a modeset if what was programmed is the one > > the first modeset tries to pick as well, will switch properly if it > > isn't, etc. > Sorry for taking so long with this, even if I said already a long time back > that I have additional patches for you. I now finally managed to get them > into some kind of order, and I have pushed a branch to: > > git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git > ti/boot-splash-v8.5 > > It's based on today's drm-misc-next, with the following posted series on > top: > > - [PATCH RESEND 00/83] drm: Switch drivers to > drm_mode_config_create_initial_state > - [PATCH v8 00/39] drm: Implement state readout support > > However, from the SRO series, I dropped all the tidss patches. It was > getting so difficult to make my changes at changes on top, so I decided to > just make fresh clean ones. I've tried to keep authorship where applicable, > but I could have missed some. > > After the SRO series, I have a pile of patches on top. It starts with tidss > patches that are not quite SRO related, but fix things or change the > structure so that SRO gets easier to add: > > drm/tidss: Fix the plane staying disabled after a CRTC off and on > drm/tidss: Remove the unused 'is_enabled' > drm/tidss: Split requesting the interrupt from enabling it > drm/tidss: Split dispc_init_hw() into steps called from probe > drm/tidss: Reset the DSS after the probe steps that can defer > drm/tidss: Keep the DSS enabled from the reset to the end of probe > > Then I have some non-tidss patches. Some of these, I think, you already had > in a local tree or were posted in the tilcdc series. The panel side is > lacking, so I labeled those as hacks. I'm not quite sure how to correctly > implement that. > > drm/atomic_sro: Do not compare the plane zpos > drm/atomic_sro: Do not compare planes on an inactive CRTC > drm/atomic_sro: Add a device-level atomic_sro_install_state hook > drm/bridge: Add an atomic_sro_install_state hook for bridges > HACK: drm/bridge: panel: Prepare and enable the panel when installing the > state > HACK: drm/panel: simple: Set the sync polarities of Microtips MF-101HIEBCAF0 > > Then I have tidss SRO patches. Many of these are based on yours, but there > are plenty of details that have changed, fixing issues I found when testing > different combinations. > > drm/tidss: Implement .hw_reset hook > drm/tidss: Reset the DISPC at runtime suspend if probe did not reset it > drm/tidss: dispc: Add helpers for the state readout > drm/tidss: encoder: Implement atomic_sro_get_current_crtc > drm/tidss: oldi: Implement hw readout support > drm/tidss: dispc: Keep DPIENABLE of an active VP in dispc_vp_init() > drm/tidss: crtc: Implement hw readout support > drm/tidss: plane: Implement hw readout support > drm/tidss: encoder: Implement bridge state readout > drm/tidss: Implement hw readout support > > I have been testing these with AM62-SK, HDMI and OLDI, with all the > different combinations I've come up with. However, I realized just today > that the bootloader could still do things a bit differently, which wouldn't > work with the current patches. I decided to ignore that for now. > > I also need to test all this on other TI boards, without SRO, or perhaps > adding SRO if it's easy-ish. > > So... Again, thanks Maxime for the great work you've done here, I really > like this series. It's annoyingly complicated to get to work reliably, > though, but maybe we'll get there =). With all my tests now working, I'll > try to find the time to actually review the series.
Thanks a lot for your work too. I share the frustration because I don't have access to all the hardware variants :) I've just sent a new version that fixes a fair number of issues you were facing and creates an install_state hook you needed. I've also split the tidss readout changes to make it easier to review / modify, but then your branch diverged a fair bit from mine and I didn't have a good enough understanding of the tidss driver to reconcile most of the tidss changes you made. The core should have everything you need though, so hopefully we can merge the core changes if sashiko doesn't anything of importance, and merge the tidss changes once we have something reliable. Maxime
signature.asc
Description: PGP signature
