From: Mark yao <mark.yao@rock-chips.com>
To: Chris Zhong <zyw@rock-chips.com>,
yzq@rock-chips.com, tfiga@chromium.org, heiko@sntech.de,
airlied@linux.ie
Cc: dianders@chromium.org, marcheu@chromium.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, seanpaul@chromium.org,
briannorris@chromium.org
Subject: Re: [PATCH] drm/rockchip: vop: make vop register setting take effect
Date: Mon, 29 Aug 2016 10:51:45 +0800 [thread overview]
Message-ID: <57C3A341.9030302@rock-chips.com> (raw)
In-Reply-To: <1472269178-16593-1-git-send-email-zyw@rock-chips.com>
On 2016年08月27日 11:39, Chris Zhong wrote:
> The setting of vop registers need a reg_done writing to take effect.
> In vop_enable the vop return to work by by restoring registers, but the
> registers do not take effect immediately, it should a vop_cfg_done
> after it. The same thing is needed by windows_disabled in
> vop_crtc_disable.
>
> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
> ---
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 4 ++++
> 1 file changed, 4 insertions(+)
Thanks for your fix.
applied to my drm-fixes.
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> index efbc41a..a0bfcff 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> @@ -464,6 +464,8 @@ static int vop_enable(struct drm_crtc *crtc)
> }
>
> memcpy(vop->regs, vop->regsbak, vop->len);
> + vop_cfg_done(vop);
> +
> /*
> * At here, vop clock & iommu is enable, R/W vop regs would be safe.
> */
> @@ -513,6 +515,8 @@ static void vop_crtc_disable(struct drm_crtc *crtc)
> spin_unlock(&vop->reg_lock);
> }
>
> + vop_cfg_done(vop);
> +
> drm_crtc_vblank_off(crtc);
>
> /*
--
Mark Yao
WARNING: multiple messages have this Message-ID (diff)
From: mark.yao@rock-chips.com (Mark yao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/rockchip: vop: make vop register setting take effect
Date: Mon, 29 Aug 2016 10:51:45 +0800 [thread overview]
Message-ID: <57C3A341.9030302@rock-chips.com> (raw)
In-Reply-To: <1472269178-16593-1-git-send-email-zyw@rock-chips.com>
On 2016?08?27? 11:39, Chris Zhong wrote:
> The setting of vop registers need a reg_done writing to take effect.
> In vop_enable the vop return to work by by restoring registers, but the
> registers do not take effect immediately, it should a vop_cfg_done
> after it. The same thing is needed by windows_disabled in
> vop_crtc_disable.
>
> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
> ---
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 4 ++++
> 1 file changed, 4 insertions(+)
Thanks for your fix.
applied to my drm-fixes.
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> index efbc41a..a0bfcff 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> @@ -464,6 +464,8 @@ static int vop_enable(struct drm_crtc *crtc)
> }
>
> memcpy(vop->regs, vop->regsbak, vop->len);
> + vop_cfg_done(vop);
> +
> /*
> * At here, vop clock & iommu is enable, R/W vop regs would be safe.
> */
> @@ -513,6 +515,8 @@ static void vop_crtc_disable(struct drm_crtc *crtc)
> spin_unlock(&vop->reg_lock);
> }
>
> + vop_cfg_done(vop);
> +
> drm_crtc_vblank_off(crtc);
>
> /*
--
?ark Yao
next prev parent reply other threads:[~2016-08-29 2:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 3:39 [PATCH] drm/rockchip: vop: make vop register setting take effect Chris Zhong
2016-08-27 3:39 ` Chris Zhong
2016-08-29 2:51 ` Mark yao [this message]
2016-08-29 2:51 ` Mark yao
2017-01-17 9:32 ` Tomasz Figa
2017-01-17 9:32 ` Tomasz Figa
2017-01-17 9:32 ` Tomasz Figa
[not found] ` <CAAFQd5CP8ERvJzchZo0=5gvuUuP+EBiyfhKDkgRYBa8iQYW0Kw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-17 10:06 ` Mark yao
2017-01-17 10:06 ` Mark yao
2017-01-17 10:06 ` Mark yao
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=57C3A341.9030302@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marcheu@chromium.org \
--cc=seanpaul@chromium.org \
--cc=tfiga@chromium.org \
--cc=yzq@rock-chips.com \
--cc=zyw@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 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.