From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Sean Paul <sean@poorly.run>
Cc: dim-tools@lists.freedesktop.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PULL] topic/hdr-formats
Date: Thu, 7 Mar 2019 10:48:24 +0100 [thread overview]
Message-ID: <f2485309-d645-bed4-95f4-e66ff312aa05@linux.intel.com> (raw)
Hi Sean and Joonas,
Here's a pull request for HDR format enabling in i915. Can this be pulled to drm-misc-next and dinq?
Cheers,
Maarten
topic/hdr-formats-2019-03-07:
Add support for Y21x and Y41x to drm core and i915, and P01x support to i915.
The following changes since commit 4b057e73f28f1df13b77b77a52094238ffdf8abd:
Merge tag 'drm-misc-fixes-2019-02-22' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2019-03-05 08:14:22 +1000)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-misc tags/topic/hdr-formats-2019-03-07
for you to fetch changes up to 296e9b19eff6157e1e4f130fa436e105c45725e9:
drm/i915/icl: Enabling Y2xx and Y4xx (xx:10/12/16) formats for universal planes (2019-03-05 12:49:00 +0100)
----------------------------------------------------------------
Add support for Y21x and Y41x to drm core and i915, and P01x support to i915.
----------------------------------------------------------------
Juha-Pekka Heikkila (3):
drm/i915: Add P010, P012, P016 plane control definitions
drm/i915: Preparations for enabling P010, P012, P016 formats
drm/i915: Enable P010, P012, P016 formats for primary and sprite planes
Swati Sharma (3):
drm: Add Y2xx and Y4xx (xx:10/12/16) format definitions and fourcc
drm/i915/icl: Add Y2xx and Y4xx (xx:10/12/16) plane control definitions
drm/i915/icl: Enabling Y2xx and Y4xx (xx:10/12/16) formats for universal planes
drivers/gpu/drm/drm_fourcc.c | 6 ++
drivers/gpu/drm/i915/i915_reg.h | 9 +++
drivers/gpu/drm/i915/intel_atomic_plane.c | 2 +-
drivers/gpu/drm/i915/intel_display.c | 57 ++++++++++++++--
drivers/gpu/drm/i915/intel_drv.h | 1 +
drivers/gpu/drm/i915/intel_pm.c | 14 ++--
drivers/gpu/drm/i915/intel_sprite.c | 108 ++++++++++++++++++++++++++++--
include/uapi/drm/drm_fourcc.h | 16 +++++
8 files changed, 194 insertions(+), 19 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-07 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 9:48 Maarten Lankhorst [this message]
2019-03-07 17:12 ` [PULL] topic/hdr-formats Adam Jackson
2019-03-11 11:19 ` Maarten Lankhorst
2019-03-11 17:52 ` Adam Jackson
2019-03-11 18:02 ` Daniel Vetter
2019-03-07 17:46 ` Sean Paul
2019-03-08 12:45 ` Maarten Lankhorst
2019-03-08 15:40 ` Sean Paul
2019-03-11 11:57 ` Joonas Lahtinen
2019-03-11 12:05 ` Maarten Lankhorst
-- strict thread matches above, loose matches on Subject: below --
2019-03-13 11:21 Maarten Lankhorst
2019-03-13 18:20 ` Sean Paul
2019-03-18 15:22 ` Joonas Lahtinen
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=f2485309-d645-bed4-95f4-e66ff312aa05@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=rodrigo.vivi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.