From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "Jadav, Raag" <raag.jadav@intel.com>,
"zhanwei919@gmail.com" <zhanwei919@gmail.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Brost, Matthew" <matthew.brost@intel.com>,
"thomas.hellstrom@linux.intel.com"
<thomas.hellstrom@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4] drm/xe/hwmon: document DG2 fan speed reporting quirk
Date: Wed, 17 Jun 2026 11:02:43 +0000 [thread overview]
Message-ID: <03460c5632c235a0a278db8ecb90bedd35718a08.camel@intel.com> (raw)
In-Reply-To: <ajJ86P9MvLmtbPpp@black.igk.intel.com>
On Wed, 2026-06-17 at 12:54 +0200, Raag Jadav wrote:
> On Wed, Jun 03, 2026 at 12:17:07AM +0800, Zhan Wei wrote:
> > On DG2 the driver always shows two fan channels, because the
> > FSC_READ_NUM_FANS command does not work on some cards. OEMs decide
> > how
> > the fans map to tach channels, so two fans can share one tach line.
> > When that happens, the second channel reads 0 RPM even though the
> > fan
> > is spinning.
> >
> > Note this on the fan2_input ABI entry so the steady 0 RPM is not
> > mistaken for a driver bug.
> >
> > Fixes: 28f79ac609de ("drm/xe/hwmon: expose fan speed")
> > Signed-off-by: Zhan Wei <zhanwei919@gmail.com>
> > Reviewed-by: Raag Jadav <raag.jadav@intel.com>
>
> This one seems got lost in the noise. Any takers?
pushed, thanks for patch, review, and heads up.
>
> Raag
prev parent reply other threads:[~2026-06-17 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260527115311.13398-1-zhanwei919@gmail.com>
2026-05-29 13:50 ` [PATCH v2] drm/xe/hwmon: document DG2 fan speed reporting quirk Zhan Wei
2026-05-29 14:05 ` 占wei
2026-05-29 16:12 ` Raag Jadav
2026-05-29 17:24 ` [PATCH v3] " Zhan Wei
2026-05-30 7:12 ` Raag Jadav
2026-06-02 16:17 ` [PATCH v4] " Zhan Wei
2026-06-17 10:54 ` Raag Jadav
2026-06-17 11:02 ` Vivi, Rodrigo [this message]
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=03460c5632c235a0a278db8ecb90bedd35718a08.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=raag.jadav@intel.com \
--cc=skhan@linuxfoundation.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=zhanwei919@gmail.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