From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>, Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>
Subject: Re: [PATCH 1/1] drm/bridge: ti-sn65dsi83: Fix enable error path
Date: Thu, 4 May 2023 10:43:56 +0300 [thread overview]
Message-ID: <20230504074356.GD4551@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20230504065316.2640739-1-alexander.stein@ew.tq-group.com>
Hi Alexander,
Thank you for the patch.
On Thu, May 04, 2023 at 08:53:16AM +0200, Alexander Stein wrote:
> If PLL locking failed, the regulator needs to be disabled again.
>
> Fixes: 5664e3c907e2 ("drm/bridge: ti-sn65dsi83: Add vcc supply regulator support")
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> drivers/gpu/drm/bridge/ti-sn65dsi83.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> index 75286c9afbb9..1f5c07989e2b 100644
> --- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> +++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> @@ -478,6 +478,7 @@ static void sn65dsi83_atomic_enable(struct drm_bridge *bridge,
> dev_err(ctx->dev, "failed to lock PLL, ret=%i\n", ret);
> /* On failure, disable PLL again and exit. */
> regmap_write(ctx->regmap, REG_RC_PLL_EN, 0x00);
> + regulator_disable(ctx->vcc);
> return;
> }
>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-05-04 7:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 6:53 [PATCH 1/1] drm/bridge: ti-sn65dsi83: Fix enable error path Alexander Stein
2023-05-04 7:43 ` Laurent Pinchart [this message]
2023-05-04 7:54 ` rfoss
2024-02-22 15:36 ` Luca Ceresoli
2024-02-27 12:05 ` Alexander Stein
2024-02-27 17:41 ` Luca Ceresoli
2024-02-28 6:59 ` Alexander Stein
2024-02-28 8:15 ` Alexander Stein
2024-02-29 9:47 ` Luca Ceresoli
2024-02-29 10:48 ` Frieder Schrempf
2024-03-01 9:13 ` Luca Ceresoli
2024-02-29 11:11 ` Alexander Stein
2024-03-01 9:44 ` Luca Ceresoli
2024-03-01 9:57 ` Alexander Stein
2024-03-01 10:10 ` Luca Ceresoli
2024-03-01 10:45 ` Alexander Stein
2024-03-06 12:41 ` Luca Ceresoli
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=20230504074356.GD4551@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox