From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Julia Filipchuk <julia.filipchuk@intel.com>
Subject: Re: [PATCH 0/3] Enable GSC loading and PXP for PTL
Date: Mon, 12 Jan 2026 10:03:54 -0800 [thread overview]
Message-ID: <511b6ae1-0bd6-4e31-8aa5-e039d2d7f817@intel.com> (raw)
In-Reply-To: <aV_BA4BlDMgn2IUs@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
On 1/8/2026 6:36 AM, Rodrigo Vivi wrote:
> On Wed, Jan 07, 2026 at 05:13:41PM -0800, Daniele Ceraolo Spurio wrote:
>> GSC loading is required for content protection features (PXP, HDCP).
>>
>> Since PTL force_probe was removed before we added the FW, the driver
>> needs to keep working if the FW is not found. Therefore, the code has
>> been modified to allow the GSC FW to be missing for BMG and newer HW
>> (older HW platforms require GSC for power management, so on those we
>> don't want to continue if the FW is missing).
>>
>> Note that I haven't pushed the FW yet. This is on purpose, as I want to
>> get CI with the FW missing to test that case. Once the patches have been
>> reviewed and tested without the FW, I'll push the FW to intel-staging
>> and re-trigger CI to make sure everything works with the FW as well.
>
> Acked-by: Rodrigo Vivi<rodrigo.vivi@intel.com>
>
> on both, the optional approach proposed by the first patch and on
> the CI approach you took here.
I've re-run CI and no regression have popped up both without [1] and
with [2] the FW.
[1] https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-159774v1/index.html?
xe 0000:00:02.0: [drm] Tile0: GT1: GSC firmware xe/ptl_gsc_1.bin not found
xe 0000:00:02.0: [drm] Tile0: GT1: GSC firmware(s) can be downloaded from ...
[2] https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-159774v3/index.html?
xe 0000:00:02.0: [drm] Tile0: GT1: Using GSC firmware from xe/ptl_gsc_1.bin version 105.0.2.1301
I've also sent the PR for the FW to linux-firmware:
https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/858
So I'm going to go ahead and merge this.
Daniele
>
>> Cc: Rodrigo Vivi<rodrigo.vivi@intel.com>
>> Cc: Julia Filipchuk<julia.filipchuk@intel.com>
>>
>> Daniele Ceraolo Spurio (3):
>> drm/xe/gsc: Make GSC FW load optional for newer platforms
>> drm/xe/ptl: Define GSC for PTL
>> drm/xe/ptl: Enable PXP for PTL
>>
>> drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 2 +-
>> drivers/gpu/drm/xe/xe_gsc.c | 13 +++++++------
>> drivers/gpu/drm/xe/xe_pci.c | 1 +
>> drivers/gpu/drm/xe/xe_uc_fw.c | 11 ++++++++---
>> 4 files changed, 17 insertions(+), 10 deletions(-)
>>
>> --
>> 2.43.0
>>
[-- Attachment #2: Type: text/html, Size: 4472 bytes --]
next prev parent reply other threads:[~2026-01-12 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 1:13 [PATCH 0/3] Enable GSC loading and PXP for PTL Daniele Ceraolo Spurio
2026-01-08 1:13 ` [PATCH 1/3] drm/xe/gsc: Make GSC FW load optional for newer platforms Daniele Ceraolo Spurio
2026-01-08 14:35 ` Rodrigo Vivi
2026-01-08 16:36 ` Daniele Ceraolo Spurio
2026-01-08 20:27 ` Rodrigo Vivi
2026-01-09 15:52 ` Julia Filipchuk
2026-01-08 1:13 ` [PATCH 2/3] drm/xe/ptl: Define GSC for PTL Daniele Ceraolo Spurio
2026-01-09 15:41 ` Julia Filipchuk
2026-01-08 1:13 ` [PATCH 3/3] drm/xe/ptl: Enable PXP " Daniele Ceraolo Spurio
2026-01-08 14:35 ` Rodrigo Vivi
2026-01-08 1:20 ` ✓ CI.KUnit: success for Enable GSC loading and " Patchwork
2026-01-08 1:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-08 3:23 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-08 14:36 ` [PATCH 0/3] " Rodrigo Vivi
2026-01-12 18:03 ` Daniele Ceraolo Spurio [this message]
2026-01-10 0:28 ` ✓ CI.KUnit: success for Enable GSC loading and PXP for PTL (rev2) Patchwork
2026-01-10 1:01 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-10 6:49 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-10 22:10 ` ✓ CI.KUnit: success for Enable GSC loading and PXP for PTL (rev3) Patchwork
2026-01-10 22:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-10 23:50 ` ✗ Xe.CI.Full: 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=511b6ae1-0bd6-4e31-8aa5-e039d2d7f817@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=julia.filipchuk@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