Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	intel-xe@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2 2/2] drm/xe/sysfs: Simplify sysfs registration
Date: Thu, 18 Sep 2025 10:14:00 +0200	[thread overview]
Message-ID: <aMu_SAKsM2ytBdm-@black.igk.intel.com> (raw)
In-Reply-To: <wfzmbfx3mnre7lvzquhpxxbcks37orlqpfdeam4awzpa6d5kx6@wwnysmofevfx>

On Wed, Sep 17, 2025 at 02:38:14PM -0500, Lucas De Marchi wrote:
> On Wed, Sep 17, 2025 at 12:52:45PM +0200, Raag Jadav wrote:
> > On Wed, Sep 17, 2025 at 12:24:24PM +0200, Michal Wajdeczko wrote:
> > > On 9/17/2025 8:18 AM, Raag Jadav wrote:
> > > > On Tue, Sep 16, 2025 at 07:00:29PM +0200, Michal Wajdeczko wrote:
> > > > > Instead of manually maintaining each sysfs file define and use
> > > > > attribute groups and register them using device managed function.

Nit: Although this gets the point across, is there a punctuation missing here
or am I reading it wrong?

> > > > > Then use is_visible() to filter-out unsupported attributes.

...

> > > > >  	xe_pm_runtime_put(xe);
> > > >
> > > > The device is already in D0 while probing so runtime PM is probably
> > > > not needed here.
> > > 
> > > true, but this is how it was initially coded and I didn't want to change it now
> > > 
> > > we can either drop it completely or replace with
> > > 
> > > 	xe_pm_runtime_get_noresume(xe);
> > > 	xe_pm_runtime_put(xe);
> > > 
> > > do you want this to be done as part of this series or it can be done later as follow-up?
> > 
> > Since there's no functional impact, I don't see any harm in dropping
> > it as part of refactoring here. But whatever the maintainers think is
> > best.
> 
> Let's keep those changes separate so we avoid bundling multiple changes
> in one patch. One small patch on top to do that doesn't hurt. Please
> send it when you can.

Sure, thanks.

Raag

  reply	other threads:[~2025-09-18  8:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16 17:00 [PATCH v2 0/2] drm/xe/sysfs: Fix attributes registration on VFs Michal Wajdeczko
2025-09-16 17:00 ` [PATCH v2 1/2] drm/xe/vf: Don't expose sysfs attributes not applicable for VFs Michal Wajdeczko
2025-09-16 17:07   ` Lucas De Marchi
2025-09-16 17:00 ` [PATCH v2 2/2] drm/xe/sysfs: Simplify sysfs registration Michal Wajdeczko
2025-09-17  6:18   ` Raag Jadav
2025-09-17 10:24     ` Michal Wajdeczko
2025-09-17 10:52       ` Raag Jadav
2025-09-17 19:38         ` Lucas De Marchi
2025-09-18  8:14           ` Raag Jadav [this message]
2025-09-16 17:08 ` ✓ CI.KUnit: success for drm/xe/sysfs: Fix attributes registration on VFs (rev2) Patchwork
2025-09-16 17:54 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-16 18:52 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-17 19:58   ` Michal Wajdeczko

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=aMu_SAKsM2ytBdm-@black.igk.intel.com \
    --to=raag.jadav@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michal.wajdeczko@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