All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Geffon <bgeffon@google.com>
To: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	ville.syrjala@linux.intel.com, uma.shankar@intel.com,
	pranay.samala@intel.com, radford@google.com, gildekel@google.com,
	seanpaul@google.com
Subject: Re: [PATCH v3 0/4] More Fixes for color pipeline
Date: Thu, 28 May 2026 22:27:57 +0000	[thread overview]
Message-ID: <ahjBbUwF_8jcXKHY@google.com> (raw)
In-Reply-To: <20260511053213.3122314-1-chaitanya.kumar.borah@intel.com>

On Mon, May 11, 2026 at 11:02:09AM +0530, Chaitanya Kumar Borah wrote:
> v3:
> - Re-arrange patches

We've been impacted by this on PTL devices. Ray has tested and can
provide more details.

In the meantime can we ask that a maintainer take a look?

> 
> v2:
> - Make dependency on atomic state more explicit (Ville)
> - handle blobs in hw state clear
> 
> Chaitanya Kumar Borah (4):
>   drm/i915/display: Copy color pipeline from plane in the primary joiner
>     pipe
>   drm/i915/display: Don’t use atomic state back-pointer to derive color
>     pipeline
>   drm/i915: Avoid programming color HW blocks for NV12 Y planes
>   drm/i915: Fix color blob reference handling in intel_plane_state
> 
>  drivers/gpu/drm/i915/display/intel_cursor.c   |  2 +-
>  .../drm/i915/display/intel_initial_plane.c    |  2 +-
>  drivers/gpu/drm/i915/display/intel_plane.c    | 77 ++++++++++++++-----
>  drivers/gpu/drm/i915/display/intel_plane.h    |  5 +-
>  4 files changed, 61 insertions(+), 25 deletions(-)
>

Thanks!
Brian

> -- 
> 2.25.1
> 

  parent reply	other threads:[~2026-05-28 22:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  5:32 [PATCH v3 0/4] More Fixes for color pipeline Chaitanya Kumar Borah
2026-05-11  5:32 ` [PATCH v3 1/4] drm/i915/display: Copy color pipeline from plane in the primary joiner pipe Chaitanya Kumar Borah
2026-05-12  9:58   ` Shankar, Uma
2026-05-11  5:32 ` [PATCH v3 2/4] drm/i915/display: Don’t use atomic state back-pointer to derive color pipeline Chaitanya Kumar Borah
2026-05-31 18:20   ` Shankar, Uma
2026-05-11  5:32 ` [PATCH v3 3/4] drm/i915: Avoid programming color HW blocks for NV12 Y planes Chaitanya Kumar Borah
2026-05-12 10:51   ` Jani Nikula
2026-05-11  5:32 ` [PATCH v3 4/4] drm/i915: Fix color blob reference handling in intel_plane_state Chaitanya Kumar Borah
2026-05-28 23:16   ` Sean Paul
2026-06-01  8:16     ` Borah, Chaitanya Kumar
2026-05-11 13:35 ` ✗ CI.checkpatch: warning for More Fixes for color pipeline Patchwork
2026-05-11 13:38 ` ✓ CI.KUnit: success " Patchwork
2026-05-11 14:47 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-11 16:02 ` ✓ Xe.CI.FULL: " Patchwork
2026-05-11 16:59 ` ✓ i915.CI.BAT: " Patchwork
2026-05-11 22:53 ` ✗ i915.CI.Full: failure " Patchwork
2026-05-12 14:16 ` ✓ i915.CI.Full: success " Patchwork
2026-05-28 22:27 ` Brian Geffon [this message]
2026-05-28 22:35   ` [PATCH v3 0/4] " Ray Juang

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=ahjBbUwF_8jcXKHY@google.com \
    --to=bgeffon@google.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=gildekel@google.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=pranay.samala@intel.com \
    --cc=radford@google.com \
    --cc=seanpaul@google.com \
    --cc=uma.shankar@intel.com \
    --cc=ville.syrjala@linux.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 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.