From: Andres Freund <andres@anarazel.de>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Tushar Dave <tushar.n.dave@intel.com>,
Zhang Rui <rui.zhang@intel.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal: intel_pch_thermal: Add PCI ids for Lewisburg PCH.
Date: Wed, 28 Oct 2020 13:21:01 -0700 [thread overview]
Message-ID: <20201028202101.2m2jp3tfa6mh3brz@alap3.anarazel.de> (raw)
In-Reply-To: <2de70e961f24592d2d157b8586526df2eaf0ae6e.camel@linux.intel.com>
Hi,
On 2020-01-16 11:41:34 -0800, Srinivas Pandruvada wrote:
> On Thu, 2020-01-16 at 10:42 -0800, Andres Freund wrote:
> > Hi,
> >
> > On 2020-01-16 05:53:13 -0800, Srinivas Pandruvada wrote:
> > > On Wed, 2020-01-15 at 10:44 -0800, Andres Freund wrote:
> > > > I noticed that I couldn't read the PCH temperature on my
> > > > workstation
> > > > (C620 series chipset, w/ 2x Xeon Gold 5215 CPUs) directly, but
> > > > had to
> > > > go
> > > > through IPMI. Looking at the data sheet, it looks to me like the
> > > > existing intel PCH thermal driver should work without changes for
> > > > Lewisburg.
> > > Does the temperature reading match with what you read via IPMI?
> >
> > It does:
> >
> > root@awork3:~# ipmitool sdr|grep ^PCH
> > PCH Temp | 58 degrees C | ok
> >
> > andres@awork3:~$ cat /sys/class/thermal/thermal_zone0/type
> > pch_lewisburg
> > andres@awork3:~$ cat /sys/class/thermal/thermal_zone0/temp
> > 58000
> >
> > And if I generate some load, it rises for both:
> > root@awork3:~# ipmitool sdr|grep ^PCH
> > PCH Temp | 60 degrees C | ok
> > andres@awork3:~$ cat /sys/class/thermal/thermal_zone0/temp
> > 60000
> >
> Thanks for the test.
>
> Rui can add his ACK.
Ping? Looks like this got lost somewhere?
Greetings,
Andres Freund
next prev parent reply other threads:[~2020-10-29 2:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 18:44 [PATCH] thermal: intel_pch_thermal: Add PCI ids for Lewisburg PCH Andres Freund
2020-01-16 8:08 ` Daniel Lezcano
2020-01-16 13:53 ` Srinivas Pandruvada
2020-01-16 18:42 ` Andres Freund
2020-01-16 19:41 ` Srinivas Pandruvada
2020-10-28 20:21 ` Andres Freund [this message]
2020-11-12 11:29 ` Daniel Lezcano
2020-11-12 11:34 ` Daniel Lezcano
2020-11-13 20:49 ` Andres Freund
2020-11-14 18:41 ` Pandruvada, Srinivas
2020-11-16 9:28 ` Daniel Lezcano
2020-11-21 0:46 ` Andres Freund
2020-11-24 9:36 ` [thermal: thermal/next] " thermal-bot for Andres Freund
2020-11-13 20:50 ` [PATCH] " Andres Freund
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=20201028202101.2m2jp3tfa6mh3brz@alap3.anarazel.de \
--to=andres@anarazel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tushar.n.dave@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;
as well as URLs for NNTP newsgroup(s).