From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Jani Nikula" <jani.nikula@intel.com>
Subject: Re: [PATCH] drm/xe/lnl: Drop force_probe requirement
Date: Fri, 23 Aug 2024 10:30:00 -0400 [thread overview]
Message-ID: <Zsic6M0jOt_nzzXi@intel.com> (raw)
In-Reply-To: <20240822224615.793540-1-lucas.demarchi@intel.com>
On Thu, Aug 22, 2024 at 03:46:15PM -0700, Lucas De Marchi wrote:
> Lunar Lake has been usable for a while in a desktop setup. Bugs are
> sporadically showing up in CI, but being promptly fixed. Nothing very
> concerning.
>
> All the uapi changes related to fundamental platform usage have been
> finalized.
>
> Remove the force_probe requirement and enable the platform by default.
>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>
> Last concerning bug[1] should now be fixed since [2] is merged. Mesa CI
> was hitting it frequently, which was badly impacting their execution.
>
> [1] https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1705
> [2] https://lore.kernel.org/intel-xe/20240821193842.352557-1-rodrigo.vivi@intel.com/T/#t
>
> We should probably wait a few more days for this forward-looking patch
> before merging it though.
>
> drivers/gpu/drm/xe/xe_pci.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index 0c2342988650..fa57996f9c37 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -342,7 +342,6 @@ static const struct xe_device_desc mtl_desc = {
> static const struct xe_device_desc lnl_desc = {
> PLATFORM(LUNARLAKE),
> .has_display = true,
> - .require_force_probe = true,
> };
>
> static const struct xe_device_desc bmg_desc = {
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-08-23 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 22:46 [PATCH] drm/xe/lnl: Drop force_probe requirement Lucas De Marchi
2024-08-22 22:51 ` ✓ CI.Patch_applied: success for " Patchwork
2024-08-22 22:52 ` ✓ CI.checkpatch: " Patchwork
2024-08-22 22:53 ` ✓ CI.KUnit: " Patchwork
2024-08-22 23:05 ` ✓ CI.Build: " Patchwork
2024-08-22 23:07 ` ✓ CI.Hooks: " Patchwork
2024-08-22 23:08 ` ✓ CI.checksparse: " Patchwork
2024-08-22 23:28 ` ✓ CI.BAT: " Patchwork
2024-08-23 6:06 ` ✗ CI.FULL: failure " Patchwork
2024-08-23 14:30 ` Rodrigo Vivi [this message]
2024-08-23 15:21 ` [PATCH] " Thomas Hellström
2024-08-27 6:26 ` Lucas De Marchi
2024-08-27 7:49 ` Jani Nikula
2024-08-27 16:24 ` Lucas De Marchi
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=Zsic6M0jOt_nzzXi@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=thomas.hellstrom@linux.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