public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jean Delvare <khali@linux-fr.org>,
	Serge Belyshev <belyshev@depni.sinp.msu.ru>,
	linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org,
	x86@kernel.org
Subject: Re: [PATCH v4] k10temp: temperature sensor for AMD Family 10h/11h CPUs
Date: Thu, 26 Nov 2009 08:46:35 +0100	[thread overview]
Message-ID: <4B0E325B.7060203@ladisch.de> (raw)
In-Reply-To: <20091125114544.df69cc98.akpm@linux-foundation.org>

Andrew Morton wrote:
> Clemens Ladisch <clemens@ladisch.de> wrote:
> > This adds a driver for the internal temperature sensor of AMD Family 10h
> > and 11h CPUs.
> > ...
> > +#define REG_HARDWARE_THERMAL_CONTROL	0x64
> > +#define  HTC_ENABLE			0x00000001
> > +
> > +#define REG_REPORTED_TEMPERATURE	0xa4
> > +
> > +#define REG_NORTHBRIDGE_CAPABILITIES	0xe8
> > +#define  NB_CAP_HTC			0x00000400
> 
> These definitions relate to register addresses within the AMD CPUs,
> yes?

Yes, in the PCI configuration space of the internal northbridge.

> I wonder if these should be placed in some header file in
> arch/x86/include/asm/ where other such things are described.

There is no such header.  The files that also access PCI cfg registers:
  arch/x86/kernel/k8.c
  arch/x86/kernel/quirks.c
  arch/x86/oprofile/op_model_amd.c
define their own private symbols or use magic numbers.


Best regards,
Clemens

  reply	other threads:[~2009-11-26  7:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AF91F70.10106@ladisch.de>
2009-11-20  8:15 ` [PATCH] k10temp: temperature sensor for AMD Family 10h/11h CPUs Clemens Ladisch
2009-11-20 10:22   ` Serge Belyshev
2009-11-20 10:44     ` [lm-sensors] " Jean Delvare
2009-11-20 10:47     ` [PATCH v2] " Clemens Ladisch
2009-11-20 11:30       ` [lm-sensors] " Jean Delvare
2009-11-20 11:56         ` Clemens Ladisch
2009-11-20 12:18           ` Jean Delvare
2009-11-23  7:45             ` [PATCH v3] " Clemens Ladisch
2009-11-23 13:51               ` Jean Delvare
2009-11-23 15:29                 ` Clemens Ladisch
2009-11-23 19:05                   ` Jean Delvare
2009-11-24  8:43                     ` Clemens Ladisch
2009-11-24 13:26                       ` Jean Delvare
2009-11-24 14:09                         ` Clemens Ladisch
2009-11-24 20:11                           ` Jean Delvare
2009-11-25  9:51                             ` Clemens Ladisch
2009-11-26 20:44                               ` Jean Delvare
2009-11-27 13:03                                 ` Clemens Ladisch
2010-01-10 14:45                                   ` Jean Delvare
2010-01-15  9:57                                     ` Clemens Ladisch
2010-01-15 13:31                                       ` Jean Delvare
2009-11-24  8:43                     ` [PATCH v4] " Clemens Ladisch
2009-11-25 19:45                       ` Andrew Morton
2009-11-26  7:46                         ` Clemens Ladisch [this message]
2009-11-27 15:43                       ` Jean Delvare
2009-11-28  7:48                         ` Andrew Morton

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=4B0E325B.7060203@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=akpm@linux-foundation.org \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox