[PATCH 1/2] drm/ bridge: tc358762: move bridge init to enable callback
Laurent Pinchart
laurent.pinchart at ideasonboard.com
Thu Dec 9 17:06:21 UTC 2021
Hi Dmitry,
(CC'ing Tomi)
On Thu, Dec 09, 2021 at 07:53:43PM +0300, Dmitry Baryshkov wrote:
> On Fri, 26 Nov 2021 at 14:56, Dave Stevenson wrote:
> > On Fri, 26 Nov 2021 at 00:32, Dmitry Baryshkov wrote:
> > >
> > > During the pre_enable time the previous bridge (e.g. DSI host) might be
> > > not initialized yet. Move the regulator enablement and bridge init to
> > > te enable callback (and consequently regulator disblement to disable).
> >
> > Except that in the enable callback the DSI host has video enabled too,
> > so the data lanes may be in HS mode too, and the bridge may not be
> > prepared to accept that during power on / initialisation. That means
> > you've got a race condition over how quickly the composition hardware
> > starts producing pixel data vs when this enable callback is called. I
> > suspect that is why we had [1] for the rare case when the race
> > condition failed.
> > There's also seems to be no guarantee that a host can do LP commands
> > between HS video packets (eg sunxi [2])
>
> I see.
>
> > This is the same issue that was being hacked around in [3], and is one
> > of the questions I'd raised back in July [4].
> > The DSI support is broken when it comes to accommodating
> > initialisation sequences, but in trying to ensure all possible
> > sequences can be accomodated, all currently proposed solutions have
> > been shot down.
> > Some platforms have worked around it by powering up the DSI host in
> > mode_set (dw-mipi-dsi),
>
> Looks like this approach is supported by panel-bridge, so I have
> proposed a similar change to the msm dsi driver. [5]
>
> > others have broken the bridge chain apart so
> > their pre_enable gets called first (exynos and currently vc4) except
> > that approach is broken for the atomic API.
> >
> > There is a need for some form of resolution, even if it is only
> > documenting the correct hack to implement in the DSI host driver.
> > Hacking bridge or panel drivers to try and workaround it seems wrong.
>
> Thank you for this lengthy explanation, background and pointers. This
> helped a lot.
>
> It really looks like we need a separate callback between pre-enable
> and enable (or before pre-enable, but that would break the 'clocks not
> enabled' constraint.
>
> Another option would be to move video mode enablement from bridge ops
> to dsi host interface, making the panel/bridge implicitly tell the
> host to switch from LP to HS mode.
Do you mean explicitly ?
> This way the bridge's enable() callback would start with the DSI host
> powered up, but not sending the video, so the DSI device can send
> setup commands. Then it'd enable the video/cmd mode on the DSI host
> and then make final adjustments (like enabling the backlight/etc, so
> that the video is visible/sent to the next item in a chain. WDYT?
This is how the omapdrm driver originally implemented support for
bridges (as custom omapdrm components, before it was ported to
drm_bridge), with an that allowed downstream components to explicitly
control the enable/disable sequence of upstream components. I'm
beginning to think it's a better model, but switching drm_bridge to that
is likely an impossible task. Keeping it specific to the DSI interface
could be a good middle-ground, although some DSI encoders may need to
propagate any control operation they receive from the downstream
component up to their upstream component (for instance instructing the
CRTC to enable video when the panel requests video to be enabled).
Still, it's probably worth being investigated.
I can't agree more with Dave about the need for documentation, DSI
drivers (both on the TX and RX side) are very creative these days,
causing lots of interoperability issues. This wild west situation really
needs some policing.
If anyone documents rules that can be enforced, I'll be very happy to
buy them a few rounds of drinks in any conference we'll happen to both
attend (even more so because that will mean travel restrictions will be
lifted :-)).
> > [1] https://lists.freedesktop.org/archives/dri-devel/2021-September/322119.html
> > [2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c#n776
> > [3] https://lists.freedesktop.org/archives/dri-devel/2021-November/332003.html
> > [4] https://lists.freedesktop.org/archives/dri-devel/2021-July/313576.html
>
> [5] https://patchwork.freedesktop.org/patch/465764/?series=97688&rev=1
>
> > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov at linaro.org>
> > > ---
> > > drivers/gpu/drm/bridge/tc358762.c | 20 ++++++++++----------
> > > 1 file changed, 10 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/bridge/tc358762.c b/drivers/gpu/drm/bridge/tc358762.c
> > > index 7104828024fd..ebdf771a1e49 100644
> > > --- a/drivers/gpu/drm/bridge/tc358762.c
> > > +++ b/drivers/gpu/drm/bridge/tc358762.c
> > > @@ -64,7 +64,7 @@ struct tc358762 {
> > > struct drm_connector connector;
> > > struct regulator *regulator;
> > > struct drm_bridge *panel_bridge;
> > > - bool pre_enabled;
> > > + bool enabled;
> > > int error;
> > > };
> > >
> > > @@ -125,26 +125,26 @@ static int tc358762_init(struct tc358762 *ctx)
> > > return tc358762_clear_error(ctx);
> > > }
> > >
> > > -static void tc358762_post_disable(struct drm_bridge *bridge)
> > > +static void tc358762_disable(struct drm_bridge *bridge)
> > > {
> > > struct tc358762 *ctx = bridge_to_tc358762(bridge);
> > > int ret;
> > >
> > > /*
> > > - * The post_disable hook might be called multiple times.
> > > + * The disable hook might be called multiple times.
> > > * We want to avoid regulator imbalance below.
> > > */
> > > - if (!ctx->pre_enabled)
> > > + if (!ctx->enabled)
> > > return;
> > >
> > > - ctx->pre_enabled = false;
> > > + ctx->enabled = false;
> > >
> > > ret = regulator_disable(ctx->regulator);
> > > if (ret < 0)
> > > dev_err(ctx->dev, "error disabling regulators (%d)\n", ret);
> > > }
> > >
> > > -static void tc358762_pre_enable(struct drm_bridge *bridge)
> > > +static void tc358762_enable(struct drm_bridge *bridge)
> > > {
> > > struct tc358762 *ctx = bridge_to_tc358762(bridge);
> > > int ret;
> > > @@ -157,7 +157,7 @@ static void tc358762_pre_enable(struct drm_bridge *bridge)
> > > if (ret < 0)
> > > dev_err(ctx->dev, "error initializing bridge (%d)\n", ret);
> > >
> > > - ctx->pre_enabled = true;
> > > + ctx->enabled = true;
> > > }
> > >
> > > static int tc358762_attach(struct drm_bridge *bridge,
> > > @@ -170,8 +170,8 @@ static int tc358762_attach(struct drm_bridge *bridge,
> > > }
> > >
> > > static const struct drm_bridge_funcs tc358762_bridge_funcs = {
> > > - .post_disable = tc358762_post_disable,
> > > - .pre_enable = tc358762_pre_enable,
> > > + .disable = tc358762_disable,
> > > + .enable = tc358762_enable,
> > > .attach = tc358762_attach,
> > > };
> > >
> > > @@ -218,7 +218,7 @@ static int tc358762_probe(struct mipi_dsi_device *dsi)
> > > mipi_dsi_set_drvdata(dsi, ctx);
> > >
> > > ctx->dev = dev;
> > > - ctx->pre_enabled = false;
> > > + ctx->enabled = false;
> > >
> > > /* TODO: Find out how to get dual-lane mode working */
> > > dsi->lanes = 1;
--
Regards,
Laurent Pinchart
More information about the dri-devel
mailing list