From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: <intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: <anshuman.gupta@intel.com>, <rodrigo.vivi@intel.com>,
<alexander.usyskin@intel.com>, <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v4 07/10] drm/xe/xe_late_bind_fw: Reload late binding fw during system resume
Date: Fri, 27 Jun 2025 13:23:16 +0530 [thread overview]
Message-ID: <20bdbd2a-4ee6-492b-9ceb-13a70cd2d767@intel.com> (raw)
In-Reply-To: <20250625170015.33912-8-badal.nilawar@intel.com>
Hi Daniele,
On 25-06-2025 22:30, Badal Nilawar wrote:
> Reload late binding fw during resume from system suspend
>
> v2:
> - Unconditionally reload late binding fw (Rodrigo)
> - Flush worker during system suspend
>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index 91923fd4af80..f49b7b6eab97 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -127,6 +127,8 @@ int xe_pm_suspend(struct xe_device *xe)
> if (err)
> goto err;
>
> + xe_late_bind_wait_for_worker_completion(&xe->late_bind);
> +
During system suspend, MEI will unbind the component. This flush is
unnecessary because it takes place within
xe_late_bind_component_unbind(). I will remove this call.
Badal
> for_each_gt(gt, xe, id)
> xe_gt_suspend_prepare(gt);
>
> @@ -205,6 +207,8 @@ int xe_pm_resume(struct xe_device *xe)
>
> xe_pxp_pm_resume(xe->pxp);
>
> + xe_late_bind_fw_load(&xe->late_bind);
> +
> drm_dbg(&xe->drm, "Device resumed\n");
> return 0;
> err:
next prev parent reply other threads:[~2025-06-27 7:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 17:00 [PATCH v4 00/10] Introducing firmware late binding Badal Nilawar
2025-06-25 17:00 ` [PATCH v4 01/10] mei: bus: add mei_cldev_mtu interface Badal Nilawar
2025-06-25 17:00 ` [PATCH v4 02/10] mei: late_bind: add late binding component driver Badal Nilawar
2025-06-26 3:50 ` Gupta, Anshuman
2025-06-27 14:06 ` Nilawar, Badal
2025-06-28 12:18 ` Greg KH
2025-07-01 8:32 ` Nilawar, Badal
2025-07-01 9:45 ` Greg KH
2025-07-01 12:34 ` Nilawar, Badal
2025-07-01 16:41 ` Nilawar, Badal
2025-07-01 17:34 ` Rodrigo Vivi
2025-07-02 4:12 ` Gupta, Anshuman
2025-07-02 6:24 ` Usyskin, Alexander
2025-07-01 10:05 ` Usyskin, Alexander
2025-06-28 12:19 ` Greg KH
2025-07-01 8:07 ` Nilawar, Badal
2025-07-01 8:17 ` Greg KH
2025-07-01 8:22 ` Nilawar, Badal
2025-07-01 8:32 ` Usyskin, Alexander
2025-06-25 17:00 ` [PATCH v4 03/10] drm/xe/xe_late_bind_fw: Introducing xe_late_bind_fw Badal Nilawar
2025-06-27 21:04 ` Rodrigo Vivi
2025-06-30 13:49 ` Nilawar, Badal
2025-06-25 17:00 ` [PATCH v4 04/10] drm/xe/xe_late_bind_fw: Initialize late binding firmware Badal Nilawar
2025-06-26 21:06 ` Daniele Ceraolo Spurio
2025-06-27 12:48 ` Nilawar, Badal
2025-06-25 17:00 ` [PATCH v4 05/10] drm/xe/xe_late_bind_fw: Load " Badal Nilawar
2025-06-26 17:24 ` Rodrigo Vivi
2025-06-26 21:27 ` Daniele Ceraolo Spurio
2025-06-26 21:49 ` Rodrigo Vivi
2025-06-26 22:38 ` Daniele Ceraolo Spurio
2025-06-26 22:49 ` Rodrigo Vivi
2025-06-25 17:00 ` [PATCH v4 06/10] drm/xe/xe_late_bind_fw: Reload late binding fw in rpm resume Badal Nilawar
2025-06-25 17:00 ` [PATCH v4 07/10] drm/xe/xe_late_bind_fw: Reload late binding fw during system resume Badal Nilawar
2025-06-27 7:53 ` Nilawar, Badal [this message]
2025-06-25 17:00 ` [PATCH v4 08/10] drm/xe/xe_late_bind_fw: Introduce debug fs node to disable late binding Badal Nilawar
2025-06-25 17:00 ` [PATCH v4 09/10] drm/xe/xe_late_bind_fw: Extract and print version info Badal Nilawar
2025-06-26 21:32 ` Daniele Ceraolo Spurio
2025-06-25 17:00 ` [PATCH v4 10/10] drm/xe/xe_late_bind_fw: Select INTEL_MEI_LATE_BIND for CI Badal Nilawar
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=20bdbd2a-4ee6-492b-9ceb-13a70cd2d767@intel.com \
--to=badal.nilawar@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®