All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Hogander, Jouni" <jouni.hogander@intel.com>
Cc: "rodrigo.vivi@kernel.org" <rodrigo.vivi@kernel.org>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Subject: Re: [Intel-xe] [RFC PATCH 04/20] fixup! drm/xe/display: Implement display support
Date: Mon, 8 May 2023 09:35:16 -0400	[thread overview]
Message-ID: <ZFj6lOUI6J0jv46K@intel.com> (raw)
In-Reply-To: <2fd68f32e780c1c1436a45b410dfb4e903bdf0b2.camel@intel.com>

On Mon, May 08, 2023 at 09:19:48AM +0000, Hogander, Jouni wrote:
> On Fri, 2023-05-05 at 10:44 -0400, Rodrigo Vivi wrote:
> > 
> > I believe we could already start merging patches 1-4, no?!
> 
> Patches 1-4 alone are currently breaking build. I can fix that. 

That shouldn't ever happen anyway.

Every single patch needs to build and be self-sufficient, otherwise
we break bisects and auto-bisects.

> 
> Generally: in current form GPU frontbuffer rendering + PSR,FBC doesn't
> work with Xe driver in drm-xe-next branch. Additionally it is breaking
> it for i915 as well. If patches 1-4 are applied i915 GPU frontbuffer
> rendering + PSR,FBC is not broken anymore. Drawback is that neither CPU
> or GPU fronbuffer rendering + PSR,FBC is working anymore with Xe
> driver. Subsequent patches are fixing that.
> > 
> > Maarten?
> > 
> > On Fri, May 05, 2023 at 11:29:40AM +0300, Jouni Högander wrote:
> > > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > > ---
> > >  drivers/gpu/drm/xe/display/xe_plane_initial.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/gpu/drm/xe/display/xe_plane_initial.c
> > > b/drivers/gpu/drm/xe/display/xe_plane_initial.c
> > > index d0f91f37b6d8..34ae461865a7 100644
> > > --- a/drivers/gpu/drm/xe/display/xe_plane_initial.c
> > > +++ b/drivers/gpu/drm/xe/display/xe_plane_initial.c
> > > @@ -228,7 +228,7 @@ intel_find_initial_plane_obj(struct intel_crtc
> > > *crtc,
> > >         plane_state->uapi.crtc = &crtc->base;
> > >         intel_plane_copy_uapi_to_hw_state(plane_state, plane_state,
> > > crtc);
> > >  
> > > -       atomic_or(plane->frontbuffer_bit,
> > > &to_intel_framebuffer(fb)->bits);
> > > +       atomic_or(plane->frontbuffer_bit,
> > > &to_intel_frontbuffer(fb)->bits);
> > >  
> > >         plane_config->vma = vma;
> > >  
> > > -- 
> > > 2.34.1
> > > 
> 

  reply	other threads:[~2023-05-08 13:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05  8:29 [Intel-xe] [RFC PATCH 00/20] Xe frontbuffer tracking Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 01/20] Revert "drm/i915/display: Neuter frontbuffer tracking harder" Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 02/20] Revert "drm/i915: Remove gem and overlay frontbuffer tracking" Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 03/20] fixup! drm/i915/display: Remaining changes to make xe compile Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 04/20] fixup! drm/xe/display: Implement display support Jouni Högander
2023-05-05 14:44   ` Rodrigo Vivi
2023-05-08  9:19     ` Hogander, Jouni
2023-05-08 13:35       ` Rodrigo Vivi [this message]
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 05/20] drm/i915/display: Change __intel_frontbuffer_get parameter Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 06/20] drm/i915: Add macros to get i915 device from i915_gem_object Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 07/20] drm/xe: Add macro to get i915 device from xe_bo Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 08/20] drm/xe: Add intel_bo_flush_if_display define for Xe Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 09/20] drm/i915: Add intel_bo_flush_if_display define for i915 Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 10/20] drm/xe: Add struct i915_active for Xe Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 11/20] drm/xe: Add i915_active.h compatibility header Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 12/20] drm/xe/display: Include i916_active related headers Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 13/20] drm/i915: Add function to clear scanout flag for vmas Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 14/20] drm/xe: Add function to clear scanout flag Jouni Högander
2023-05-05  8:43   ` Maarten Lankhorst
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 15/20] drm/i915/display: Use i915_ggtt_clear_scanout Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 16/20] drm/i915/display: Use drm_gem_object_get/put Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 17/20] drm/xe/display: Use frontbuffer tracking for Xe as well Jouni Högander
2023-05-05  8:50   ` Maarten Lankhorst
2023-05-05 11:39     ` Hogander, Jouni
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 18/20] drm/i915: Add new frontbuffer tracking interface to queue flush Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 19/20] drm/i915: Handle dma fences in dirtyfb callback Jouni Högander
2023-05-05  8:29 ` [Intel-xe] [RFC PATCH 20/20] drm/xe/display: Use custom dirtyfb for Xe as well Jouni Högander
2023-05-05  8:34 ` [Intel-xe] ✓ CI.Patch_applied: success for Xe frontbuffer tracking Patchwork
2023-05-05  8:35 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-05  8:38 ` [Intel-xe] ✗ CI.Build: failure " Patchwork

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=ZFj6lOUI6J0jv46K@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=jouni.hogander@intel.com \
    --cc=rodrigo.vivi@kernel.org \
    --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.