All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Foss <robert.foss@linaro.org>
To: Marek Vasut <marex@denx.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Jagan Teki <jagan@amarulasolutions.com>,
	dri-devel@lists.freedesktop.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH][RESEND] drm/bridge: ti-sn65dsi83: Check link status register after enabling the bridge
Date: Thu, 31 Mar 2022 17:32:24 +0200	[thread overview]
Message-ID: <CAG3jFyvvM4hah-bqYZdD9zOM2bB04ioD_67TJGgcnZf33=zX-w@mail.gmail.com> (raw)
In-Reply-To: <20220213022648.495895-1-marex@denx.de>

On Sun, 13 Feb 2022 at 03:27, Marek Vasut <marex@denx.de> wrote:
>
> In rare cases, the bridge may not start up correctly, which usually
> leads to no display output. In case this happens, warn about it in
> the kernel log.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Jagan Teki <jagan@amarulasolutions.com>
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Robert Foss <robert.foss@linaro.org>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: dri-devel@lists.freedesktop.org
> ---
>  drivers/gpu/drm/bridge/ti-sn65dsi83.c | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> index 19daaddd29a41..1d7c154ea1d79 100644
> --- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> +++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> @@ -488,6 +488,11 @@ static void sn65dsi83_atomic_enable(struct drm_bridge *bridge,
>         /* Clear all errors that got asserted during initialization. */
>         regmap_read(ctx->regmap, REG_IRQ_STAT, &pval);
>         regmap_write(ctx->regmap, REG_IRQ_STAT, pval);
> +
> +       usleep_range(10000, 12000);
> +       regmap_read(ctx->regmap, REG_IRQ_STAT, &pval);
> +       if (pval)
> +               dev_err(ctx->dev, "Unexpected link status 0x%02x\n", pval);
>  }
>
>  static void sn65dsi83_atomic_disable(struct drm_bridge *bridge,
> --
> 2.34.1
>

Reviewed-by: Robert Foss <robert.foss@linaro.org>

  reply	other threads:[~2022-03-31 15:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13  2:26 [PATCH][RESEND] drm/bridge: ti-sn65dsi83: Check link status register after enabling the bridge Marek Vasut
2022-03-31 15:32 ` Robert Foss [this message]
2022-03-31 15:32   ` Robert Foss
2022-04-05 11:42 ` Laurent Pinchart
2022-04-05 11:59   ` Marek Vasut
2022-04-05 12:00   ` Dave Stevenson
2022-04-05 13:08     ` Laurent Pinchart
2022-04-05 13:25       ` Dave Stevenson
2022-04-05 13:49         ` Marek Vasut
2022-04-05 14:20           ` Dave Stevenson
2022-04-05 14:48             ` Marek Vasut
2022-04-05 15:24               ` Dave Stevenson
2022-04-05 21:36                 ` Marek Vasut
2022-04-06 14:11                   ` Frieder Schrempf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG3jFyvvM4hah-bqYZdD9zOM2bB04ioD_67TJGgcnZf33=zX-w@mail.gmail.com' \
    --to=robert.foss@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=marex@denx.de \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.