From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, lucas.demarchi@intel.com,
uma.shankar@intel.com, rodrigo.vivi@intel.com,
"Jouni Högander" <jouni.hogander@intel.com>
Subject: [Intel-xe] [PATCH 4/4] fixup! drm/xe/display: Implement display support
Date: Mon, 15 May 2023 12:46:14 +0300 [thread overview]
Message-ID: <20230515094614.1850878-5-jouni.hogander@intel.com> (raw)
In-Reply-To: <20230515094614.1850878-1-jouni.hogander@intel.com>
Now we have struct intel_frontbuffer pointer in intel_fb for Xe as
well. Handle setting frontbuffer bit same way as done in i915.
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
next prev parent reply other threads:[~2023-05-15 9:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 9:46 [Intel-xe] [PATCH 0/4] Revert frontbuffer tracking removal Jouni Högander
2023-05-15 9:46 ` [Intel-xe] [PATCH 1/4] Revert "drm/i915/display: Neuter frontbuffer tracking harder" Jouni Högander
2023-05-15 9:46 ` [Intel-xe] [PATCH 2/4] Revert "drm/i915: Remove gem and overlay frontbuffer tracking" Jouni Högander
2023-05-15 9:46 ` [Intel-xe] [PATCH 3/4] fixup! drm/i915/display: Remaining changes to make xe compile Jouni Högander
2023-05-15 9:46 ` Jouni Högander [this message]
2023-05-15 9:48 ` [Intel-xe] ✓ CI.Patch_applied: success for Revert frontbuffer tracking removal Patchwork
2023-05-15 9:51 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-15 9:55 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-15 10:18 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-05-18 19:52 ` [Intel-xe] [PATCH 0/4] " Rodrigo Vivi
2023-05-19 7:43 ` Hogander, Jouni
-- strict thread matches above, loose matches on Subject: below --
2023-05-16 13:32 [Intel-xe] [PATCH 0/4] drm/xe: use hotplug irq code from i915 Jani Nikula
2023-05-16 13:32 ` [Intel-xe] [PATCH 4/4] fixup! drm/xe/display: Implement display support Jani Nikula
2023-05-16 20:58 ` Rodrigo Vivi
2023-05-17 8:04 ` Jani Nikula
2023-07-04 15:32 [Intel-xe] [PATCH 0/4] drm/xe/display: reuse soc/ code from i915 Jani Nikula
2023-07-04 15:32 ` [Intel-xe] [PATCH 4/4] fixup! drm/xe/display: Implement display support Jani Nikula
2023-09-18 7:00 [Intel-xe] [PATCH 0/4] Xe runtime pm refactoring Jouni Högander
2023-09-18 7:01 ` [Intel-xe] [PATCH 4/4] fixup! drm/xe/display: Implement display support Jouni Högander
2023-09-18 21:22 ` Govindapillai, Vinod
2023-11-09 16:17 [Intel-xe] [PATCH 0/4] xe&i915 display pxp cleanup Jani Nikula
2023-11-09 16:17 ` [Intel-xe] [PATCH 4/4] fixup! drm/xe/display: Implement display support Jani Nikula
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=20230515094614.1850878-5-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=uma.shankar@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