Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "Syrjala, Ville" <ville.syrjala@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [Intel-gfx] [Intel-xe] [PATCH v5 0/2] fbc on any planes
Date: Mon, 25 Sep 2023 13:01:49 +0000	[thread overview]
Message-ID: <660dcc0d9e69a1ba538b397bd0943abe462db294.camel@intel.com> (raw)
In-Reply-To: <87sf72morn.fsf@intel.com>

On Mon, 2023-09-25 at 15:16 +0300, Jani Nikula wrote:
> On Fri, 22 Sep 2023, Vinod Govindapillai <vinod.govindapillai@intel.com> wrote:
> > FBC can be supported in first three planes in lnl
> 
> When you're cross-posting to intel-xe and intel-gfx lists, you need to
> actually say what you want done with these patches. Otherwise we won't
> know.
> 
> Before xe is upstream, the order of business for i915 changes should be:
> 
> 1) Get them merged to upstream i915 (send to intel-gfx)
> 
> 2) Get the merged commits backported to xe (send to intel-xe)
> 
> 
> BR,
> Jani.

Okay. I was following the [https://gfx-linux.intel.com/xe.html]
Here I assumed the flow as you have mentioned.

Lucas has asked to hold off merging until the initial display support is merged.

So wonder if I should take first internal and then upstream route for this.


BR
Vinod

> 
> > 
> > Vinod Govindapillai (2):
> >   drm/i915/lnl: possibility to enable FBC on first three planes
> >   drm/i915/lnl: update the supported plane formats with FBC
> > 
> >  drivers/gpu/drm/i915/display/intel_fbc.c           | 11 ++++++++++-
> >  drivers/gpu/drm/i915/display/skl_universal_plane.c |  9 ++++++---
> >  drivers/gpu/drm/i915/i915_reg.h                    |  2 ++
> >  3 files changed, 18 insertions(+), 4 deletions(-)
> 


  reply	other threads:[~2023-09-25 13:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 13:30 [Intel-gfx] [PATCH v5 0/2] fbc on any planes Vinod Govindapillai
2023-09-22 13:30 ` [Intel-gfx] [PATCH v5 1/2] drm/i915/lnl: possibility to enable FBC on first three planes Vinod Govindapillai
2023-09-22 13:30 ` [Intel-gfx] [PATCH v5 2/2] drm/i915/lnl: update the supported plane formats with FBC Vinod Govindapillai
2023-09-23  1:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for fbc on any planes (rev3) Patchwork
2023-09-23  1:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-23  1:51 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-09-28 15:55   ` Ville Syrjälä
2023-09-28 17:32     ` Govindapillai, Vinod
2023-09-25 12:16 ` [Intel-gfx] [Intel-xe] [PATCH v5 0/2] fbc on any planes Jani Nikula
2023-09-25 13:01   ` Govindapillai, Vinod [this message]
2023-09-29  7:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success for fbc on any planes (rev3) Patchwork
2023-09-29 11:49 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-01  9:07   ` Govindapillai, Vinod
2023-10-03 12:58 ` [Intel-gfx] [Intel-xe] [PATCH v5 0/2] fbc on any planes Ville Syrjälä

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=660dcc0d9e69a1ba538b397bd0943abe462db294.camel@intel.com \
    --to=vinod.govindapillai@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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