On Fri, Feb 26, 2021 at 10:27 PM Maxime Ripard <mripard@xxxxxxxxxx> wrote: > > Hi, > > On Mon, Feb 15, 2021 at 01:11:01AM +0530, Jagan Teki wrote: > > Use drm_panel_bridge to replace manual panel handling code. > > > > This simplifies the driver to allows all components in the > > display pipeline to be treated as bridges, paving the way > > to generic connector handling. > > > > Use drm_bridge_connector_init to create a connector for display > > pipelines that use drm_bridge. > > > > This allows splitting connector operations across multiple bridges > > when necessary, instead of having the last bridge in the chain > > creating the connector and handling all connector operations > > internally. > > > > Signed-off-by: Jagan Teki <jagan@xxxxxxxxxxxxxxxxxxxx> > > Most of the code removed in that patch was actually introduced earlier > which feels a bit weird. Is there a reason we can't do that one first, > and then introduce the bridge support? This patch adds new bridge API's which requires the driver has to support the bridge first. Jagan. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel