On Thu, Sep 03, 2026 at 10:11:05AM +0200, Luca Ceresoli wrote: > Work is in progress for every drm_panel to embed a drm_bridge, which will > make the drm_panel code (currently in the drm module) depend on the > drm_kms_helper module. > > However that would create a dependency loop: > > * the panel_bridge code in bridge/panel.c [drm_kms_helper module] > already depends on the drm_panel.c code (it manipulates a drm_panel) > * additionally, the drm_panel.c code, in order to create a drm_bridge, > will depend on the helpers in drm_atomic_helper and drm_probe_helper > code [drm_kms_helper module] > > Prevent the loop by moving the panel bridge out to its own module. > > Signed-off-by: Luca Ceresoli <[email protected]>
Again, in the previous discussion, I suggested that you moved the drm_panel code into its own module. If you're doing everything at once, it will break, but the only source of breakage you're talking about here are introduced by *future* patches, not the current state. So, what prevented you *in this patch* from moving drm_panel into its own module? Maxime
signature.asc
Description: PGP signature
