From: Andrew Morton <akpm@linux-foundation.org>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: djwong@us.ibm.com, khali@linux-fr.org,
linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [PATCH 1/5] adt7462: New hwmon driver
Date: Fri, 7 Nov 2008 11:18:08 -0800 [thread overview]
Message-ID: <20081107111808.851dad3b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081107185626.13022.59407.stgit@elm3a70.beaverton.ibm.com>
On Fri, 07 Nov 2008 10:56:26 -0800
"Darrick J. Wong" <djwong@us.ibm.com> wrote:
>
> New driver to play with. As Jean mentioned a couple of years ago, this
> chip is a beast with odd combinations of 8 fans, 4 temperatures, and
> 13 voltage sensors. This driver has been tested on an IntelliStation
> Z30.
>
> ...
>
> + * 9. Vbatt/FSB_Vtt (pin 26)
> + * A. +3.3V/+1.2V1 (pin 25)
> + * B. Vccp2/+2.5V/+1.8V/+1.5V (pin 24)
> + * C. +1.5V ICH (only if BOTH pin 28/29 are set to +1.5V)
> + * D. +1.5V 3GPIO (only if BOTH pin 28/29 are set to +1.5V)
> + *
> + * Each of these 13 has a factor to convert raw to voltage. Even better,
> + * the pins can be connected to other sensors (tach/gpio/hot/etc), which
> + * makes the bookkeeping tricky.
> + *
> + * Some, but not all, of these voltages have low/high limits.
> + */
> +#define ADT7462_VOLT_COUNT 12
> +
> +#define ADT7462_VENDOR 0x41
> +#define ADT7462_DEVICE 0x62
> +/* datasheet only mentions a revision 4 */
> +#define ADT7462_REVISION 0x04
> +
> +/* How often do we reread sensors values? (In jiffies) */
> +#define SENSOR_REFRESH_INTERVAL (2 * HZ)
> +
> +/* How often do we reread sensor limit values? (In jiffies) */
> +#define LIMIT_REFRESH_INTERVAL (60 * HZ)
> +
> +/* datasheet says to divide this number by the fan reading to get fan rpm */
> +#define FAN_PERIOD_TO_RPM(x) ((90000 * 60) / (x))
> +#define FAN_RPM_TO_PERIOD FAN_PERIOD_TO_RPM
> +#define FAN_PERIOD_INVALID 65535
> +#define FAN_DATA_VALID(x) ((x) && (x) != FAN_PERIOD_INVALID)
A macro which evaluates its args more than once is a bit naughty.
> +#define MASK_AND_SHIFT(value, prefix) \
> + (((value) & prefix##_MASK) >> prefix##_SHIFT)
> +
> +#define ROUND_DIV(x, divisor) (((x) + ((divisor) / 2)) / (divisor))
hm, ok.
That evaluates `divisor' twice, too.
argh. ALIGN() has the same problem. Something like this...
--- a/include/linux/kernel.h~a
+++ a/include/linux/kernel.h
@@ -39,7 +39,12 @@ extern const char linux_proc_banner[];
#define STACK_MAGIC 0xdeadbeef
#define ALIGN(x,a) __ALIGN_MASK(x,(typeof(x))(a)-1)
-#define __ALIGN_MASK(x,mask) (((x)+(mask))&~(mask))
+
+#define __ALIGN_MASK(x,mask) ({ \
+ typeof(mask) __mask = mask; \
+ (((x) + __mask) & ~__mask); \
+})
+
#define PTR_ALIGN(p, a) ((typeof(p))ALIGN((unsigned long)(p), (a)))
#define IS_ALIGNED(x, a) (((x) & ((typeof(x))(a) - 1)) == 0)
_
Looks good to my untrained eye. Quite a large driver.
next prev parent reply other threads:[~2008-11-07 19:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 18:56 [PATCH 0/5] Various hwmon patches Darrick J. Wong
2008-11-07 18:56 ` [PATCH 1/5] adt7462: New hwmon driver Darrick J. Wong
2008-11-07 19:04 ` Harvey Harrison
2008-11-07 19:27 ` Andrew Morton
2008-11-07 19:34 ` Darrick J. Wong
2008-11-07 19:38 ` Darrick J. Wong
2008-11-07 19:18 ` Andrew Morton [this message]
2008-11-07 18:56 ` [PATCH 2/5] i5k_amb: Load automatically on all 5000/5400 chipsets Darrick J. Wong
2008-11-08 11:09 ` Jean Delvare
2008-11-11 6:26 ` Greg KH
2008-11-07 18:56 ` [PATCH 3/5] adt7470: Check input range when sysfs files are written Darrick J. Wong
2008-11-11 0:22 ` Andrew Morton
2008-11-11 0:49 ` Darrick J. Wong
2008-11-07 18:56 ` [PATCH 4/5] adt7473: Check inputs from sysfs writes Darrick J. Wong
2008-11-07 19:20 ` Andrew Morton
2008-11-07 20:35 ` Jean Delvare
2008-11-07 20:49 ` Joe Perches
2008-11-07 21:00 ` Jean Delvare
2008-11-07 21:02 ` Randy Dunlap
2008-11-07 18:56 ` [PATCH 5/5] lm85: Support adt7468 chips Darrick J. Wong
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=20081107111808.851dad3b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=djwong@us.ibm.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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