From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Fix merge fails related to display runtime PM
Date: Mon, 2 Sep 2024 14:16:26 +0200 [thread overview]
Message-ID: <ZtWsmvIIus-Cl3lT@phenom.ffwll.local> (raw)
In-Reply-To: <20240902112002.489225-1-maarten.lankhorst@linux.intel.com>
On Mon, Sep 02, 2024 at 01:20:02PM +0200, Maarten Lankhorst wrote:
> The most recent merge commits introduced some fails to drm/drm-next,
> I've noticed these when looking at the xe patches.
>
> Solve it!
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
I dropped the first hunk, since that was broken in drm-tip too. So
separate bugfix that should go in with proper review and Fixes: tag and
all that imo.
Otherwise with this drm-next now matches what was in drm-tip.
Thanks for the quick fix!
Cheers, Sima
> ---
> drivers/gpu/drm/xe/display/xe_display.c | 2 --
> drivers/gpu/drm/xe/xe_pm.c | 4 +---
> 2 files changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
> index 78a884ddd499a..710b1e2170c13 100644
> --- a/drivers/gpu/drm/xe/display/xe_display.c
> +++ b/drivers/gpu/drm/xe/display/xe_display.c
> @@ -341,8 +341,6 @@ void xe_display_pm_suspend(struct xe_device *xe, bool runtime)
>
> xe_display_flush_cleanup_work(xe);
>
> - xe_display_flush_cleanup_work(xe);
> -
> intel_dp_mst_suspend(xe);
>
> intel_hpd_cancel_work(xe);
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index 2e2accd76fb2b..39e0a8774a104 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -392,8 +392,6 @@ int xe_pm_runtime_suspend(struct xe_device *xe)
> xe_display_pm_runtime_suspend(xe);
>
> if (xe->d3cold.allowed) {
> - xe_display_pm_suspend(xe, true);
> -
> err = xe_bo_evict_all(xe);
> if (err)
> goto out;
> @@ -411,7 +409,7 @@ int xe_pm_runtime_suspend(struct xe_device *xe)
> xe_display_pm_suspend_late(xe);
> out:
> if (err)
> - xe_display_pm_resume(xe, true);
> + xe_display_pm_runtime_resume(xe);
> xe_rpm_lockmap_release(xe);
> xe_pm_write_callback_task(xe, NULL);
> return err;
> --
> 2.45.2
>
--
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2024-09-02 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 11:20 [PATCH] drm/xe: Fix merge fails related to display runtime PM Maarten Lankhorst
2024-09-02 11:25 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-09-02 12:16 ` Daniel Vetter [this message]
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=ZtWsmvIIus-Cl3lT@phenom.ffwll.local \
--to=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@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