Hello,
On Mon, Feb 07, 2022 at 02:34:34PM -0800, Doug Anderson wrote:
> On Sun, Feb 6, 2022 at 7:44 AM Sam Ravnborg <s...@ravnborg.org> wrote:
> >
> > From: Rob Clark <robdcl...@chromium.org>
> >
> > Slightly awkward to fish out the display_info when we aren't creating
> > own connector. But I don't see an obvious better way.
> >
> > v3:
> > - Rebased and dropped the ti_sn_bridge_get_bpp() patch
> > as this was solved in a different way (Sam)
> >
> > v2:
> > - Remove error return with NO_CONNECTOR flag (Rob)
> >
> > Signed-off-by: Rob Clark <robdcl...@chromium.org>
> > Signed-off-by: Sam Ravnborg <s...@ravnborg.org>
> > Cc: Rob Clark <robdcl...@chromium.org>
> > Cc: Douglas Anderson <diand...@chromium.org>
> > Cc: Andrzej Hajda <a.ha...@samsung.com>
> > Cc: Neil Armstrong <narmstr...@baylibre.com>
> > Cc: Robert Foss <robert.f...@linaro.org>
> > Cc: Laurent Pinchart <laurent.pinch...@ideasonboard.com>
> > Cc: Jonas Karlman <jo...@kwiboo.se>
> > Cc: Jernej Skrabec <jernej.skra...@gmail.com>
> > ---
> > drivers/gpu/drm/bridge/ti-sn65dsi86.c | 20 +++++++++-----------
> > 1 file changed, 9 insertions(+), 11 deletions(-)
>
> This is fine by me assuming we can fix the previous patches.
>
> Reviewed-by: Douglas Anderson <diand...@chromium.org>
Likewise,
Reviewed-by: Laurent Pinchart <laurent.pinch...@ideasonboard.com>
> NOTE: to me, this isn't something to do _instead_ of my patch [1] but
> _in addition_ to it. ${SUBJECT} patch transitions us to a more modern
> approach of having the connector created elsewhere but doesn't remove
> the old fallback code. Might as well clean the fallback code up unless
> you think it's going to simply be deleted right away or something?
I don't really mind either way, but I of course would favour removal of
connector support as soon as practical :-)
> [1]
> https://lore.kernel.org/r/20220204161245.v2.1.I3ab26b7f197cc56c874246a43e57913e9c2c1028@changeid
--
Regards,
Laurent Pinchart
