mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Davis <Ben.Davis@arm.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Cc: nd <nd@arm.com>, Liviu Dudau <Liviu.Dudau@arm.com>,
	Brian Starkey <Brian.Starkey@arm.com>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	"maarten.lankhorst@linux.intel.com" 
	<maarten.lankhorst@linux.intel.com>,
	"maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
	"sean@poorly.run" <sean@poorly.run>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ben Davis <Ben.Davis@arm.com>
Subject: [PATCH v4 0/2] Add writeback scaling
Date: Thu, 2 May 2019 16:10:07 +0000	[thread overview]
Message-ID: <1556813386-18823-1-git-send-email-ben.davis@arm.com> (raw)

Add support for scaling on writeback. To do this add
writeback_dest_x,y,w,h writeback connector properties to specify the
desired output dimensions.
Then implement downscaling on writeback for Malidp-550 and Malidp-650
(upscaling on writeback is not supported on these devices).

v2: Use 0 as default for writeback_w,h and so update range to use 1 as
    minimum.

v3: Rename properties to specify they are destination width/height.
    Make sure the values from the properties are passed to
    enable_memwrite rather than the framebuffer dimensions.

v4: Add writeback_dest_x,y properties as well for consistency with
    plane properties.
    Writing to arbitrary x,y on writeback is not supported on the
    hardware so we simulate this in the driver.
    Clear the properties on duplicate state for robustness.
    Use 0 as minimum for all added properties.
    Also actually make sure the values from the properties are passed
    to enable_memwrite as intended in v3 and some other clean up.

Ben Davis (2):
  drm: Add writeback_dest_x,y,w,h properties
  drm/malidp: Enable writeback scaling

 drivers/gpu/drm/arm/malidp_crtc.c         |  47 ++++++------
 drivers/gpu/drm/arm/malidp_drv.c          |  10 ++-
 drivers/gpu/drm/arm/malidp_drv.h          |   2 +
 drivers/gpu/drm/arm/malidp_hw.c           |  45 ++++++++----
 drivers/gpu/drm/arm/malidp_hw.h           |  19 ++++-
 drivers/gpu/drm/arm/malidp_mw.c           | 117 ++++++++++++++++++++++++------
 drivers/gpu/drm/arm/malidp_regs.h         |   1 +
 drivers/gpu/drm/drm_atomic_state_helper.c |   6 ++
 drivers/gpu/drm/drm_atomic_uapi.c         |  17 +++++
 drivers/gpu/drm/drm_writeback.c           |  66 +++++++++++++++++
 include/drm/drm_connector.h               |  23 ++++++
 include/drm/drm_mode_config.h             |  20 +++++
 12 files changed, 308 insertions(+), 65 deletions(-)

-- 
2.7.4


             reply	other threads:[~2019-05-02 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 16:10 Ben Davis [this message]
2019-05-02 16:10 ` [PATCH v4 1/2] drm: Add writeback_dest_x,y,w,h properties Ben Davis
2019-05-02 16:21   ` Liviu Dudau
2019-05-02 16:10 ` [PATCH v4 2/2] drm/malidp: Enable writeback scaling Ben Davis
2019-05-02 16:24   ` 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=1556813386-18823-1-git-send-email-ben.davis@arm.com \
    --to=ben.davis@arm.com \
    --cc=Brian.Starkey@arm.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=nd@arm.com \
    --cc=sean@poorly.run \
    /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

all inboxes | Powered by JetHome®