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 v2] drm/xe/i2c: Don't rely on d3cold.allowed flag in system PM path
Date: Thu, 18 Sep 2025 10:41:51 -0400 [thread overview]
Message-ID: <aMwaLxuoB9UU8Hb6@intel.com> (raw)
In-Reply-To: <20250918103200.2952576-1-raag.jadav@intel.com>
On Thu, Sep 18, 2025 at 04:02:00PM +0530, Raag Jadav wrote:
> In S3 and above sleep states, the device can loose power regardless of
> d3cold.allowed flag. Bring up I2C controller explicitly in system PM
> path to ensure its normal operation after loosing power.
>
> v2: Cover S3 and above states (Rodrigo)
>
> 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 a303ed5780b4..00ced1f63776 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, true);
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> xe_irq_resume(xe);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-09-18 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 10:32 [PATCH v2] drm/xe/i2c: Don't rely on d3cold.allowed flag in system PM path Raag Jadav
2025-09-18 10:38 ` ✗ CI.checkpatch: warning for " Patchwork
2025-09-18 10:39 ` ✓ CI.KUnit: success " Patchwork
2025-09-18 11:26 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-18 14:41 ` Rodrigo Vivi [this message]
2025-09-18 18:52 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-30 9:41 ` [PATCH v2] " Raag Jadav
2025-10-02 14:29 ` 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=aMwaLxuoB9UU8Hb6@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