From: Tomasz Figa <tfiga@chromium.org>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/5] drm/rockchip: sort registers define by chip's number
Date: Thu, 2 Jun 2016 06:51:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20160602T084340-509@post.gmane.org> (raw)
In-Reply-To: 1461133097-1478-2-git-send-email-mark.yao@rock-chips.com
Hi Mark,
Mark Yao <mark.yao <at> rock-chips.com> writes:
>
> No functional changes, sort the vop registers to make
> code more readable.
I might have found a typo. I guess it could be just fixed in this patch,
if it's already moving the code around. Please see the comments inline.
>
> Signed-off-by: Mark Yao <mark.yao <at> rock-chips.com>
> ---
> drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 166 +++++++++++++--------
------
> drivers/gpu/drm/rockchip/rockchip_vop_reg.h | 88 +++++++-------
> 2 files changed, 127 insertions(+), 127 deletions(-)
>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
b/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> index 3166b46..e75b2b8 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_vop_reg.c
> <at> <at> -50,6 +50,87 <at> <at> static const uint32_t
formats_win_lite[] = {
> DRM_FORMAT_BGR565,
> };
>
> +static const struct vop_scl_regs rk3066_win_scl = {
Why is this rk3066 and not rk3036? It doesn't match the sorting order
introduced by this patch, by the way. Typo?
> + .scale_yrgb_x = VOP_REG(RK3036_WIN0_SCL_FACTOR_YRGB, 0xffff, 0x0),
> + .scale_yrgb_y = VOP_REG(RK3036_WIN0_SCL_FACTOR_YRGB, 0xffff, 16),
> + .scale_cbcr_x = VOP_REG(RK3036_WIN0_SCL_FACTOR_CBR, 0xffff, 0x0),
> + .scale_cbcr_y = VOP_REG(RK3036_WIN0_SCL_FACTOR_CBR, 0xffff, 16),
> +};
> +
> +static const struct vop_win_phy rk3036_win0_data = {
> + .scl = &rk3066_win_scl,
Ditto.
Best regards,
Tomasz
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-02 6:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 6:18 [PATCH v2 0/5] drm/rockchip: add rk3399 display controller support Mark Yao
2016-04-20 6:18 ` [PATCH v2 1/5] drm/rockchip: sort registers define by chip's number Mark Yao
2016-06-02 6:51 ` Tomasz Figa [this message]
2016-06-02 7:05 ` Mark yao
2016-08-17 17:20 ` [PATCH v3 " Sean Paul
2016-08-18 9:08 ` Mark yao
2016-08-18 9:11 ` Daniel Vetter
2016-08-18 10:02 ` Mark yao
2016-08-22 20:30 ` Sean Paul
2016-08-23 0:40 ` Mark yao
2016-08-23 13:13 ` Sean Paul
2016-08-25 2:25 ` Mark yao
2016-08-25 17:15 ` Sean Paul
2016-08-25 17:17 ` Sean Paul
2016-04-20 6:18 ` [PATCH v2 2/5] dt-bindings: sort Rockchip vop compatible " Mark Yao
2016-04-20 6:18 ` [PATCH v2 3/5] drm/rockchip: vop: introduce VOP_REG_MASK Mark Yao
2016-06-02 7:19 ` Tomasz Figa
2016-08-17 17:23 ` [PATCH v3 " Sean Paul
2016-04-20 6:18 ` [PATCH v2 4/5] drm/rockchip: vop: add rk3399 vop support Mark Yao
2016-06-02 7:27 ` Tomasz Figa
2016-04-20 6:20 ` [PATCH v2 5/5] dt-bindings: add documentation for Rockchip rk3399 display controllers Mark Yao
2016-06-02 7:33 ` Tomasz Figa
2016-08-17 17:16 ` [PATCH v3 5/5] dt-bindings: add compatible strings for big/little rockchip vops Sean Paul
[not found] <0001-<1471454202-1631-1-git-send-email-seanpaul@chromium.org>
2016-08-18 21:12 ` Sean Paul
[not found] ` <1471554763-22202-1-git-send-email-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-08-19 13:50 ` Rob Herring
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=loom.20160602T084340-509@post.gmane.org \
--to=tfiga@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
/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