From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <uma.shankar@intel.com>,
<imre.deak@intel.com>
Subject: Re: [PATCH 2/2] drm/xe/display: Do not do intel_fbdev_set_suspend during runtime
Date: Wed, 11 Sep 2024 16:39:13 -0400 [thread overview]
Message-ID: <ZuH_8bUkSJu8tvSG@intel.com> (raw)
In-Reply-To: <20240911152724.693560-3-suraj.kandpal@intel.com>
On Wed, Sep 11, 2024 at 08:57:24PM +0530, Suraj Kandpal wrote:
> Do not do intel_fbdev_set_suspend during runtime_suspend/resume
> functions. This cause a big circular lock_dep splat.
Please also add the lockdep splat here.
I also agree with the change and believe it should be removed.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/xe/display/xe_display.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
> index a09062b7687d..bf18fd69e1c2 100644
> --- a/drivers/gpu/drm/xe/display/xe_display.c
> +++ b/drivers/gpu/drm/xe/display/xe_display.c
> @@ -333,7 +333,9 @@ void xe_display_pm_suspend(struct xe_device *xe, bool runtime)
> * properly.
> */
> intel_power_domains_disable(xe);
> - intel_fbdev_set_suspend(&xe->drm, FBINFO_STATE_SUSPENDED, true);
> + if (!runtime)
> + intel_fbdev_set_suspend(&xe->drm, FBINFO_STATE_SUSPENDED, true);
> +
> if (!runtime && has_display(xe)) {
> drm_kms_helper_poll_disable(&xe->drm);
> intel_display_driver_disable_user_access(xe);
> @@ -420,7 +422,8 @@ void xe_display_pm_resume(struct xe_device *xe, bool runtime)
>
> intel_opregion_resume(display);
>
> - intel_fbdev_set_suspend(&xe->drm, FBINFO_STATE_RUNNING, false);
> + if (!runtime)
> + intel_fbdev_set_suspend(&xe->drm, FBINFO_STATE_RUNNING, false);
>
> intel_power_domains_enable(xe);
> }
> --
> 2.43.2
>
next prev parent reply other threads:[~2024-09-11 20:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 15:27 [PATCH 0/2] Move some functions out of runtime sus/resume Suraj Kandpal
2024-09-11 15:27 ` [PATCH 1/2] drm/xe/display: Do not suspend resume dp mst during runtime Suraj Kandpal
2024-09-11 20:37 ` Rodrigo Vivi
2024-09-11 15:27 ` [PATCH 2/2] drm/xe/display: Do not do intel_fbdev_set_suspend " Suraj Kandpal
2024-09-11 20:39 ` Rodrigo Vivi [this message]
2024-09-11 16:12 ` ✓ CI.Patch_applied: success for Move some functions out of runtime sus/resume Patchwork
2024-09-11 16:12 ` ✓ CI.checkpatch: " Patchwork
2024-09-11 16:13 ` ✓ CI.KUnit: " Patchwork
2024-09-11 16:33 ` ✓ CI.Build: " Patchwork
2024-09-11 16:36 ` ✓ CI.Hooks: " Patchwork
2024-09-11 16:38 ` ✓ CI.checksparse: " Patchwork
2024-09-11 16:55 ` ✗ CI.BAT: failure " Patchwork
2024-09-11 18:06 ` ✗ CI.FULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 1:25 [PATCH 0/2] " Suraj Kandpal
2024-09-12 1:25 ` [PATCH 2/2] drm/xe/display: Do not do intel_fbdev_set_suspend during runtime Suraj Kandpal
2024-09-13 20:39 ` Rodrigo Vivi
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=ZuH_8bUkSJu8tvSG@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@intel.com \
--cc=uma.shankar@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;
as well as URLs for NNTP newsgroup(s).