All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-xe@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2 1/3] drm/xe: Remove ci-only GuC FW definitions
Date: Tue, 30 Jan 2024 14:11:29 -0800	[thread overview]
Message-ID: <85eddybhf2.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <b54fe849-bf9f-4000-b695-069bb3c25b70@intel.com>

On Tue, 30 Jan 2024 10:48:50 -0800, Daniele Ceraolo Spurio wrote:
>
> On 1/30/2024 10:33 AM, Dixit, Ashutosh wrote:
> > On Tue, 19 Dec 2023 12:00:20 -0800, Daniele Ceraolo Spurio wrote:
> >> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
> >> index 73d6938c921d..9dff96dfe455 100644
> >> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
> >> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
> >> @@ -102,9 +102,7 @@ struct fw_blobs_by_type {
> >>   };
> >>
> >>   #define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver)			\
> >> -	fw_def(LUNARLAKE,	mmp_ver(xe,	guc,	lnl,	70, 6, 8))	\
> >>	fw_def(METEORLAKE,	major_ver(i915,	guc,	mtl,	70, 7))		\
> >> -	fw_def(PVC,		mmp_ver(xe,	guc,	pvc,	70, 9, 1))	\
> >>	fw_def(DG2,		major_ver(i915,	guc,	dg2,	70, 5))		\
> >>	fw_def(DG1,		major_ver(i915,	guc,	dg1,	70, 5))		\
> >>	fw_def(ALDERLAKE_N,	major_ver(i915,	guc,	tgl,	70, 5))		\
> > I think this commit should include an error message saying FW not found (or
> > whatever). A lot of people have spent a lot of time because probe just
> > fails with "xe: probe of 0000:00:02.0 failed with error -22" without any
> > indication of why?
>
> There already is a drm_notice for the firmware fetch failure, in
> uc_fw_request(). Are you say that's not coming out in dmesg?

Because from what I am seeing, xe_uc_fw_init() is not failing, xe_guc_init
is returning from if (!xe_uc_fw_is_enabled()):

int xe_guc_init(struct xe_guc *guc)
{
        struct xe_device *xe = guc_to_xe(guc);
        struct xe_gt *gt = guc_to_gt(guc);
        int ret;

        guc->fw.type = XE_UC_FW_TYPE_GUC;
        ret = xe_uc_fw_init(&guc->fw);
        if (ret)
                goto out;

        if (!xe_uc_fw_is_enabled(&guc->fw))
                return 0;

And finally xe_uc_init fails, not because xe_guc_init fails, but because
xe_wopcm_init fails :/

  reply	other threads:[~2024-01-30 22:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 20:00 [PATCH v2 1/3] drm/xe: Remove ci-only GuC FW definitions Daniele Ceraolo Spurio
2023-12-19 20:00 ` [PATCH v2 2/3] drm/xe/guc: define PVC FW Daniele Ceraolo Spurio
2023-12-19 20:00 ` [PATCH v2 3/3] drm/xe/guc: define LNL FW Daniele Ceraolo Spurio
2023-12-19 20:03 ` ✓ CI.Patch_applied: success for series starting with [v2,1/3] drm/xe: Remove ci-only GuC FW definitions Patchwork
2023-12-19 20:03 ` ✓ CI.checkpatch: " Patchwork
2023-12-19 20:04 ` ✓ CI.KUnit: " Patchwork
2023-12-19 20:11 ` ✓ CI.Build: " Patchwork
2023-12-19 20:12 ` ✓ CI.Hooks: " Patchwork
2023-12-19 20:13 ` ✓ CI.checksparse: " Patchwork
2023-12-19 20:55 ` ✗ CI.BAT: failure " Patchwork
2023-12-19 22:58 ` [PATCH v2 1/3] " Rodrigo Vivi
2024-01-04 11:58 ` ✓ CI.Patch_applied: success for series starting with [v2,1/3] " Patchwork
2024-01-04 11:58 ` ✓ CI.checkpatch: " Patchwork
2024-01-04 11:59 ` ✓ CI.KUnit: " Patchwork
2024-01-04 12:07 ` ✓ CI.Build: " Patchwork
2024-01-04 12:07 ` ✓ CI.Hooks: " Patchwork
2024-01-04 12:08 ` ✓ CI.checksparse: " Patchwork
2024-01-04 12:43 ` ✓ CI.BAT: " Patchwork
2024-01-30 18:33 ` [PATCH v2 1/3] " Dixit, Ashutosh
2024-01-30 18:48   ` Daniele Ceraolo Spurio
2024-01-30 22:11     ` Dixit, Ashutosh [this message]
2024-01-30 22:29       ` 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=85eddybhf2.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.