Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	John Harrison <John.C.Harrison@intel.com>
Subject: Re: [PATCH 0/6] Move HuC and GSC FW defs for LNL and BMG to drm-xe-next
Date: Thu, 25 Jul 2024 09:00:57 -0700	[thread overview]
Message-ID: <de2fafa3-9bf0-41c2-b9b6-b67cf3b11351@intel.com> (raw)
In-Reply-To: <tqx4jfnjgkzq3opvcdtsjcr3ivqvsw3qs3upptne37fr7afzuu@2y2ath6vpri4>



On 7/24/2024 9:48 PM, Lucas De Marchi wrote:
> On Wed, Jul 24, 2024 at 05:32:17PM GMT, Daniele Ceraolo Spurio wrote:
>> The FW defines are currently in the for-ci branch because the FW blobs
>> weren't ready to be officially published. Now that we have updated HuC
>> and GSC blobs that are ready to be sent to linux-firmware, we can remove
>> the defines from the for-ci branch and add them to drm-xe-next.
>>
>> Note that the 3 reverts are not meant to be merged, they're there to
>> indicate the removal of those patches from the for-ci branch. Only the
>> latter 3 patches are meant to be merged.
>>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: John Harrison <John.C.Harrison@Intel.com>
>
> not a huge fan of UFC, but the first thing that came to mind when I saw
> this was the catchphrase "iiiiiiiit's tiiime" :) Although I still miss
> GuC in the series, hopefully we can get it soon.
>
> If CI is happy, I'm happy with this.
>
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> It would be good to note, in the cover letter, where the firmware blobs
> currently are (the commit in drm/firmware containing them) and the
> status for sending this to upstream linux-firmware.
>
> AFAICS 
> https://gitlab.freedesktop.org/drm/firmware/-/commits/intel-staging?ref_type=heads
> up to commit 0690b69dc20da6d096450faa0c256f6896ff8365 has these 3 blobs.
> Can you share the plan to send them to linux-firmware? Is this going to
> happen just after having the CI results?

I was planning to wait for the GuC binaries to be ready first and then 
send a single PR to linux-firmware with all the blobs, which means 
sending the PR either late this week or early next week. Note that we 
usually send the PR after the patches have been merged for 1-2 days, so 
this would be in line with that.

CI is happy, so let me know if you prefer me to hold until we're ready 
with all the binaries, otherwise I'll go ahead and merge.

Daniele

>
>
> thanks
> Lucas De Marchi
>
>>
>> Daniele Ceraolo Spurio (6):
>>  Revert "drm/xe/huc: Define BMG HuC"
>>  Revert "drm/xe/gsc: define GSC FW for LNL"
>>  Revert "drm/xe/huc: Define LNL HuC"
>>  drm/xe/huc: Define HuC binary for LNL
>>  drm/xe/gsc: Define GSC binary for LNL
>>  drm/xe/huc: Define HuC binary for BMG
>>
>> drivers/gpu/drm/xe/xe_uc_fw.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> -- 
>> 2.43.0
>>


  reply	other threads:[~2024-07-25 16:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  0:32 [PATCH 0/6] Move HuC and GSC FW defs for LNL and BMG to drm-xe-next Daniele Ceraolo Spurio
2024-07-25  0:32 ` [PATCH 1/6] Revert "drm/xe/huc: Define BMG HuC" Daniele Ceraolo Spurio
2024-07-25  0:32 ` [PATCH 2/6] Revert "drm/xe/gsc: define GSC FW for LNL" Daniele Ceraolo Spurio
2024-07-25  0:32 ` [PATCH 3/6] Revert "drm/xe/huc: Define LNL HuC" Daniele Ceraolo Spurio
2024-07-25  0:32 ` [PATCH 4/6] drm/xe/huc: Define HuC binary for LNL Daniele Ceraolo Spurio
2024-07-25  0:32 ` [PATCH 5/6] drm/xe/gsc: Define GSC " Daniele Ceraolo Spurio
2024-07-25  0:32 ` [PATCH 6/6] drm/xe/huc: Define HuC binary for BMG Daniele Ceraolo Spurio
2024-07-25  1:14 ` ✓ CI.Patch_applied: success for Move HuC and GSC FW defs for LNL and BMG to drm-xe-next Patchwork
2024-07-25  1:14 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-25  1:18 ` ✓ CI.KUnit: success " Patchwork
2024-07-25  1:30 ` ✓ CI.Build: " Patchwork
2024-07-25  1:31 ` ✓ CI.Hooks: " Patchwork
2024-07-25  1:33 ` ✓ CI.checksparse: " Patchwork
2024-07-25  1:56 ` ✓ CI.BAT: " Patchwork
2024-07-25  2:58 ` ✗ CI.FULL: failure " Patchwork
2024-07-25  4:48 ` [PATCH 0/6] " Lucas De Marchi
2024-07-25 16:00   ` Daniele Ceraolo Spurio [this message]
2024-07-25 18:05     ` Lucas De Marchi
2024-07-25 20:19       ` Daniele Ceraolo Spurio

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=de2fafa3-9bf0-41c2-b9b6-b67cf3b11351@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=John.C.Harrison@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@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