public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Andrzej Pietrasiewicz <andrzej.p@collabora•com>
To: dri-devel@lists•freedesktop.org
Cc: "Heiko Stübner" <heiko@sntech•de>,
	"David Airlie" <airlied@linux•ie>,
	"Liviu Dudau" <liviu.dudau@arm•com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux•intel.com>,
	"Sandy Huang" <hjc@rock-chips•com>,
	"Maxime Ripard" <mripard@kernel•org>,
	"Andrzej Pietrasiewicz" <andrzej.p@collabora•com>,
	linux-rockchip@lists•infradead.org,
	linux-arm-kernel@lists•infradead.org,
	"Daniel Vetter" <daniel@ffwll•ch>,
	kernel@collabora•com, "Sean Paul" <sean@poorly•run>,
	"Brian Starkey" <brian.starkey@arm•com>,
	linux-kernel@vger•kernel.org
Subject: [PATCH 0/2] AFBC for Rockchip
Date: Fri, 11 Oct 2019 13:18:09 +0200	[thread overview]
Message-ID: <20191011111813.20851-1-andrzej.p@collabora.com> (raw)

This series adds AFBC support for Rockchip.
It is inspired by:

https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/factory-gru-9017.B-chromeos-4.4/drivers/gpu/drm/rockchip/rockchip_drm_vop.c

The first patch factors out some afbc helper functions from malidp,
as they are useful in general. The second patch adds implementation proper
of AFBC support for Rockchip.

Andrzej Pietrasiewicz (2):
  drm/arm: Factor out generic afbc helpers
  drm/rockchip: Add support for afbc

 drivers/gpu/drm/Kconfig                     |   4 +
 drivers/gpu/drm/Makefile                    |   1 +
 drivers/gpu/drm/arm/Kconfig                 |   1 +
 drivers/gpu/drm/arm/malidp_drv.c            |  58 +-------
 drivers/gpu/drm/drm_afbc.c                  | 114 ++++++++++++++++
 drivers/gpu/drm/rockchip/Kconfig            |   1 +
 drivers/gpu/drm/rockchip/rockchip_drm_fb.c  |  43 ++++++
 drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 140 +++++++++++++++++++-
 drivers/gpu/drm/rockchip/rockchip_drm_vop.h |  12 ++
 drivers/gpu/drm/rockchip/rockchip_vop_reg.c |  86 +++++++++++-
 include/drm/drm_afbc.h                      |  25 ++++
 11 files changed, 427 insertions(+), 58 deletions(-)
 create mode 100644 drivers/gpu/drm/drm_afbc.c
 create mode 100644 include/drm/drm_afbc.h

-- 
2.17.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-10-11 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 11:18 Andrzej Pietrasiewicz [this message]
2019-10-11 11:18 ` [PATCH 1/2] drm/arm: Factor out generic afbc helpers Andrzej Pietrasiewicz
2019-10-21 13:50   ` Ayan Halder
2019-10-21 14:41     ` Mihail Atanassov
2019-10-11 11:18 ` [PATCH 2/2] drm/rockchip: Add support for afbc Andrzej Pietrasiewicz
2019-10-11 11:59   ` Daniel Stone

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=20191011111813.20851-1-andrzej.p@collabora.com \
    --to=andrzej.p@collabora$(echo .)com \
    --cc=airlied@linux$(echo .)ie \
    --cc=brian.starkey@arm$(echo .)com \
    --cc=daniel@ffwll$(echo .)ch \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=heiko@sntech$(echo .)de \
    --cc=hjc@rock-chips$(echo .)com \
    --cc=kernel@collabora$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-rockchip@lists$(echo .)infradead.org \
    --cc=liviu.dudau@arm$(echo .)com \
    --cc=maarten.lankhorst@linux$(echo .)intel.com \
    --cc=mripard@kernel$(echo .)org \
    --cc=sean@poorly$(echo .)run \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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