linux-kernel - Re: [lm-sensors] [PATCH V3] hwmon, k10temp: Add support for F15h M60h

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 15 Aug 2014 08:39:24 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Phil Pokorny <ppokorny@...guincomputing.com>,
	Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>
CC:	"clemens@...isch.de" <clemens@...isch.de>,
	"jdelvare@...e.de" <jdelvare@...e.de>,
	"rdunlap@...radead.org" <rdunlap@...radead.org>,
	"bp@...e.de" <bp@...e.de>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>
Subject: Re: [lm-sensors] [PATCH V3] hwmon, k10temp: Add support for F15h
 M60h

On 08/15/2014 08:18 AM, Phil Pokorny wrote:
>
>         On 08/14/2014 04:15 PM, Aravind Gopalakrishnan wrote:
>
>             This patch adds temperature monitoring support for F15h M60h processor.
>                - Add new pci device id for the relevant processor
>                - The functionality of REG_REPORTED_TEMPERATURE is moved to
>                  D0F0xBC_xD820_0CA4 [Reported Temperature Control]
>                  - So, use this to get CUR_TEMP value
>                  - Since we need an indirect register access, protect this with
>                    a mutex lock
>
>
> What about making this a new driver forked from k10temp.
>
> AMD has changed how they report temperatures and the very different method of getting these temps suggests that it is no longer reasonable to add support to this driver for these new chips. Particular attention to the mutex required to protect the indirect register suggests that this would benefit from focus in its own driver now that there are multiple members of the "k15temp" family.
>
> Anyone else have thoughts?
>

Everything in that new driver except for reading the actual temperature
would be exactly the same. That doesn't make sense to me.

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/