Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 0/2] Enable R8A7794 DU VSPD compositor
Date: Thu, 29 Dec 2016 11:54:43 +0200	[thread overview]
Message-ID: <3105218.LKxk3bXDQr@avalon> (raw)
In-Reply-To: <18781159.4YChoBxRU5@wasted.cogentembedded.com>

Hi Sergei,

On Thursday 29 Dec 2016 00:18:40 Sergei Shtylyov wrote:
> Hello.
> 
>    Here's the set of 2 patches against the 'drm-next' branch of David
> Airlie's 'linux.git' repo. We're switching to the DU compositor for the DU
> driver on the Renesas R8A7794 SoC.
> 
> [1/2] drm: rcar-du: support less VSPs than CRTCs
> [2/2] drm: rcar-du: enable VSPD on R8A7794

Nack for the same reasons as your previous related patches. If you want to get 
this feature merged we'll need to configure whether the VSPD is used 
standalone or for DU operation at runtime. The DRM live sources were an 
attempt at implementing that, feel free to revive the idea and brush up the 
patches.

-- 
Regards,

Laurent Pinchart

      parent reply	other threads:[~2016-12-29  9:54 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 ` [PATCH 2/2] drm: rcar-du: enable VSPD on R8A7794 Sergei Shtylyov
2016-12-29  9:54 ` Laurent Pinchart [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=3105218.LKxk3bXDQr@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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