From: Mark Yao <mark.yao@rock-chips.com>
To: Mark Yao <mark.yao@rock-chips.com>,
David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] drm/rockchip: add all full framework vop support
Date: Tue, 11 Jul 2017 20:41:47 +0800 [thread overview]
Message-ID: <1499776908-16811-1-git-send-email-mark.yao@rock-chips.com> (raw)
These patches try to make all current rockchip full framework vop works
on drm, The newer vop design always have some different to the old one,
So we add a register verify mechanism to distinguish those register, then
the registers table can be reused.
And people can easy to know the different for the vops from register table.
Mark Yao (5):
drm/rockchip: vop: get rid of register init table
drm/rockchip: vop: support verify registers with vop version
drm/rockchip: vop: move line_flag_num to interrupt registers
drm/rockchip: vop: add a series of vop support
dt-bindings: display: fill Documents for series of vop
.../bindings/display/rockchip/rockchip-vop.txt | 4 +
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 74 +-
drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 32 +-
drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 259 +++---
drivers/gpu/drm/rockchip/rockchip_vop_reg.h | 905 ++++++++++++++++-----
5 files changed, 952 insertions(+), 322 deletions(-)
--
1.9.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-07-11 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 12:41 Mark Yao [this message]
2017-07-11 12:42 ` [PATCH 5/5] dt-bindings: display: fill Documents for series of vop Mark Yao
[not found] ` <1499776958-17062-1-git-send-email-mark.yao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-07-11 12:45 ` Heiko Stübner
2017-07-12 0:21 ` 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=1499776908-16811-1-git-send-email-mark.yao@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--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=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).