All of lore.kernel.org
 help / color / mirror / Atom feed
From: hjk@linutronix.de (Hans-Jürgen Koch)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] Add MAX6650 support
Date: Mon, 12 Feb 2007 13:48:05 +0000	[thread overview]
Message-ID: <200702121448.06283.hjk@linutronix.de> (raw)
In-Reply-To: <200701171359.46334.hjk@linutronix.de>

Am Sonntag, 11. Februar 2007 17:22 schrieb Hans-J?rgen Koch:
> Am Sonntag 11 Februar 2007 16:44 schrieb corentin.labbe:
> > Hello
> >
> > i saw some problems in your code:
> >
> > On line 141 you excess the 80 characters width
> > + static ssize_t get_fan(struct device *dev, struct
> > device_attribute *devattr, char *buf, int nr)
> >
> >
> > On the comment you have written "MAX6650 also" instead of "MAX6551
> > also" * This module has only been tested with the MAX6650 chip. It
> > should * work with the MAX6650 also, though with reduced
> > functionality. It * does not distinguish max6650 and max6651 chips.
> >
> >
> > You must use dev_dbg instead of #ifdef debug
> >
> >
> > On line 535 the while(0) is useless
> > erase the max6650_init_client function
> > +static void max6650_init_client(struct i2c_client *client)
> > +{
> > +	/* Nothing to do here - assume the BIOS has initialized the chip
> > */ +	while(0)
> > +	{
> > +		;
> > +	}
> > +}
> >
> >
> > Don't use down() up()
> > replace with mutex
> >
> > On line 553
> > 	MAX6650_REG_TACH0, MAX6650_REG_TACH1,
> > 	MAX6650_REG_TACH2, MAX6650_REG_TACH3
> > 	one per line
> > 	"," at the end
> > like
> > static const u8 tach_reg[] > > {
> > 	MAX6650_REG_TACH0,
> > 	MAX6650_REG_TACH1,
> > 	MAX6650_REG_TACH2,
> > 	MAX6650_REG_TACH3,
> > };
> >
> >
> > Why use max6650_read_value and max6650_write_value?
> > replace with i2c_smbus_write_byte_data and i2c_smbus_read_byte_data
> > directly
> >
> > Check error return code of i2c_detach_client(client);
> > like
> > if ((err = i2c_detach_client(client)))
> > 	return err;
> >
> >
> > Don't use many device_create_file
> > use sysfs_create_group
>
> Thanks for your review, I'll look at the code again and post an
> updated patch soon.
>

Hi,
here's the promised patch with these issues hopefully solved. I tested the 
module on a Kontron CPX board, with a vanilla 2.6.20 kernel, it seems to work 
fine.

Thanks again for the review,

Hans
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: max6650.patch
Type: text/x-diff
Size: 18702 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070212/7ca36436/attachment.bin 

  parent reply	other threads:[~2007-02-12 13:48 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 12:59 [lm-sensors] [PATCH] Add MAX6650 support Hans-Jürgen Koch
2007-01-22  8:36 ` Jean Delvare
2007-02-11 15:44 ` corentin.labbe
2007-02-11 16:22 ` Hans-Jürgen Koch
2007-02-12 13:48 ` Hans-Jürgen Koch [this message]
2007-02-27 15:21 ` [lm-sensors] " Matej Kenda
2007-02-27 15:35 ` [lm-sensors] " Jean Delvare
2007-02-27 16:17 ` Hans-Jürgen Koch
2007-02-27 16:29 ` Matej Kenda
2007-02-27 17:03 ` Matej Kenda
2007-02-27 17:13 ` Hans-Jürgen Koch
2007-02-27 18:07 ` Jean Delvare
2007-02-27 19:58 ` Hans-Jürgen Koch
2007-02-28 11:44 ` Hans-Jürgen Koch
2007-02-28 15:57 ` Matej Kenda
2007-02-28 16:08 ` Hans-Jürgen Koch
2007-03-01  7:15 ` Jean Delvare
2007-03-01  7:34 ` Jean Delvare
2007-03-01 10:11 ` Hans-Jürgen Koch
2007-03-01 17:34 ` corentin.labbe
2007-03-02 11:32 ` Jean Delvare
2007-03-05 11:34 ` Hans-Jürgen Koch
2007-03-11 14:40 ` Jean Delvare
2007-03-11 15:21 ` Jean Delvare
2007-03-11 21:08 ` Hans-Jürgen Koch
2007-03-12 13:50 ` Jean Delvare
2007-03-12 14:44 ` Hans-Jürgen Koch
2007-03-12 16:49 ` Jean Delvare
2007-03-13 13:25 ` Hans-Jürgen Koch
2007-03-15 20:10 ` Jean Delvare
2007-03-16 16:44 ` Hans-Jürgen Koch
2007-03-16 19:17 ` Jean Delvare
2007-03-16 21:07 ` Hans-Jürgen Koch
2007-03-16 21:19 ` Hans-Jürgen Koch
2007-03-16 21:19 ` Thomas Gleixner
2007-03-16 21:33 ` Thomas Gleixner
2007-03-17 13:39 ` Jean Delvare
2007-03-17 14:23 ` Hans-Jürgen Koch

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=200702121448.06283.hjk@linutronix.de \
    --to=hjk@linutronix.de \
    --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.