dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	"open list:DRM DRIVERS FOR RENESAS R-CAR"
	<dri-devel@lists.freedesktop.org>,
	"open list:DRM DRIVERS FOR RENESAS R-CAR"
	<linux-renesas-soc@vger.kernel.org>,
	Phong Hoang <phong.hoang.wz@renesas.com>
Subject: Re: [PATCH 2/4] drm: ti-sn65dsi86: Check bridge connection failure
Date: Thu, 20 Jun 2024 09:43:05 +0300	[thread overview]
Message-ID: <404691d2-b013-4bcc-b7e4-bcc809e4bfbb@ideasonboard.com> (raw)
In-Reply-To: <20240619193258.GC31507@pendragon.ideasonboard.com>

On 19/06/2024 22:32, Laurent Pinchart wrote:
> Hi Jacopo,
> 
> Thank you for the patch.
> 
> On Wed, Jun 19, 2024 at 12:22:16PM +0200, Jacopo Mondi wrote:
>> From: Phong Hoang <phong.hoang.wz@renesas.com>
>>
>> Add a check to the register access function when attaching a bridge
>> device.

I think the desc is missing the "why". I'm guessing it's the first 
register access to the IC, and thus verifies that it is accessible.

  Tomi

>>
>> Signed-off-by: Phong Hoang <phong.hoang.wz@renesas.com>
>> Signed-off-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> 
> Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> 
>> ---
>>   drivers/gpu/drm/bridge/ti-sn65dsi86.c | 6 +++++-
>>   1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi86.c b/drivers/gpu/drm/bridge/ti-sn65dsi86.c
>> index 84698a0b27a8..b7df53577987 100644
>> --- a/drivers/gpu/drm/bridge/ti-sn65dsi86.c
>> +++ b/drivers/gpu/drm/bridge/ti-sn65dsi86.c
>> @@ -696,6 +696,7 @@ static struct ti_sn65dsi86 *bridge_to_ti_sn65dsi86(struct drm_bridge *bridge)
>>   
>>   static int ti_sn_attach_host(struct auxiliary_device *adev, struct ti_sn65dsi86 *pdata)
>>   {
>> +	int ret;
>>   	int val;
>>   	struct mipi_dsi_host *host;
>>   	struct mipi_dsi_device *dsi;
>> @@ -720,8 +721,11 @@ static int ti_sn_attach_host(struct auxiliary_device *adev, struct ti_sn65dsi86
>>   
>>   	/* check if continuous dsi clock is required or not */
>>   	pm_runtime_get_sync(dev);
>> -	regmap_read(pdata->regmap, SN_DPPLL_SRC_REG, &val);
>> +	ret = regmap_read(pdata->regmap, SN_DPPLL_SRC_REG, &val);
>>   	pm_runtime_put_autosuspend(dev);
>> +	if (ret)
>> +		return ret;
>> +
>>   	if (!(val & DPPLL_CLK_SRC_DSICLK))
>>   		dsi->mode_flags |= MIPI_DSI_CLOCK_NON_CONTINUOUS;
>>   
> 


  reply	other threads:[~2024-06-20  6:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 10:22 [PATCH 0/4] drm: rcar-du: Add support for R8A779H0 Jacopo Mondi
2024-06-19 10:22 ` [PATCH 1/4] drm: rcar-mipi-dsi: Fix CLOCKSET1_LOCK definition Jacopo Mondi
2024-06-19 19:29   ` Laurent Pinchart
2024-06-20  6:40     ` Tomi Valkeinen
2024-06-19 10:22 ` [PATCH 2/4] drm: ti-sn65dsi86: Check bridge connection failure Jacopo Mondi
2024-06-19 19:32   ` Laurent Pinchart
2024-06-20  6:43     ` Tomi Valkeinen [this message]
2024-06-20 10:42       ` Laurent Pinchart
2024-06-20 11:00         ` Tomi Valkeinen
2024-06-19 10:22 ` [PATCH 3/4] drm: rcar-mipi-dsi: Add support for R8A779H0 Jacopo Mondi
2024-06-19 11:07   ` Krzysztof Kozlowski
2024-06-19 12:00     ` Jacopo Mondi
2024-06-19 12:11       ` Krzysztof Kozlowski
2024-06-19 10:22 ` [PATCH 4/4] drm: rcar-du: " Jacopo Mondi
2024-06-19 19:44   ` Laurent Pinchart
2024-06-20 12:48     ` Geert Uytterhoeven
2024-06-20 16:48       ` Jacopo Mondi
2024-06-20 16:57         ` Geert Uytterhoeven

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=404691d2-b013-4bcc-b7e4-bcc809e4bfbb@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=phong.hoang.wz@renesas.com \
    /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