From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: rodrigo.vivi@intel.com, intel-xe@lists.freedesktop.org,
anshuman.gupta@intel.com, badal.nilawar@intel.com,
riana.tauro@intel.com
Subject: Re: [PATCH v6 1/3] drm/xe/pm: s/xe_device_sysfs_init/xe_pm_sysfs_init
Date: Sat, 3 May 2025 10:55:11 +0300 [thread overview]
Message-ID: <aBXL3-nvGOReGNH8@black.fi.intel.com> (raw)
In-Reply-To: <4keegjzampto67kcdasnztjnv4pdli2zwfztey5mo26akzvw6v@tnxf5z6keokk>
On Fri, May 02, 2025 at 05:00:55PM -0500, Lucas De Marchi wrote:
> On Sat, May 03, 2025 at 12:07:37AM +0530, Raag Jadav wrote:
> > Attributes being exposed in xe_pm_init() are PM specific and should
> > follow its naming.
> >
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > Reviewed-by: Riana Tauro <riana.tauro@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_device_sysfs.c | 6 +++---
> > drivers/gpu/drm/xe/xe_device_sysfs.h | 2 +-
> > drivers/gpu/drm/xe/xe_pm.c | 2 +-
> > 3 files changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_device_sysfs.c b/drivers/gpu/drm/xe/xe_device_sysfs.c
> > index 7efbd4c52791..2d25e5b5d4bf 100644
> > --- a/drivers/gpu/drm/xe/xe_device_sysfs.c
> > +++ b/drivers/gpu/drm/xe/xe_device_sysfs.c
> > @@ -63,14 +63,14 @@ vram_d3cold_threshold_store(struct device *dev, struct device_attribute *attr,
> >
> > static DEVICE_ATTR_RW(vram_d3cold_threshold);
> >
> > -static void xe_device_sysfs_fini(void *arg)
> > +static void xe_pm_sysfs_fini(void *arg)
> > {
> > struct xe_device *xe = arg;
> >
> > sysfs_remove_file(&xe->drm.dev->kobj, &dev_attr_vram_d3cold_threshold.attr);
> > }
> >
> > -int xe_device_sysfs_init(struct xe_device *xe)
> > +int xe_pm_sysfs_init(struct xe_device *xe)
> > {
> > struct device *dev = xe->drm.dev;
> > int ret;
> > @@ -79,5 +79,5 @@ int xe_device_sysfs_init(struct xe_device *xe)
> > if (ret)
> > return ret;
> >
> > - return devm_add_action_or_reset(dev, xe_device_sysfs_fini, xe);
> > + return devm_add_action_or_reset(dev, xe_pm_sysfs_fini, xe);
> > }
> > diff --git a/drivers/gpu/drm/xe/xe_device_sysfs.h b/drivers/gpu/drm/xe/xe_device_sysfs.h
> > index f9e83d8bd2c7..2c1fabdba9e4 100644
> > --- a/drivers/gpu/drm/xe/xe_device_sysfs.h
> > +++ b/drivers/gpu/drm/xe/xe_device_sysfs.h
> > @@ -8,6 +8,6 @@
> >
> > struct xe_device;
> >
> > -int xe_device_sysfs_init(struct xe_device *xe);
> > +int xe_pm_sysfs_init(struct xe_device *xe);
>
> you can do it on top, but I don't see it in this series. If you are
> naming this xe_pm_* since it's pm specific, then please make sure
> it is in xe_pm.c
Yes, I already have it locally but delayed it since it's unrelated
to the series. Will send it out separately once we merge this.
Raag
next prev parent reply other threads:[~2025-05-03 7:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 18:37 [PATCH v6 0/3] BMG PCIe link downgrade attributes and usage Raag Jadav
2025-05-02 18:37 ` [PATCH v6 1/3] drm/xe/pm: s/xe_device_sysfs_init/xe_pm_sysfs_init Raag Jadav
2025-05-02 22:00 ` Lucas De Marchi
2025-05-03 7:55 ` Raag Jadav [this message]
2025-05-05 19:12 ` Rodrigo Vivi
2025-05-02 18:37 ` [PATCH v6 2/3] drm/xe: Expose PCIe link downgrade attributes Raag Jadav
2025-05-02 18:37 ` [PATCH v6 3/3] drm/xe/doc: Wire up PCIe Gen5 limitations Raag Jadav
2025-05-02 18:44 ` ✓ CI.Patch_applied: success for BMG PCIe link downgrade attributes and usage (rev2) Patchwork
2025-05-02 18:45 ` ✓ CI.checkpatch: " Patchwork
2025-05-02 18:46 ` ✓ CI.KUnit: " Patchwork
2025-05-02 18:54 ` ✓ CI.Build: " Patchwork
2025-05-02 18:57 ` ✓ CI.Hooks: " Patchwork
2025-05-02 18:58 ` ✓ CI.checksparse: " Patchwork
2025-05-03 0:00 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-06 8:36 ` ✓ Xe.CI.BAT: success " 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=aBXL3-nvGOReGNH8@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@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