Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: "Souza, Jose" <jose.souza@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/display: Disable AuxCCS framebuffers if built for Xe
Date: Thu, 25 Jan 2024 17:56:06 +0200	[thread overview]
Message-ID: <78627f64-0f6e-430b-a954-30bec402b132@gmail.com> (raw)
In-Reply-To: <c7209d47d99a35d08a96e6a302595e4854b1d543.camel@intel.com>

On 25.1.2024 17.28, Souza, Jose wrote:
> On Thu, 2024-01-25 at 17:25 +0200, Juha-Pekka Heikkila wrote:
>> AuxCCS framebuffers don't work on Xe driver hence disable them
>> from plane capabilities until they are fixed. FlatCCS framebuffers
>> work and they are left enabled. CCS is left untouched for i915
>> deriver.
>>
>> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/933
>> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
>> ---
>>   drivers/gpu/drm/i915/display/skl_universal_plane.c | 8 ++++++++
>>   1 file changed, 8 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/skl_universal_plane.c b/drivers/gpu/drm/i915/display/skl_universal_plane.c
>> index 511dc1544854..1521d829525a 100644
>> --- a/drivers/gpu/drm/i915/display/skl_universal_plane.c
>> +++ b/drivers/gpu/drm/i915/display/skl_universal_plane.c
>> @@ -2290,6 +2290,14 @@ static u8 skl_get_plane_caps(struct drm_i915_private *i915,
>>   	if (HAS_4TILE(i915))
>>   		caps |= INTEL_PLANE_CAP_TILING_4;
>>   
>> +	/*
>> +	 * FIXME: Below if(IS_ENABLED(CONFIG_I915)..) is because Xe driver
>> +	 * can't use AuxCCS framebuffers. Once they are fixed this need to be
>> +	 * removed.
>> +	 */
>> +	if (!IS_ENABLED(CONFIG_I915) && !HAS_FLAT_CCS(i915))
>> +		return caps;
>> +
> 
> functional but looks odd.
> would rather add a check inside of gen12_plane_has_mc_ccs() or 'if ((!IS_ENABLED(CONFIG_I915) && !HAS_FLAT_CCS(i915)) && gen12_plane_has_mc_ccs(i915,
> plane_id))'

Hi Jose,

not sure I understood your idea. Here need to be disabled all versions 
of aux ccs for Xe, not just mc ccs.

> 
>>   	if (skl_plane_has_rc_ccs(i915, pipe, plane_id)) {
>>   		caps |= INTEL_PLANE_CAP_CCS_RC;
>>   		if (DISPLAY_VER(i915) >= 12)
> 


  reply	other threads:[~2024-01-25 15:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 15:25 [PATCH] drm/i915/display: Disable AuxCCS framebuffers if built for Xe Juha-Pekka Heikkila
2024-01-25 15:28 ` Souza, Jose
2024-01-25 15:56   ` Juha-Pekka Heikkila [this message]
2024-01-25 16:07     ` Souza, Jose
2024-02-02 20:51       ` Souza, Jose
2024-02-05 10:00         ` Juha-Pekka Heikkila
2024-01-25 16:00 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-01-25 17:23 ` ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26 20:36 [PATCH] " Juha-Pekka Heikkila
2024-02-27  8:57 ` Jani Nikula
2024-02-28 14:02 Juha-Pekka Heikkila
2024-02-28 14:04 ` Souza, Jose
2024-02-29 16:44   ` Souza, Jose
2024-02-29 17:36     ` Souza, Jose
2024-03-05 16:44 ` Jani Nikula
2025-01-28 13:08   ` Tvrtko Ursulin
2025-01-28 15:55     ` Juha-Pekka Heikkilä
2025-01-29  8:44       ` Tvrtko Ursulin
2025-01-29 15:20         ` Juha-Pekka Heikkilä
2024-03-06 13:57 ` Souza, Jose

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=78627f64-0f6e-430b-a954-30bec402b132@gmail.com \
    --to=juhapekka.heikkila@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jose.souza@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