From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: <lucas.demarchi@intel.com>, <intel-xe@lists.freedesktop.org>,
<riana.tauro@intel.com>, <badal.nilawar@intel.com>
Subject: Re: [PATCH v1] drm/xe/i2c: Rely on d3cold.capable flag in system PM path
Date: Wed, 17 Sep 2025 15:58:08 -0400 [thread overview]
Message-ID: <aMsS0BQ0SIjvH6_z@intel.com> (raw)
In-Reply-To: <20250917180929.2906157-1-raag.jadav@intel.com>
On Wed, Sep 17, 2025 at 11:39:29PM +0530, Raag Jadav wrote:
> We don't consider allowed flag for D3cold transition in system PM path.
> Rely on capable flag instead, which reflects root port capability.
>
> Fixes: 0ea07b69517a ("drm/xe/pm: Wire up suspend/resume for I2C controller")
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index 17c7dd024343..0014b5f4ad07 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -198,7 +198,7 @@ int xe_pm_resume(struct xe_device *xe)
> if (err)
> goto err;
>
> - xe_i2c_pm_resume(xe, xe->d3cold.allowed);
> + xe_i2c_pm_resume(xe, xe->d3cold.capable);
something off here...
When do we need:
xe_mmio_rmw32(mmio, I2C_CONFIG_CMD, 0, PCI_COMMAND_MEMORY | PCI_COMMAND_MASTER);
?
if we need everytime we lose power, you should simply do
xe_i2c_pm_resume(xe, true);
in here, since on s3 we will lose power, regardless the d3cold capable.
>
> xe_irq_resume(xe);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-09-17 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 18:09 [PATCH v1] drm/xe/i2c: Rely on d3cold.capable flag in system PM path Raag Jadav
2025-09-17 18:20 ` ✓ CI.KUnit: success for " Patchwork
2025-09-17 19:02 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-17 19:58 ` Rodrigo Vivi [this message]
2025-09-17 21:07 ` ✗ Xe.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=aMsS0BQ0SIjvH6_z@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@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