devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrzej Hajda <a.hajda@samsung.com>
To: YoungJun Cho <yj44.cho@samsung.com>,
	airlied@linux.ie, dri-devel@lists.freedesktop.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org, pawel.moll@arm.com,
	ijc+devicetree@hellion.org.uk, sw0312.kim@samsung.com,
	kyungmin.park@samsung.com, robh+dt@kernel.org,
	galak@codeaurora.org, kgene.kim@samsung.com
Subject: Re: [RFC PATCH 02/14] drm/exynos: dsi: delay setting clocks after reset
Date: Fri, 18 Apr 2014 14:15:48 +0200	[thread overview]
Message-ID: <53511774.7030607@samsung.com> (raw)
In-Reply-To: <1397540862-21359-3-git-send-email-yj44.cho@samsung.com>

Hi YoungJun,

Thanks for the whole patchset.

On 04/15/2014 07:47 AM, YoungJun Cho wrote:
> Some phy control registers are not kept after software reset.
> So this patch makes the clocks containing phy control to be set
> after software reset.
>
> Signed-off-by: YoungJun Cho <yj44.cho@samsung.com>
> Signed-off-by: Inki Dae <inki.dae@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
>  drivers/gpu/drm/exynos/exynos_drm_dsi.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/exynos/exynos_drm_dsi.c b/drivers/gpu/drm/exynos/exynos_drm_dsi.c
> index 956e5f3..2cf1f0b 100644
> --- a/drivers/gpu/drm/exynos/exynos_drm_dsi.c
> +++ b/drivers/gpu/drm/exynos/exynos_drm_dsi.c
> @@ -946,10 +946,10 @@ static irqreturn_t exynos_dsi_irq(int irq, void *dev_id)
>  
>  static int exynos_dsi_init(struct exynos_dsi *dsi)
>  {
> -	exynos_dsi_enable_clock(dsi);
>  	exynos_dsi_reset(dsi);
>  	enable_irq(dsi->irq);
>  	exynos_dsi_wait_for_reset(dsi);
> +	exynos_dsi_enable_clock(dsi);
>  	exynos_dsi_init_link(dsi);
>  
>  	return 0;
Are you sure this sequence is OK? I have observed that sequence:

dsi power off
dsi power on
dsi_reset

on 4210 or 4412 resulted in lack of irq after reset, only enabling
clocks helped.
And according to documentation reset do not touch registers set by
exynos_dsi_enable_clock,
so the current solution should work.

Regards
Andrzej

  reply	other threads:[~2014-04-18 12:15 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15  5:47 [RFC PATCH 00/14] drm/exynos: support MIPI DSI command mode display YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 01/14] drm/exynos: dsi: move the Eot packets configuration point YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 02/14] drm/exynos: dsi: delay setting clocks after reset YoungJun Cho
2014-04-18 12:15   ` Andrzej Hajda [this message]
2014-04-19 22:30     ` YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 03/14] drm/exynos: use wait_event_timeout() for safety usage YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 04/14] ARM: dts: add exynos5 compatible to sysreg YoungJun Cho
2014-04-15  8:02   ` Sachin Kamat
2014-04-16  4:38     ` [RFC PATCH v2 04/14] ARM: dts: sysreg: add exynos5 compatible to DT bindings YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 05/14] ARM: dts: samsung-fimd: add I80 specific properties YoungJun Cho
2014-04-16 21:26   ` Laurent Pinchart
2014-04-17  5:33     ` YoungJun Cho
2014-04-17 11:53       ` [RFC PATCH v2 " YoungJun Cho
2014-04-18 12:32         ` Andrzej Hajda
2014-04-20  0:34           ` YoungJun Cho
2014-04-21 22:35       ` [RFC PATCH " Laurent Pinchart
2014-04-15  5:47 ` [RFC PATCH 06/14] drm/exynos: support MIPI DSI command mode YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 07/14] ARM: dts: exynos_dsim: add exynos5420 Soc compatible YoungJun Cho
     [not found]   ` <1397540862-21359-8-git-send-email-yj44.cho-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-04-15  8:09     ` Sachin Kamat
2014-04-16  4:38       ` [RFC PATCH v2 07/14] ARM: dts: exynos_dsim: add exynos5420 compatible to DT bindings YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 08/14] drm/exynos: dsi: add driver data to support Exynos5420 YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 09/14] ARM: dts: s6e3fa0: add DT bindings YoungJun Cho
2014-04-15  8:18   ` Sachin Kamat
2014-04-16  4:38     ` [RFC PATCH v2 " YoungJun Cho
2014-04-16 21:45       ` Laurent Pinchart
2014-04-17 11:54         ` [RFC PATCH v3 " YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 10/14] drm/panel: add S6E3FA0 driver YoungJun Cho
2014-04-17 11:54   ` [RFC PATCH v3 " YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 11/14] ARM: dts: exynos4: add system register node YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 12/14] ARM: dts: exynos5: add system register support YoungJun Cho
2014-04-15  8:41   ` Sachin Kamat
2014-04-15  9:18     ` Sylwester Nawrocki
2014-04-15  9:31       ` Sachin Kamat
2014-04-15  5:47 ` [RFC PATCH 13/14] ARM: dts: exynos5420: add mipi-phy node YoungJun Cho
2014-04-15  5:47 ` [RFC PATCH 14/14] ARM: dts: exynos5420: add dsi node YoungJun Cho
2014-04-15  8:04   ` Sachin Kamat
2014-04-16  4:39     ` [RFC PATCH v2 " YoungJun Cho

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=53511774.7030607@samsung.com \
    --to=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sw0312.kim@samsung.com \
    --cc=yj44.cho@samsung.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;
as well as URLs for NNTP newsgroup(s).