From: Imre Deak <imre.deak@intel.com>
To: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
rodrigo.vivi@intel.com, maarten.lankhorst@linux.intel.com
Subject: Re: [PATCH v3] drm/i915/display: Fix BMG CCS modifiers
Date: Wed, 4 Sep 2024 14:54:50 +0300 [thread overview]
Message-ID: <ZthKitcktaEq8VnR@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20240902074021.459480-1-juhapekka.heikkila@gmail.com>
On Mon, Sep 02, 2024 at 10:40:21AM +0300, Juha-Pekka Heikkila wrote:
> Let I915_FORMAT_MOD_4_TILED_BMG_CCS show up as supported modifier
>
> Fixes: 97c6efb36497 ("drm/i915/display: Plane capability for 64k phys alignment")
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---
> drivers/gpu/drm/i915/display/skl_universal_plane.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/skl_universal_plane.c b/drivers/gpu/drm/i915/display/skl_universal_plane.c
> index 9452cad41d07..17d4c880ecc4 100644
> --- a/drivers/gpu/drm/i915/display/skl_universal_plane.c
> +++ b/drivers/gpu/drm/i915/display/skl_universal_plane.c
> @@ -2453,6 +2453,9 @@ static u8 skl_get_plane_caps(struct drm_i915_private *i915,
> if (gen12_plane_has_mc_ccs(i915, plane_id))
> caps |= INTEL_PLANE_CAP_CCS_MC;
>
> + if (DISPLAY_VER(i915) >= 14 && IS_DGFX(i915))
> + caps |= INTEL_PLANE_CAP_NEED64K_PHYS;
> +
With the simplification in plane_has_modifier() discussed earlier
removing the BMG/LNL checks as a follow-up this looks ok:
Reviewed-by: Imre Deak <imre.deak@intel.com>
> return caps;
> }
>
> --
> 2.45.2
>
prev parent reply other threads:[~2024-09-04 11:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 7:40 [PATCH v3] drm/i915/display: Fix BMG CCS modifiers Juha-Pekka Heikkila
2024-09-02 8:15 ` ✓ CI.Patch_applied: success for drm/i915/display: Fix BMG CCS modifiers (rev3) Patchwork
2024-09-02 8:15 ` ✓ CI.checkpatch: " Patchwork
2024-09-02 8:17 ` ✓ CI.KUnit: " Patchwork
2024-09-02 8:28 ` ✓ CI.Build: " Patchwork
2024-09-02 8:31 ` ✓ CI.Hooks: " Patchwork
2024-09-02 8:32 ` ✗ CI.checksparse: warning " Patchwork
2024-09-02 8:51 ` ✓ CI.BAT: success " Patchwork
2024-09-02 10:19 ` ✗ CI.FULL: failure " Patchwork
2024-09-04 9:42 ` Juha-Pekka Heikkila
2024-09-04 11:54 ` Imre Deak [this message]
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=ZthKitcktaEq8VnR@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=rodrigo.vivi@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