lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 21 Dec 2014 14:58:02 -0800 From: Guenter Roeck <linux@...ck-us.net> To: Pali Rohár <pali.rohar@...il.com>, Arnd Bergmann <arnd@...db.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org> CC: linux-kernel@...r.kernel.org Subject: Re: [PATCH 08/10] i8k: Autodetect maximal fan speed and fan RPM multiplier On 12/21/2014 11:54 AM, Pali Rohár wrote: > This patch adds new function i8k_get_fan_nominal_speed() for doing SMM call > which will return nominal fan RPM for specified fan speed. It returns nominal > RPM value at which fan operate when speed (0, 1, 2, 3) is set. It looks like > RPM value is not accurate, but still provides very useful information. > > First it can be used to validate if certain fan speed could be accepted by SMM > for setting fan speed and we can use this routine to detect maximal fan speed. > > Second it returns RPM value, so we can check if value looks correct with > multiplier 30 or multiplier 1 (until now only these two multiplier were used). > If RPM value with multiplier 30 is too high, then multiplier 1 is used. > > In case when SMM reports that new function is not supported we will fallback > to old hardcoded values. Maximal fan speed would be 2 and RPM multiplier 30. > > Signed-off-by: Pali Rohár <pali.rohar@...il.com> > Tested-by: Pali Rohár <pali.rohar@...il.com> As mentioned earlier, we can unfortunately not rely on fan speed range auto-detection. Maybe you can take that part out for now, and we can look at it again separately. Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists