From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH 1/3] drm/xe: Fix build by setting the correct parameter to intel_dmc_suspend()
Date: Wed, 11 Sep 2024 16:11:06 -0400 [thread overview]
Message-ID: <ZuH5WkDeQKwDA-7F@intel.com> (raw)
In-Reply-To: <20240911200218.130219-1-jose.souza@intel.com>
On Wed, Sep 11, 2024 at 01:02:16PM -0700, José Roberto de Souza wrote:
> intel_dmc_suspend() was a intel_display no a xe_device.
>
> Fixes: 501d799a47e2 ("drm/xe: Wire up device shutdown handler")
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
> drivers/gpu/drm/xe/display/xe_display.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
> index 3551a9c8eb755..e65e7d70f9890 100644
> --- a/drivers/gpu/drm/xe/display/xe_display.c
> +++ b/drivers/gpu/drm/xe/display/xe_display.c
> @@ -377,7 +377,7 @@ void xe_display_pm_shutdown(struct xe_device *xe)
>
> intel_opregion_suspend(display, PCI_D3cold);
>
> - intel_dmc_suspend(xe);
> + intel_dmc_suspend(display);
It's a drm-build conflict that needs to be solved at drm-tip rebuild...
I'm looking into it right now... Thanks for the heads up
> }
>
> void xe_display_pm_runtime_suspend(struct xe_device *xe)
> --
> 2.46.0
>
next prev parent reply other threads:[~2024-09-11 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 20:02 [PATCH 1/3] drm/xe: Fix build by setting the correct parameter to intel_dmc_suspend() José Roberto de Souza
2024-09-11 20:02 ` [PATCH 2/3] drm/xe: Add a parameter to xe_bb_create_job() to append or not batch buffer end instruction José Roberto de Souza
2024-09-12 2:13 ` Dixit, Ashutosh
2024-09-12 15:39 ` Souza, Jose
2024-09-11 20:02 ` [PATCH 3/3] drm/xe/oa: Fix overflow in oa batch buffer José Roberto de Souza
2024-09-11 20:08 ` ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe: Fix build by setting the correct parameter to intel_dmc_suspend() Patchwork
2024-09-11 20:08 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-11 20:09 ` ✓ CI.KUnit: success " Patchwork
2024-09-11 20:11 ` Rodrigo Vivi [this message]
2024-09-11 20:22 ` ✓ CI.Build: " Patchwork
2024-09-11 20:24 ` ✓ CI.Hooks: " Patchwork
2024-09-11 20:25 ` ✓ CI.checksparse: " Patchwork
2024-09-11 20:41 ` ✓ CI.BAT: " Patchwork
2024-09-11 21:46 ` ✗ CI.FULL: failure " Patchwork
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=ZuH5WkDeQKwDA-7F@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).