Hi Derek. On Wed, Jul 24, 2019 at 03:15:19PM -0700, dbasehore . wrote: > Hi Sam, thanks for pointing out the potential conflict. > > On Tue, Jul 23, 2019 at 2:19 AM Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > > > > Hi Derek. > > > > On Tue, Jul 09, 2019 at 07:16:57PM -0700, Derek Basehore wrote: > > > Devicetree systems can set panel orientation via a panel binding, but > > > there's no way, as is, to propagate this setting to the connector, > > > where the property need to be added. > > > To address this, this patch sets orientation, as well as other fixed > > > values for the panel, in the drm_panel_attach function. These values > > > are stored from probe in the drm_panel struct. > > > > This approch seems to conflict with work done by Laurent where the > > ownership/creation of the connector will be moved to the display controller. > > > > If I understand it correct then there should not be a 1:1 relation > > between a panel and a connector anymore. > > > Can you point me to this work? Please take a look at the series with subject: "[PATCH 00/60] drm/omap: Replace custom display drivers with drm_bridge and drm_panel" Link: https://patchwork.kernel.org/cover/11034175/ Laurent has done a great job explaining the background, If you look into the patched you will see the idea is that a drm_panel no longer get attached to a drm_controller - it will be an argument to get_modes(). Sam _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
