From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: laurent.pinchart@ideasonboard.com, airlied@linux.ie,
dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH 2/2] drm: rcar-du: enable VSPD on R8A7794
Date: Thu, 29 Dec 2016 00:20:33 +0300 [thread overview]
Message-ID: <1637352.TRSum6nTUx@wasted.cogentembedded.com> (raw)
In-Reply-To: <18781159.4YChoBxRU5@wasted.cogentembedded.com>
We're going to use R8A7794 VSPD to control DU, so set the corresponding flag
and the newly added field, 'num_vspds'...
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
drivers/gpu/drm/rcar-du/rcar_du_drv.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index: linux/drivers/gpu/drm/rcar-du/rcar_du_drv.c
===================================================================
--- linux.orig/drivers/gpu/drm/rcar-du/rcar_du_drv.c
+++ linux/drivers/gpu/drm/rcar-du/rcar_du_drv.c
@@ -136,7 +136,8 @@ static const struct rcar_du_device_info
static const struct rcar_du_device_info rcar_du_r8a7794_info = {
.gen = 2,
.features = RCAR_DU_FEATURE_CRTC_IRQ_CLOCK
- | RCAR_DU_FEATURE_EXT_CTRL_REGS,
+ | RCAR_DU_FEATURE_EXT_CTRL_REGS
+ | RCAR_DU_FEATURE_VSP1_SOURCE,
.num_crtcs = 2,
.routes = {
/* R8A7794 has two RGB outputs and one (currently unsupported)
@@ -154,6 +155,7 @@ static const struct rcar_du_device_info
},
},
.num_lvds = 0,
+ .num_vspds = 1,
};
static const struct rcar_du_device_info rcar_du_r8a7795_info = {
next prev parent reply other threads:[~2016-12-28 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 21:18 [PATCH 0/2] Enable R8A7794 DU VSPD compositor Sergei Shtylyov
2016-12-28 21:19 ` [PATCH 1/2] drm: rcar-du: support less VSPs than CRTCs Sergei Shtylyov
2016-12-28 21:20 ` Sergei Shtylyov [this message]
2016-12-29 9:54 ` [PATCH 0/2] Enable R8A7794 DU VSPD compositor Laurent Pinchart
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=1637352.TRSum6nTUx@wasted.cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.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