[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <587DECC3.50304@rock-chips.com>
Date: Tue, 17 Jan 2017 18:06:59 +0800
From: Mark yao <mark.yao@...k-chips.com>
To: Tomasz Figa <tfiga@...omium.org>
Cc: Chris Zhong <zyw@...k-chips.com>,
姚智情 <yzq@...k-chips.com>,
Heiko Stübner <heiko@...ech.de>,
David Airlie <airlied@...ux.ie>,
Douglas Anderson <dianders@...omium.org>,
Stéphane Marchesin <marcheu@...omium.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sean Paul <seanpaul@...omium.org>, briannorris@...omium.org
Subject: Re: [PATCH] drm/rockchip: vop: make vop register setting take effect
Hi Tomasz
I had sent to Dave, but maybe something is wrong, it miss.
the patch is on this pull-request:
https://lists.freedesktop.org/archives/dri-devel/2016-September/118505.html
I forgot to double check it, I will resend to Dave soon.
Thanks.
On 2017年01月17日 17:32, Tomasz Figa wrote:
> Hi Mark,
>
> On Mon, Aug 29, 2016 at 11:51 AM, Mark yao <mark.yao@...k-chips.com> wrote:
>> 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@...k-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.
> This patch seems to have been lost in action. I don't see it in linux-next.
>
> Best regards,
> Tomasz
>
>
>
--
Mark Yao
Powered by blists - more mailing lists