public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: "R, Durgadoss" <durgadoss.r@intel.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
	linux-acpi@vger.kernel.org, "Zhang, Rui" <rui.zhang@intel.com>,
	lm-sensors@lm-sensors.org, lenb@kernel.org
Subject: Re: [lm-sensors] Patch[1/2] Adding Core and Package Thermal Threshold  Support to Coretemp
Date: Wed, 8 Dec 2010 16:22:14 +0100	[thread overview]
Message-ID: <20101208162214.353e3899@endymion.delvare> (raw)
In-Reply-To: <D6D887BA8C9DFF48B5233887EF04654105C0E05F4E@bgsmsx502.gar.corp.intel.com>

On Wed, 8 Dec 2010 14:40:29 +0530, R, Durgadoss wrote:
> Hi Fenghua,
> 
> This patch adds the core and package thermal threshold support to coretemp.c.
> These thresholds can be read/written using the hwmon sysfs interfaces
> temp1_core_thresh[0/1] and temp1_pkg_thresh[0/1].

The package temperature isn't currently supported by the coretemp
driver but by the pkgtemp driver. It makes no sense to add support for
package thermal threshold to coretemp as long as the pkgtemp functionality
hasn't been merged back into coretemp. This was the plan, BTW, I
objected to the very existence of a separate pkgtemp driver since day
1, and I thought we had agreed that pkgtemp would be removed and its
functionality would be merged into coretemp.

> Signed-off-by: Durgadoss R <durgadoss.r@intel.com>

Please note also that we will need your full name for kernel
submissions.

-- 
Jean Delvare

  parent reply	other threads:[~2010-12-08 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08  9:10 Patch[1/2] Adding Core and Package Thermal Threshold Support to Coretemp R, Durgadoss
2010-12-08 14:49 ` [lm-sensors] " Guenter Roeck
2010-12-08 15:22 ` Jean Delvare [this message]
2010-12-08 16:36   ` R, Durgadoss
2010-12-08 17:11   ` 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=20101208162214.353e3899@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=durgadoss.r@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=rui.zhang@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