From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Alexander Stein <alexander.stein@systec-electronic.com>,
Fenghua Yu <fenghua.yu@intel.com>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: coretemp: Support for Intel Atom E6XX CPU (TunnelCreek)?
Date: Mon, 27 Jun 2011 09:10:54 -0700 [thread overview]
Message-ID: <1309191054.8271.636.camel@groeck-laptop> (raw)
In-Reply-To: <20110627164108.777c2e28@endymion.delvare>
On Mon, 2011-06-27 at 10:41 -0400, Jean Delvare wrote:
> Hi Alexander,
>
> On Mon, 27 Jun 2011 12:20:51 +0200, Alexander Stein wrote:
> > I have a patch (for v2.6.39) which adds support for Intel Atom E6XX
> > (TunnelCreek) to coretemp. It's merely only adding x86_model 0x26.
>
> You have a patch, great for you. What do you expect if you don't share
> it with us?
>
> I'm not quite sure what your patch would be doing anyway. Since kernel
> 2.6.35, supported CPU models are detected using the DTS feature flag
> rather than the family and model numbers, so your Atom E6XX should be
> detected just fine.
>
Maybe it is for Tjmax detection ?
> Note that there was a bug in kernels 2.6.35 to 2.6.39 with regards to
> TjMax guessing, which was fixed by Gunter Roeck with:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4f5f71a7abe329bdad81ee6a8e4545054a7cc30a
> You'll have to update to kernel version 2.6.39.2 to get this fix.
>
> Do you happen to know what CPUs model number 0x26 covers? Do you know
> if this model supports MSR_IA32_TEMPERATURE_TARGET or not? The original
> Atom (model 0x1c) did not.
>
> > But there are models (e.g. E660 and E660T) with different TjMax, namely 90
> > degrees C and 110 degrees C. But these different model can't be detected by
> > reading from hardware.
>
> I would appreciate a patch to Documentation/hwmon/coretemp adding the
> known TjMax for these new Atom models.
>
> BTW, is it really impossible to identify these models with a different
> TjMax? Don't the strings "E660" and "E660T" appear in the respective
> "model name" entries in /proc/cpuinfo?
I thought about replacing the manual TjMax detection code with code
using the model string to take care of problems like this - essentially
by providing a table with entries { model string, Tjmax } for each CPU
with Tjmax other than 100 degrees C. This way we could get rid of some
of the odd code we have today. Would that make sense ?
Thanks,
Guenter
next prev parent reply other threads:[~2011-06-27 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 10:20 coretemp: Support for Intel Atom E6XX CPU (TunnelCreek)? Alexander Stein
2011-06-27 13:42 ` Guenter Roeck
2011-06-27 14:41 ` Jean Delvare
2011-06-27 16:05 ` Alexander Stein
2011-06-27 16:10 ` Guenter Roeck [this message]
2011-06-27 16:40 ` [lm-sensors] " R, Durgadoss
2011-06-27 16:50 ` Guenter Roeck
2011-06-27 16:54 ` R, Durgadoss
2011-08-03 12:58 ` Alexander Stein
2011-08-03 13:26 ` R, Durgadoss
2011-08-03 14:40 ` Alexander Stein
2011-09-16 16:21 ` Jean Delvare
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=1309191054.8271.636.camel@groeck-laptop \
--to=guenter.roeck@ericsson.com \
--cc=alexander.stein@systec-electronic.com \
--cc=fenghua.yu@intel.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
/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