All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: lucas.demarchi@intel.com, rodrigo.vivi@intel.com,
	matthew.d.roper@intel.com, intel-xe@lists.freedesktop.org,
	anshuman.gupta@intel.com, riana.tauro@intel.com,
	badal.nilawar@intel.com, karthik.poosa@intel.com
Subject: Re: [PATCH v1] drm/xe/hwmon: expose fan speed
Date: Tue, 11 Feb 2025 16:06:19 +0200	[thread overview]
Message-ID: <Z6tZW5Fxc9RkOxXZ@black.fi.intel.com> (raw)
In-Reply-To: <Z6omCGczu0vjQtpc@ashyti-mobl2.lan>

On Mon, Feb 10, 2025 at 05:15:04PM +0100, Andi Shyti wrote:
> Hi Raag,
> 
> On Mon, Feb 10, 2025 at 03:35:15PM +0530, Raag Jadav wrote:
> > Add hwmon support for fan1_input, fan2_input and fan3_input attributes,
> > which will expose fan speed of respective channels in RPM when supported
> > by hardware. With this in place we can monitor fan speed using lm-sensors
> > tool.
> > 
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> 
> I think you've got the hang of it by now :-)

Yeah, we always try to have fun even when we got it but it largely depends
on subsystem.

> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>

Awesome.

> > +#define   FAN_SPEED_CONTROL			0x7D
> > +#define     FSC_READ_NUM_FANS			0x4
> > +
> 
> I don't really like the alignment here, I'd have preferred:
> 
> 	...	0x7D
> 	...	0x04
> 
> with the '0'. But you are being consistent with the header's
> style, so it's OK.

Yep, definitely got the hang.

Raag

  reply	other threads:[~2025-02-11 14:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 10:05 [PATCH v1] drm/xe/hwmon: expose fan speed Raag Jadav
2025-02-10 10:23 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-10 10:23 ` ✓ CI.checkpatch: " Patchwork
2025-02-10 10:24 ` ✓ CI.KUnit: " Patchwork
2025-02-10 10:41 ` ✓ CI.Build: " Patchwork
2025-02-10 10:43 ` ✓ CI.Hooks: " Patchwork
2025-02-10 10:44 ` ✓ CI.checksparse: " Patchwork
2025-02-10 16:15 ` [PATCH v1] " Andi Shyti
2025-02-11 14:06   ` Raag Jadav [this message]
2025-02-11  6:24 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-02-12  9:36 ` ✗ Xe.CI.Full: " Patchwork
2025-02-21 15:02 ` [PATCH v1] " Poosa, Karthik
2025-02-24  7:46   ` Raag Jadav
2025-03-06 14:51     ` Poosa, Karthik
2025-03-06 18:08       ` Raag Jadav
2025-03-03  7:26 ` Raag Jadav
2025-03-03 17:44   ` Rodrigo Vivi
2025-03-03 19:30     ` 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=Z6tZW5Fxc9RkOxXZ@black.fi.intel.com \
    --to=raag.jadav@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=karthik.poosa@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.