Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-samsung-soc@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	dri-devel@lists.freedesktop.org, Yakir Yang <ykk@rock-chips.com>
Subject: Re: [PATCH] drm/bridge: analogix_dp: Keep PHY powered from between driver bind/unbind
Date: Fri, 23 Feb 2018 08:35:32 +0100	[thread overview]
Message-ID: <fd258889-c07a-4818-8274-bbcecf554202@samsung.com> (raw)
In-Reply-To: <2791004.ZRT6x1hf9f@avalon>

Hi Laurent,

On 2018-02-21 13:49, Laurent Pinchart wrote:
> Thank you for the patch.
>
> On Wednesday, 21 February 2018 12:04:43 EET Marek Szyprowski wrote:
>> Patch f0a8b49c03d2 ("drm/bridge: analogix dp: Fix runtime PM state on
>> driver bind") fixed unbalanced call to phy_power_on() in analogix_dp_bind()
>> function by calling phy_power_off() at the end of bind operation.
>>
>> However it turned out that having PHY powered is required for proper DRM
>> display pipeline initialization on Peach-Pit Chromebook2 board, as this
>> board freezes otherwise when PHY power off is called in bind. Fix this by
>> keeping PHY powered for the whole bind/unbind driver life cycle. The
>> freeze is probably related to the fact that the display pipeline (Exynos
>> FIMD CTRC -> Exynos/Analogix DP bridge -> PS8625 dp2lvds bridge -> B116XW03
>> panel) is already configured and enabled by the bootloader and require
>> reset of all components for proper shutdown.
> "Probably" always makes me feel uncomfortable in such a context :-) Leaving
> the PHY powered at all times isn't the best idea as it will increase power
> consumption even when the DP output isn't in use. I can live with that if
> there's no other way, but it feels to me like we should first get to the
> bottom of the issue.

Frankly I spent some time on this and I have no other idea. Board 
freezes when
phy_power_off is called and the initial code worked properly on that 
board by
leaking phy turned on all the time.

>> Having PHY powered is also needed for proper EDID handling, which initially
>> fixed by commit 510353a63796 ("drm/bridge: analogix dp: Fix runtime PM state
>> in get_modes() callback").
>>
>> Fixes: f0a8b49c03d2 ("drm/bridge: analogix dp: Fix runtime PM state on
>> driver bind")
>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> ---
>>   drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
>> b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c index
>> b2756bc4225a..42595863cb03 100644
>> --- a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
>> +++ b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
>> @@ -1415,7 +1415,6 @@ int analogix_dp_bind(struct device *dev, struct
>> drm_device *drm_dev, goto err_disable_pm_runtime;
>>   	}
>>
>> -	phy_power_off(dp->phy);
>>   	pm_runtime_put(dev);
>>
>>   	return 0;
>> @@ -1448,6 +1447,7 @@ void analogix_dp_unbind(struct device *dev, struct
>> device *master,
>>
>>   	drm_dp_aux_unregister(&dp->aux);
>>   	pm_runtime_disable(dev);
>> +	phy_power_off(dp->phy);
>>   	clk_disable_unprepare(dp->clock);
>>   }
>>   EXPORT_SYMBOL_GPL(analogix_dp_unbind);

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-02-23  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180221100455eucas1p1613b6fa148d3e8a80f0053a3542aaa18@eucas1p1.samsung.com>
2018-02-21 10:04 ` [PATCH] drm/bridge: analogix_dp: Keep PHY powered from between driver bind/unbind Marek Szyprowski
2018-02-21 12:49   ` Laurent Pinchart
2018-02-23  7:35     ` Marek Szyprowski [this message]
2018-02-23  9:13       ` Laurent Pinchart

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=fd258889-c07a-4818-8274-bbcecf554202@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=ykk@rock-chips.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