From: Raag Jadav <raag.jadav@intel.com>
To: lucas.demarchi@intel.com, rodrigo.vivi@intel.com,
matthew.d.roper@intel.com, andi.shyti@linux.intel.com
Cc: 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: Mon, 3 Mar 2025 09:26:49 +0200 [thread overview]
Message-ID: <Z8VZud-t0j1bMSpv@black.fi.intel.com> (raw)
In-Reply-To: <20250210100515.2205584-1-raag.jadav@intel.com>
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>
> ---
Bump, perhaps we can apply this if no further comments?
Raag
next prev parent reply other threads:[~2025-03-03 7:26 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
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 [this message]
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=Z8VZud-t0j1bMSpv@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.