From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH 1/2 RESEND 3] hwmon: new vt1211 driver
Date: Wed, 30 Aug 2006 17:53:32 +0000 [thread overview]
Message-ID: <20060830195332.c50f26ee.khali@linux-fr.org> (raw)
In-Reply-To: <191fb4ca0608292235s3494ddecp2276c5d9841ac775@mail.gmail.com>
Juerg,
> > Hmmm, so you permuted temp1, temp2 and temp3 compared to the Linux 2.4
> > driver. While I was OK with swapping temp1 and temp3 (in line with the
> > datasheet), I'm not as happy with changing temp2. It makes matching
> > with the datasheet harder.
> >
> > What are the benefits? Making ISTEMP() more simple, and getting rid of
> > TEMPIX_FROM/TO_REG()?
>
> Oh yes! The mapping is screwed either way, just in different places.
> This way the code is simpler and easier to read.
Hmmm...
OK. We'll need to make some adjustments to user-space and possibly to
the 2.4 kernel driver, but we would have had to, anyway.
Will you be able to test the 2.4 kernel driver if we modify it?
> > > + /* Read VID and set VRM */
> > > + data->vid = vt1211_read8(data, VT1211_REG_VID) & 0x1f;
> >
> > Any reason why this is only read once, rather than updated on every
> > read?
>
> That's a static value, isn't it? Why read it more than once?
No, it may not be static. Recent CPUs change voltages on the fly, so
the VID value could change as well.
--
Jean Delvare
next prev parent reply other threads:[~2006-08-30 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 5:35 [lm-sensors] [PATCH 1/2 RESEND 3] hwmon: new vt1211 driver Juerg Haefliger
2006-08-30 16:24 ` Jean Delvare
2006-08-30 17:46 ` Juerg Haefliger
2006-08-30 17:53 ` Jean Delvare [this message]
2006-08-30 18:30 ` Juerg Haefliger
2006-08-31 1:18 ` Juerg Haefliger
2006-08-31 20:09 ` Jean Delvare
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=20060830195332.c50f26ee.khali@linux-fr.org \
--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.