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>,
<michal.wajdeczko@intel.com>
Subject: Re: [PATCH v1 2/2] drm/xe/sysfs: Drop redundant runtime PM usage
Date: Thu, 18 Sep 2025 10:31:59 -0400 [thread overview]
Message-ID: <aMwX3xgNcmLa_6C0@intel.com> (raw)
In-Reply-To: <20250918114804.2957177-3-raag.jadav@intel.com>
On Thu, Sep 18, 2025 at 05:18:04PM +0530, Raag Jadav wrote:
> The device is expected to be in D0 state during driver probe. No need to
> resume it in ->is_visible() callbacks or non I/O operations.
>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_device_sysfs.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_device_sysfs.c b/drivers/gpu/drm/xe/xe_device_sysfs.c
> index c5151c86a98a..ec9c06b06fb5 100644
> --- a/drivers/gpu/drm/xe/xe_device_sysfs.c
> +++ b/drivers/gpu/drm/xe/xe_device_sysfs.c
> @@ -38,13 +38,8 @@ vram_d3cold_threshold_show(struct device *dev,
> {
> struct pci_dev *pdev = to_pci_dev(dev);
> struct xe_device *xe = pdev_to_xe_device(pdev);
> - int ret;
>
> - xe_pm_runtime_get(xe);
> - ret = sysfs_emit(buf, "%d\n", xe->d3cold.vram_threshold);
> - xe_pm_runtime_put(xe);
> -
> - return ret;
> + return sysfs_emit(buf, "%d\n", xe->d3cold.vram_threshold);
> }
>
> static ssize_t
> @@ -173,11 +168,8 @@ static umode_t late_bind_attr_is_visible(struct kobject *kobj,
> u32 cap = 0;
> int ret;
>
> - xe_pm_runtime_get(xe);
> -
> ret = xe_pcode_read(root, PCODE_MBOX(PCODE_LATE_BINDING, GET_CAPABILITY_STATUS, 0),
> &cap, NULL);
> - xe_pm_runtime_put(xe);
> if (ret)
> return 0;
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-09-18 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 11:48 [PATCH v1 0/2] Drop redundant runtime PM usage Raag Jadav
2025-09-18 11:48 ` [PATCH v1 1/2] drm/xe/hwmon: " Raag Jadav
2025-09-30 14:57 ` Lucas De Marchi
2025-09-18 11:48 ` [PATCH v1 2/2] drm/xe/sysfs: " Raag Jadav
2025-09-18 14:31 ` Rodrigo Vivi [this message]
2025-09-18 14:32 ` Rodrigo Vivi
2025-09-18 11:55 ` ✓ CI.KUnit: success for " Patchwork
2025-09-18 12:40 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-18 20:20 ` ✓ Xe.CI.Full: " Patchwork
2025-09-30 9:42 ` [PATCH v1 0/2] " Raag Jadav
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=aMwX3xgNcmLa_6C0@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=michal.wajdeczko@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