All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gong <gong.chen@linux.intel.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH V3 3/3] hwmon: (coretemp) documentation
Date: Fri, 30 Jul 2010 02:38:44 +0000	[thread overview]
Message-ID: <4C523B34.3080702@linux.intel.com> (raw)
In-Reply-To: <1279850968-12154-4-git-send-email-gong.chen@linux.intel.com>

于 7/30/2010 3:34 AM, Andrew Morton 写道:
> On Fri, 23 Jul 2010 10:09:28 +0800
> Chen Gong<gong.chen@linux.intel.com>  wrote:
>
>> update coretemp supported CPU TjMax lists and some cleanup work.
>
> Patches #1 and #2 are unaltered.  Below are the alterations which you
> made to patch #3.  No explanation of these changes has been provided.

I've written the change in the first mail. Strange
Here is the change I copied from my original email:

V2 -> V3
patch 1/3: according to Jean's suggestion, delete _FROZEN bit from 
condition.
            Here is the reason: see commit id 561d9a96
patch 2/3: no update
patch 3/3: according to the suggestion from Guenter Roeck, clarify some 
stuff.


>
>
>
>   Documentation/hwmon/coretemp |    9 +++++----
>   drivers/hwmon/coretemp.c     |    4 ++--
>   2 files changed, 7 insertions(+), 6 deletions(-)
>
> diff -puN Documentation/hwmon/coretemp~hwmon-coretemp-documentation-update-and-cleanup-update Documentation/hwmon/coretemp
> --- a/Documentation/hwmon/coretemp~hwmon-coretemp-documentation-update-and-cleanup-update
> +++ a/Documentation/hwmon/coretemp
> @@ -21,8 +21,8 @@ Temperature is measured in degrees Celsi
>   1 degree C. Valid temperatures are from 0 to TjMax degrees C, because
>   the actual value of temperature register is in fact a delta from TjMax.
>
> -Temperature known as TjMax is the maximum junction temperature of processor.
> -Intel defines this temperature as 80C or 105C. At this temperature, protection
> +Temperature known as TjMax is the maximum junction temperature of processor,
> +which depends on the CPU model. See table below. At this temperature, protection
>   mechanism will perform actions to forcibly cool down the processor. Alarm
>   may be raised, if the temperature grows enough (more than TjMax) to trigger
>   the Out-Of-Spec bit. Following table summarizes the exported sysfs files:
> @@ -65,8 +65,8 @@ Process		Processor					TjMax(C)
>
>   45nm		Xeon Processors 5200 Dual-Core
>   		X5282, X5272, X5270, X5260			90
> -		E5240, E5220, E5205				90
> -		E5205, E5220					70
> +		E5240						90
> +		E5205, E5220					70, 90
>   		L5240						70
>   		L5238, L5215					95
>
> @@ -76,6 +76,7 @@ Process		Processor					TjMax(C)
>   		Z510/500					90
>   		N475/470/455/450				100
>   		N280/270					90
> +		330/230						125
>
>   45nm		Core2 Processors
>   		Solo ULV SU3500/3300				100
> diff -puN drivers/hwmon/coretemp.c~hwmon-coretemp-documentation-update-and-cleanup-update drivers/hwmon/coretemp.c
> --- a/drivers/hwmon/coretemp.c~hwmon-coretemp-documentation-update-and-cleanup-update
> +++ a/drivers/hwmon/coretemp.c
> @@ -54,12 +54,12 @@ struct coretemp_data {
>   	const char *name;
>   	u32 id;
>   	u16 core_id;
> -	u8 alarm;
>   	char valid;		/* zero until following fields are valid */
>   	unsigned long last_updated;	/* in jiffies */
>   	int temp;
>   	int tjmax;
>   	int ttarget;
> +	u8 alarm;
>   };
>
>   /*
> @@ -308,7 +308,7 @@ static int __devinit coretemp_probe(stru
>   #ifdef CONFIG_SMP
>   	data->core_id = c->cpu_core_id;
>   #endif
> -	data->name = DRVNAME;
> +	data->name = "coretemp";
>   	mutex_init(&data->update_lock);
>
>   	/* test if we can access the THERM_STATUS MSR */
> _
>
>


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2010-07-30  2:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23  2:09 [lm-sensors] [PATCH V3 3/3] hwmon: (coretemp) documentation update Chen Gong
2010-07-29 19:34 ` [lm-sensors] [PATCH V3 3/3] hwmon: (coretemp) documentation Andrew Morton
2010-07-30  2:38 ` Chen Gong [this message]

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=4C523B34.3080702@linux.intel.com \
    --to=gong.chen@linux.intel.com \
    --cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.