From: Mark Yao <mark.yao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
To: Mark Yao <mark.yao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/7] drm/rockchip: add all full framework vop support
Date: Tue, 18 Jul 2017 10:28:07 +0800 [thread overview]
Message-ID: <1500344888-28165-1-git-send-email-mark.yao@rock-chips.com> (raw)
These patches try to make all current rockchip full framework vop works
on drm, fill missing vop on full framework.
Vop Full framework now has following vops:
IP version chipname
3.1 rk3288
3.2 rk3368
3.4 rk3366
3.5 rk3399 big
3.6 rk3399 lit
3.7 rk3228
3.8 rk3328
Group the vop register, it would make register definition clearer and
more easily to reuse same group register define for difference vops.
Tested on rk3399 excavator board with kernel 4.12-rc1.
And other chips works find on rockchip kernel 4.4:
https://github.com/rockchip-linux/kernel/tree/release-4.4/drivers/gpu/drm/rockchip
Changes in v3:
- group vop register instead using VOP_REG_VER mechanism
- move write_relaxed flags to vop registers
- Explain more on patch commit message
- fix rk3328 overlay abnormal
Changes in v2:
- rename rk322x to rk3228(Heiko Stübner)
- correct some vop registers define
Mark Yao (7):
drm/rockchip: vop: initialize registers directly
drm/rockchip: vop: move write_relaxed flags to vop register
drm/rockchip: vop: move line_flag_num to interrupt registers
drm/rockchip: vop: group vop registers
drm/rockchip: vop: add a series of vop support
dt-bindings: display: fill Documents for series of vop
drm/rockchip: vop: rk3328: fix overlay abnormal
.../bindings/display/rockchip/rockchip-vop.txt | 4 +
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 109 ++-
drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 81 +-
drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 374 ++++++---
drivers/gpu/drm/rockchip/rockchip_vop_reg.h | 905 ++++++++++++++++-----
5 files changed, 1074 insertions(+), 399 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-07-18 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 2:28 Mark Yao [this message]
2017-07-18 2:28 ` [PATCH v3 1/7] drm/rockchip: vop: initialize registers directly Mark Yao
2017-07-18 2:28 ` [PATCH v3 2/7] drm/rockchip: vop: move write_relaxed flags to vop register Mark Yao
2017-07-18 2:28 ` [PATCH v3 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers Mark Yao
2017-07-18 2:28 ` [PATCH v3 4/7] drm/rockchip: vop: group vop registers Mark Yao
2017-07-18 2:28 ` [PATCH v3 5/7] drm/rockchip: vop: add a series of vop support Mark Yao
2017-07-18 2:28 ` [PATCH v3 6/7] dt-bindings: display: fill Documents for series of vop Mark Yao
2017-07-18 2:28 ` [PATCH v3 7/7] drm/rockchip: vop: rk3328: fix overlay abnormal 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=1500344888-28165-1-git-send-email-mark.yao@rock-chips.com \
--to=mark.yao-tnx95d0mmh7dzftrwevzcw@public.gmane.org \
--cc=airlied-cv59FeDIM0c@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).