Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Paul <sean@poorly.run>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: dim-tools@lists.freedesktop.org,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Sean Paul <sean@poorly.run>,
	intel-gfx@lists.freedesktop.org,
	Kevin Strasser <kevin.strasser@intel.com>,
	dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PULL] topic/hdr-formats
Date: Wed, 13 Mar 2019 14:20:01 -0400	[thread overview]
Message-ID: <20190313182001.GK114153@art_vandelay> (raw)
In-Reply-To: <00b96cd5-91c7-5677-9620-b138c7a92303@linux.intel.com>

On Wed, Mar 13, 2019 at 12:21:46PM +0100, Maarten Lankhorst wrote:
> Hey Sean and Joonas,
> 
> One more pull request for the hdr-formats topic branch. FP16 support
> is now also implemented.
> 
> Can this be pulled to drm-misc-next and dinq?

Merged in drm-misc-next.

Sean

> 
> ~Maarten
> 
> topic/hdr-formats-2019-03-13:
> Add support for floating point half-width formats.
> The following changes since commit 296e9b19eff6157e1e4f130fa436e105c45725e9:
> 
>   drm/i915/icl: Enabling Y2xx and Y4xx (xx:10/12/16) formats for universal planes (2019-03-05 12:49:00 +0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/topic/hdr-formats-2019-03-13
> 
> for you to fetch changes up to a94bed60cb73962f344ead14b2ee7613280432c6:
> 
>   drm/i915/icl: Implement half float formats (2019-03-13 11:23:12 +0100)
> 
> ----------------------------------------------------------------
> Add support for floating point half-width formats.
> 
> ----------------------------------------------------------------
> Kevin Strasser (3):
>       drm/fourcc: Add 64 bpp half float formats
>       drm/i915: Refactor icl_is_hdr_plane
>       drm/i915/icl: Implement half float formats
> 
>  drivers/gpu/drm/drm_fourcc.c         |  4 ++
>  drivers/gpu/drm/i915/intel_atomic.c  |  3 +-
>  drivers/gpu/drm/i915/intel_display.c | 29 +++++++++++++-
>  drivers/gpu/drm/i915/intel_drv.h     |  7 ++--
>  drivers/gpu/drm/i915/intel_sprite.c  | 78 +++++++++++++++++++++++++++++++++---
>  include/uapi/drm/drm_fourcc.h        | 11 +++++
>  6 files changed, 120 insertions(+), 12 deletions(-)

-- 
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-03-13 18:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 11:21 [PULL] topic/hdr-formats Maarten Lankhorst
2019-03-13 18:20 ` Sean Paul [this message]
2019-03-18 15:22 ` Joonas Lahtinen
  -- strict thread matches above, loose matches on Subject: below --
2019-03-07  9:48 Maarten Lankhorst
2019-03-07 17:12 ` 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

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=20190313182001.GK114153@art_vandelay \
    --to=sean@poorly.run \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kevin.strasser@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=rodrigo.vivi@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