Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Tauro, Riana" <riana.tauro@intel.com>
To: Raag Jadav <raag.jadav@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: <michal.wajdeczko@intel.com>, <lukasz.laguna@intel.com>,
	<matthew.d.roper@intel.com>, <matthew.brost@intel.com>,
	<mallesh.koujalagi@intel.com>, <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v13 7/9] drm/xe/amc: Guard xe_amc_work() with runtime PM
Date: Thu, 22 Oct 2026 10:09:47 +0530	[thread overview]
Message-ID: <c51e19af-aa41-491a-b1c9-07ba5ea17de6@intel.com> (raw)
In-Reply-To: <20261020023641.200658-8-raag.jadav@intel.com>


On 20-10-2026 08:06, Raag Jadav wrote:
> xe_device_declare_wedged() callers are expected to hold a runtime PM
> reference. Fix it.
>
> Fixes: a55b76b8bc2c ("drm/xe/i2c: Fix the interrupt handling")
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> v10: Guard wedge callers with runtime PM (Sashiko)
> v11: Use traditional xe_pm_runtime_get/put() with goto (Sashiko)
> ---
>   drivers/gpu/drm/xe/xe_amc.c | 7 +++++++
>   1 file changed, 7 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_amc.c b/drivers/gpu/drm/xe/xe_amc.c
> index b7390a4ee3ce..1f85df598e56 100644
> --- a/drivers/gpu/drm/xe/xe_amc.c
> +++ b/drivers/gpu/drm/xe/xe_amc.c
> @@ -15,9 +15,11 @@
>   #include "regs/xe_i2c_regs.h"
>   
>   #include "xe_amc.h"
> +#include "xe_any.h"
>   #include "xe_device.h"
>   #include "xe_i2c.h"
>   #include "xe_mmio.h"
> +#include "xe_pm.h"
>   
>   /**
>    * DOC: Add-In Management Controller (AMC)
> @@ -108,11 +110,14 @@ static void xe_amc_work(struct work_struct *work)
>   {
>   	const struct amc_request *request = &amc_get_alert_reason;
>   	struct xe_amc *amc = from_work(amc, work, work);
> +	struct xe_device *xe = xe_any_to_xe(amc->i2c->drm_dev);
>   	u8 alert_reason = AMC_ALERT_UNKNOWN;
>   	struct amc_response response;
>   	struct i2c_client *client;
>   	int ret;
>   
> +	xe_pm_runtime_get(xe);

Even though Sashiko did complain about guard.
Wouldn't usage of guard maintain consistency and be better here?

With or without guard
Reviewed-by: Riana Tauro <riana.tauro@intel.com>


> +
>   	client = amc->i2c->client[XE_I2C_CLIENT_AMC];
>   	if (IS_ERR_OR_NULL(client))
>   		goto out_reassert_interrupt;
> @@ -167,6 +172,8 @@ static void xe_amc_work(struct work_struct *work)
>   		dev_warn(amc->i2c->drm_dev, "unknown AMC alert: %d\n", alert_reason);
>   		break;
>   	}
> +
> +	xe_pm_runtime_put(xe);
>   }
>   
>   void xe_amc_handle_alert(struct xe_i2c *i2c)

  reply	other threads:[~2026-10-22  4:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20  2:36 [PATCH v13 0/9] Introduce xe_wedge Raag Jadav
2026-10-20  2:36 ` [PATCH v13 1/9] drm/xe/gt: Use GT ordered workqueue for wedging Raag Jadav
2026-10-20  8:30   ` sashiko-bot
2026-10-20  2:36 ` [PATCH v13 2/9] drm/xe: Drop xe_device_set_wedged_method() Raag Jadav
2026-10-20  2:36 ` [PATCH v13 3/9] drm/xe/hw_error: Guard csc_hw_error_work() with runtime PM Raag Jadav
2026-10-22  4:36   ` Tauro, Riana
2026-10-20  2:36 ` [PATCH v13 4/9] drm/xe: Move xe_device_wedged_fini() registration to xe_device_probe_early() Raag Jadav
2026-10-20  2:36 ` [PATCH v13 5/9] drm/xe: Make xe_device_declare_wedged() IRQ safe Raag Jadav
2026-10-20  2:36 ` [PATCH v13 6/9] drm/xe/pci_error: Flush GT wedge worker before bus reset Raag Jadav
2026-10-20  2:36 ` [PATCH v13 7/9] drm/xe/amc: Guard xe_amc_work() with runtime PM Raag Jadav
2026-10-22  4:39   ` Tauro, Riana [this message]
2026-10-22  5:06     ` Raag Jadav
2026-10-20  2:36 ` [PATCH v13 8/9] drm/xe: Introduce xe_wedge Raag Jadav
2026-10-20  2:36 ` [PATCH v13 9/9] drm/xe/ras: Move xe_ras_process_errors() to xe_ras Raag Jadav
2026-10-20  9:27   ` sashiko-bot

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=c51e19af-aa41-491a-b1c9-07ba5ea17de6@intel.com \
    --to=riana.tauro@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lukasz.laguna@intel.com \
    --cc=mallesh.koujalagi@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=rodrigo.vivi@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