From: Mark yao <mark.yao@rock-chips.com>
To: Yakir Yang <ykk@rock-chips.com>, Mark Yao <yzq@rock-chips.com>,
Heiko Stuebner <heiko@sntech.de>, David Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
tfiga@chromium.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] drm/rockchip: vop: add uv_vir register field for RK3036 VOP
Date: Tue, 7 Jun 2016 08:57:30 +0800 [thread overview]
Message-ID: <57561BFA.5030000@rock-chips.com> (raw)
In-Reply-To: <1465199912-20932-1-git-send-email-ykk@rock-chips.com>
On 2016年06月06日 15:58, Yakir Yang wrote:
> The WIN0 of RK3036 VOP could support YUV data format, but driver
> forget to add the uv_vir register field for it.
>
> Signed-off-by: Yakir Yang <ykk@rock-chips.com>
> ---
> drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_vop_reg.c b/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> index 3166b46..7da2311 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> @@ -210,6 +210,7 @@ static const struct vop_win_phy rk3036_win0_data = {
> .yrgb_mst = VOP_REG(RK3036_WIN0_YRGB_MST, 0xffffffff, 0),
> .uv_mst = VOP_REG(RK3036_WIN0_CBR_MST, 0xffffffff, 0),
> .yrgb_vir = VOP_REG(RK3036_WIN0_VIR, 0xffff, 0),
> + .uv_vir = VOP_REG(RK3036_WIN0_VIR, 0x1fff, 16),
> };
>
> static const struct vop_win_phy rk3036_win1_data = {
Thanks for this fix, Applied to my drm-fixes.
-- Mark Yao
prev parent reply other threads:[~2016-06-07 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 7:58 [PATCH 1/2] drm/rockchip: vop: add uv_vir register field for RK3036 VOP Yakir Yang
2016-06-06 7:58 ` [PATCH 2/2] drm/rockchip: vop: correct the source size of uv scale factor setting Yakir Yang
2016-06-07 0:57 ` Mark yao
2016-06-07 0:57 ` Mark yao [this message]
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=57561BFA.5030000@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.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=tfiga@chromium.org \
--cc=ykk@rock-chips.com \
--cc=yzq@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