From: Guenter Roeck <linux@roeck-us.net>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Steven Honeyman <stevenhoneyman@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i8k: Add support for temperature sensor labels
Date: Sun, 30 Nov 2014 08:00:18 -0800 [thread overview]
Message-ID: <547B3F12.9030705@roeck-us.net> (raw)
In-Reply-To: <201411301053.40222@pali>
On 11/30/2014 01:53 AM, Pali Rohár wrote:
[ ... ]
>>>
>>> Original Dell DOS executable ignores all temperature sensors
>>> if type SMM function fails (if I decoded and understand
>>> that DOS assembler code correctly). So maybe we should do
>>> same...
>>>
>>> But because our i8k.c code ignores sensor only if it returns
>>> invalid temperature, there could be possible regression that
>>> on same machines type SMM function is not implemented or
>>> not working...
>>>
>>> What do you think?
>>
>> Tested with XPS13, Studio 1555 (with GPU), and XPS M140.
>> Reading the type works with all of them. The Studio 1555
>> reports the GPU temperature in temp4. The M140 is quite old
>> (about 10 years), so I guess we can be reasonably sure that
>> all laptops currently in use support reporting the type.
>>
>
> Good. Then I will split this patch into two parts. One which adds
> labels and one which change init code to register only those
> sensors which have valid type.
>
Ok.
>> Do you know what is returned for the type if the GPU is turned
>> off on a system with GPU ? I think that is the only open
>> question.
>>
>
> Yes, on my E6440 in both cases when GPU is turned off and on is
> returned same type (GPU). So this does not help us.
>
Unless I misunderstand you, it does help us; it simplifies
sensor detection since we don't have to handle the special case
that the GPU is turned off anymore.
Thanks,
Guenter
next prev parent reply other threads:[~2014-11-30 16:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 16:04 [PATCH] i8k: Add support for temperature sensor labels Pali Rohár
2014-11-29 16:09 ` Pali Rohár
2014-11-29 16:24 ` Guenter Roeck
2014-11-29 16:32 ` Pali Rohár
2014-11-29 16:37 ` Steven Honeyman
2014-11-29 17:07 ` Gabriele Mazzotta
2014-11-29 17:18 ` Pali Rohár
2014-11-29 18:27 ` Gabriele Mazzotta
2014-11-29 18:58 ` Guenter Roeck
2014-11-29 19:07 ` Pali Rohár
2014-11-29 21:34 ` Guenter Roeck
2014-11-30 0:07 ` Guenter Roeck
2014-11-30 9:53 ` Pali Rohár
2014-11-30 16:00 ` Guenter Roeck [this message]
2014-11-30 17:44 ` Pali Rohár
2014-11-30 17:54 ` Guenter Roeck
2014-11-30 18:00 ` Pali Rohár
2014-11-30 18:22 ` Guenter Roeck
2014-11-30 1:25 ` Guenter Roeck
2014-11-30 10:11 ` Pali Rohár
2014-11-30 16:04 ` Guenter Roeck
2014-11-29 16:24 ` Guenter Roeck
2014-11-29 16:30 ` Pali Rohár
2014-11-29 18:15 ` Guenter Roeck
2014-11-29 17:43 ` Greg Kroah-Hartman
2014-11-29 17:49 ` Pali Rohár
2014-11-29 17:51 ` Greg Kroah-Hartman
2014-11-29 18:04 ` Pali Rohár
2014-12-02 13:23 ` Jean Delvare
2014-12-02 14:26 ` Guenter Roeck
2014-12-03 9:09 ` Jean Delvare
2014-12-03 9:25 ` Pali Rohár
2014-12-03 10:11 ` Jean Delvare
2014-12-03 19:14 ` Guenter Roeck
2014-12-04 10:16 ` Jean Delvare
2014-11-29 18:05 ` Guenter Roeck
2014-11-29 18:00 ` Guenter Roeck
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=547B3F12.9030705@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=gabriele.mzt@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=stevenhoneyman@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