public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: "Daniel Vetter" <daniel.vetter@intel.com>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Brian Starkey" <brian.starkey@arm.com>,
	"Sean Paul" <seanpaul@chromium.org>,
	"DRI devel" <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Eric Anholt" <eric@anholt.net>
Subject: Re: [PATCH v5 0/3] drm/mali-dp: Add support for memory writeback engine
Date: Fri, 2 Jun 2017 10:34:26 +0200	[thread overview]
Message-ID: <20170602103426.76a20b58@bbrezillon> (raw)
In-Reply-To: <20170515172402.30452-1-Liviu.Dudau@arm.com>

On Mon, 15 May 2017 18:23:59 +0100
Liviu Dudau <Liviu.Dudau@arm.com> wrote:

> Hi,
> 
> This series introduces support for Mali DP's memory writeback engine
> using the generic writeback connector support introduced in the
> "[PATCH v5 0/2] drm: Introduce writeback connectors" series [1]
> 
> This version updates the Mali DP code to remove the bespoke encoder used
> with the drm_writeback_connector and instead rely on the builtin one from
> the v5 series.
> 
> v4 series can be found here [2].

Whole series is

Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>

> 
> Best regards,
> Liviu
> 
> [1] https://lists.freedesktop.org/archives/dri-devel/2017-May/141796.html
> [2] https://lists.freedesktop.org/archives/dri-devel/2017-May/140850.html
> 
> Brian Starkey (2):
>   drm: mali-dp: Add RGB writeback formats for DP550/DP650
>   drm: mali-dp: Add writeback connector
> 
> Liviu Dudau (1):
>   drm: mali-dp: Add support for writeback on DP550/DP650
> 
>  drivers/gpu/drm/arm/Makefile      |   1 +
>  drivers/gpu/drm/arm/malidp_crtc.c |   9 ++
>  drivers/gpu/drm/arm/malidp_drv.c  |  19 ++-
>  drivers/gpu/drm/arm/malidp_drv.h  |   3 +
>  drivers/gpu/drm/arm/malidp_hw.c   |  88 ++++++++++---
>  drivers/gpu/drm/arm/malidp_hw.h   |  18 +++
>  drivers/gpu/drm/arm/malidp_mw.c   | 252 ++++++++++++++++++++++++++++++++++++++
>  drivers/gpu/drm/arm/malidp_mw.h   |  18 +++
>  drivers/gpu/drm/arm/malidp_regs.h |  15 +++
>  9 files changed, 402 insertions(+), 21 deletions(-)
>  create mode 100644 drivers/gpu/drm/arm/malidp_mw.c
>  create mode 100644 drivers/gpu/drm/arm/malidp_mw.h
> 

  parent reply	other threads:[~2017-06-02  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 17:23 [PATCH v5 0/3] drm/mali-dp: Add support for memory writeback engine Liviu Dudau
2017-05-15 17:24 ` [PATCH v5 1/3] drm: mali-dp: Add support for writeback on DP550/DP650 Liviu Dudau
2017-05-15 17:24 ` [PATCH v5 2/3] drm: mali-dp: Add RGB writeback formats for DP550/DP650 Liviu Dudau
2017-05-15 17:24 ` [PATCH v5 3/3] drm: mali-dp: Add writeback connector Liviu Dudau
2017-05-28  2:23   ` kbuild test robot
2017-06-02  8:34 ` Boris Brezillon [this message]
2017-06-02  9:24   ` [PATCH v5 0/3] drm/mali-dp: Add support for memory writeback engine Liviu Dudau

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=20170602103426.76a20b58@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=brian.starkey@arm.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanpaul@chromium.org \
    --cc=ville.syrjala@linux.intel.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