public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Starkey <brian.starkey@arm.com>
To: dri-devel@lists.freedesktop.org, daniel.vetter@ffwll.ch,
	daniel@fooishbar.org, airlied@linux.ie, gustavo@padovan.org,
	maarten.lankhorst@linux.intel.com, seanpaul@chromium.org
Cc: linux-kernel@vger.kernel.org, alexandru-cosmin.gheorghe@arm.com,
	liviu.dudau@arm.com, ayan.halder@arm.com, tfiga@chromium.org,
	hoegsberg@chromium.org
Subject: [RFC PATCH v2 0/3] Groundwork for AFBC YUV formats
Date: Thu, 23 Aug 2018 16:23:40 +0100	[thread overview]
Message-ID: <20180823152343.6474-1-brian.starkey@arm.com> (raw)

Hi,

This is the second round of RFC for adding a bunch of new YUV formats
for Mali/AFBC. I've included a proper AFBC documentation file too, for
posterity.

Some of the new formats don't have an integer number of
bytes-per-pixel, so I've added a bpp field to drm_format_info
(patch 1), keen to hear thoughts on that.

These three patches don't make a huge amount of sense in isolation, so
we'll pull them into a more comprehensive series for AFBC support to
merge them later.

Thanks,
-Brian

Brian Starkey (3):
  drm/fourcc: Add 'bpp' field for formats with non-integer
    bytes-per-pixel
  drm/fourcc: Add remaining fourccs for Mali
  drm/afbc: Add AFBC modifier usage documentation

 Documentation/gpu/afbc.rst                   | 226 +++++++++++++++++++++++++++
 Documentation/gpu/drivers.rst                |   1 +
 MAINTAINERS                                  |   1 +
 drivers/gpu/drm/drm_fb_cma_helper.c          |   6 +-
 drivers/gpu/drm/drm_fb_helper.c              |   8 +-
 drivers/gpu/drm/drm_fourcc.c                 |  57 +++++++
 drivers/gpu/drm/drm_framebuffer.c            |  41 ++++-
 drivers/gpu/drm/drm_gem_framebuffer_helper.c |   3 +-
 include/drm/drm_fourcc.h                     |   4 +
 include/uapi/drm/drm_fourcc.h                |  17 ++
 10 files changed, 351 insertions(+), 13 deletions(-)
 create mode 100644 Documentation/gpu/afbc.rst

-- 
2.16.1


             reply	other threads:[~2018-08-23 15:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 15:23 Brian Starkey [this message]
2018-08-23 15:23 ` [RFC PATCH v2 1/3] drm/fourcc: Add 'bpp' field for formats with non-integer bytes-per-pixel Brian Starkey
2018-08-31  8:17   ` Daniel Vetter
2018-09-07 12:45     ` Brian Starkey
2018-09-07 19:28       ` Daniel Vetter
2018-09-10  8:50         ` Brian Starkey
2018-09-10 19:53           ` Daniel Vetter
2018-09-12 13:52             ` Brian Starkey
2018-09-12 18:21               ` Daniel Vetter
2018-09-12 15:27             ` Liviu Dudau
2018-09-12 15:40               ` Brian Starkey
2018-09-12 18:24               ` Daniel Vetter
2018-09-10 14:11     ` Ayan Halder
2018-09-10 14:25       ` Brian Starkey
2018-08-23 15:23 ` [RFC PATCH v2 2/3] drm/fourcc: Add remaining fourccs for Mali Brian Starkey
2018-08-23 15:23 ` [RFC PATCH v2 3/3] drm/afbc: Add AFBC modifier usage documentation Brian Starkey

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=20180823152343.6474-1-brian.starkey@arm.com \
    --to=brian.starkey@arm.com \
    --cc=airlied@linux.ie \
    --cc=alexandru-cosmin.gheorghe@arm.com \
    --cc=ayan.halder@arm.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo@padovan.org \
    --cc=hoegsberg@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=seanpaul@chromium.org \
    --cc=tfiga@chromium.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