From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] hwmon,
Date: Wed, 18 Aug 2010 12:25:20 +0000 [thread overview]
Message-ID: <20100818142520.57489d22@hyperion.delvare> (raw)
In-Reply-To: <20100622084557.GA4524@loge.amd.com>
Hi Andreas,
On Wed, 18 Aug 2010 11:10:52 +0200, Andreas Herrmann wrote:
> On Tue, Aug 17, 2010 at 06:21:38PM +0200, Jean Delvare wrote:
>
> [...]
>
> > > +static int is_rev_g_desktop(u8 model)
> > > +{
> > > + u32 brandidx;
> > > +
> > > + if (model < 0x69)
> > > + return 0;
> > > +
> > > + if (model = 0xc1 || model = 0x6c || model = 0x7c ||
> > > + model = 0x6f || model = 0x7f)
> > > + return 0;
> > > +
> > > + if (model = 0x6b) {
> > > + /* differentiate between AM2 and ASB1 */
> > > + brandidx = cpuid_ebx(0x80000001);
> > > + brandidx = (brandidx >> 9) & 0x1f;
> > > + if (brandidx > 0xa)
> >
> > This will only catch the "AMD Sempron(tm) Processor 2RRU" entry, if I
> > read both the code and the datasheet right?
>
> No, it will catch only the dual-core CPUs
>
> 0Bh 0h AMD Turion(tm) Neo X2 Dual Core Processor L6RR (ASB1)
> 0Ch 0h AMD Athlon(tm) Neo X2 Dual Core Processor L3RR (ASB1)
>
> See revision 3.46 of the RG:
> http://support.amd.com/us/Processor_TechDocs/33610.pdf
Oh, my bad. I didn't see that table 8 was spanning over a 3rd page. Now
it makes more sense.
> > Is this correct? What about the 3 other ASB1 entries in table 8? And
> > why are you comparing with 0xa while this specific value doesn't
> > match any CPU model?
>
> Hmm, wait let me double check this. (Thought the single core variants were
> not affected by this problem)
>
> Damn!
>
> Need to update this patch. I did not check table 2 which lists
> single-core AM2 CPUs.
>
> model 0x6f and 0x7f (both single core) are also provided as ASB1 and
> AM2.
Oh, I'm glad my mistake helped somehow ;) We'd rather get it right this
time. We already introduced a regression in stable kernels, which is
very bad and should never happen, please let's not do it again.
>
> > > + return 0;
> > > + }
> > > +
> > > + return 1;
> > > +}
> > > +
> > > static int __devinit k8temp_probe(struct pci_dev *pdev,
> > > const struct pci_device_id *id)
> > > {
> > > @@ -179,9 +201,7 @@ static int __devinit k8temp_probe(struct pci_dev *pdev,
> > > "wrong - check erratum #141\n");
> > > }
> > >
> > > - if ((model >= 0x69) &&
> > > - !(model = 0xc1 || model = 0x6c || model = 0x7c ||
> > > - model = 0x6b || model = 0x6f || model = 0x7f)) {
> > > + if (is_rev_g_desktop(model))
> > > /*
> > > * RevG desktop CPUs (i.e. no socket S1G1 or
> > > * ASB1 parts) need additional offset,
> > > @@ -189,7 +209,6 @@ static int __devinit k8temp_probe(struct pci_dev *pdev,
> > > * ambient temperature
> > > */
> > > data->temp_offset = 21000;
> > > - }
> > >
> > > break;
> > > }
> >
> > I also do not like the brace change. While technically correct, it
> > could lead to mistakes on future changes, because the large comment
> > doesn't make it immediately obvious that this is currently a
> > single-statement branch.
>
> Ok.
>
> Thanks a lot for reviewing.
> I'll come up with an updated patch.
OK, I'll wait for it.
Thanks,
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-08-18 12:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 8:45 [lm-sensors] [PATCH] hwmon, Andreas Herrmann
2010-06-22 11:24 ` Andreas Herrmann
2010-06-22 11:35 ` Jean Delvare
2010-06-22 14:51 ` Jean Delvare
2010-08-16 9:17 ` Andreas Herrmann
2010-08-16 9:21 ` Andreas Herrmann
2010-08-17 16:21 ` Jean Delvare
2010-08-17 16:52 ` Jean Delvare
2010-08-18 8:55 ` Andreas Herrmann
2010-08-18 9:10 ` Andreas Herrmann
2010-08-18 12:13 ` Andreas Herrmann
2010-08-18 12:25 ` Jean Delvare [this message]
2010-08-19 8:34 ` Jean Delvare
2010-08-19 10:00 ` Andreas Herrmann
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=20100818142520.57489d22@hyperion.delvare \
--to=khali@linux-fr.org \
--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.