public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "Peres, Martin" <martin.peres@intel.com>,
	"Syrjala, Ville" <ville.syrjala@intel.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Heikkila, Juha-pekka" <juha-pekka.heikkila@intel.com>
Subject: Re: [PATCH v10 0/2] Add XYUV format support
Date: Fri, 14 Sep 2018 13:36:32 +0000	[thread overview]
Message-ID: <e6cc989505f5688cd5de445265a0fa178e4f1760.camel@intel.com> (raw)
In-Reply-To: <20180907084520.6349-1-stanislav.lisovskiy@intel.com>

On Fri, 2018-09-07 at 11:45 +0300, Stanislav Lisovskiy wrote:
> Introduced new XYUV scan-in format for framebuffer and
> added support for it to i915(SkyLake+).
> 
> Stanislav Lisovskiy (2):
>   drm: Introduce new DRM_FORMAT_XYUV
>   drm/i915: Adding YUV444 packed format support for skl+
> 
>  drivers/gpu/drm/drm_fourcc.c         |  1 +
>  drivers/gpu/drm/i915/i915_reg.h      |  2 +-
>  drivers/gpu/drm/i915/intel_display.c | 15 +++++++++++++++
>  drivers/gpu/drm/i915/intel_sprite.c  |  2 ++
>  include/uapi/drm/drm_fourcc.h        |  1 +
>  5 files changed, 20 insertions(+), 1 deletion(-)
> 

Ping. There is an IGT patch which got Reviewed-by Ville.
This one left in order to get XYUV support. 

-- 
Best Regards,

Lisovskiy Stanislav
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-09-14 13:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07  8:45 [PATCH v10 0/2] Add XYUV format support Stanislav Lisovskiy
2018-09-07  8:45 ` [PATCH v10 1/2] drm: Introduce new DRM_FORMAT_XYUV Stanislav Lisovskiy
2018-09-07  8:45 ` [PATCH v10 2/2] drm/i915: Adding YUV444 packed format support for skl+ Stanislav Lisovskiy
2018-09-07  9:00 ` ✗ Fi.CI.CHECKPATCH: warning for Add XYUV format support (rev6) Patchwork
2018-09-07  9:23 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-07 11:37 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-09-07 15:21   ` Martin Peres
2018-09-10  7:38     ` Lisovskiy, Stanislav
2018-09-12 13:29 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-12 18:55 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-14 13:36 ` Lisovskiy, Stanislav [this message]
2018-09-14 13:47   ` [PATCH v10 0/2] Add XYUV format support Ville Syrjälä
2018-09-14 14:30     ` Lisovskiy, Stanislav
2018-09-14 14:34       ` Saarinen, Jani
2018-09-14 14:49         ` [Intel-gfx] " Lisovskiy, Stanislav
2018-09-14 14:59           ` Alexandru-Cosmin Gheorghe
2018-09-17  8:27             ` [Intel-gfx] " Lisovskiy, Stanislav
2018-09-17  8:49               ` Alexandru-Cosmin Gheorghe
2018-09-14 17:05       ` Juha-Pekka Heikkilä
2018-09-17  8:25         ` [Intel-gfx] " Lisovskiy, Stanislav
2018-09-17  8:51           ` Juha-Pekka Heikkila
  -- strict thread matches above, loose matches on Subject: below --
2018-10-02 11:15 Stanislav Lisovskiy

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=e6cc989505f5688cd5de445265a0fa178e4f1760.camel@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=juha-pekka.heikkila@intel.com \
    --cc=martin.peres@intel.com \
    --cc=ville.syrjala@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