All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] ad7414 driver
Date: Mon, 16 Jun 2008 06:36:16 +0000	[thread overview]
Message-ID: <20080616083616.7418e023@hyperion.delvare> (raw)
In-Reply-To: <20080613221221.50c642ee@lappy.seanm.ca>

Hi Sean

On Sun, 15 Jun 2008 18:07:48 -0400, Sean MacLennan wrote:
> Thanks for the review... I will work on the changes.

Great.

> I just wanted to make a couple of general comments. This driver was
> based on the ad7418 driver, at least according to the copyrights at the
> top. I assumed that the basic functionality (show/set for example) was
> correct. I notice that many of the comments for this driver also apply
> to the ad7418 ;)

I just took a quick look at the current ad7418 driver and I didn't see
much that needs fixing, except for the missing inclusion of
<linux/sysfs.h>. Also, the ad7418 driver is a legacy i2c driver while
the ad7414 driver was turned into a new-style i2c driver, so all the
administrative part is different. Anyway, if you see things in the
ad7418 driver which you think needs fixing or could be improved, feel
free to send a patch and we'll review it.

> I am using the ad7414 on the PIKA Warp product. The ad7414 is a very
> important part of what we call DTM: Dynamic Thermal Management.
> Basically DTM controls the fan and shuts down the machine if it gets
> too hot.
> 
> The Warp does not have libsensors, let alone any apps to connect to
> libsensors. All of the DTM is done in the kernel itself.
> 
> I could give you a link to the DTM code, but we had a bad thunderstorm
> here and I can no longer connect to work :( I believe it is here:
> 
> http://svn.pikatech.com/appliance/branches/linux-2.6/arch/powerpc/platforms/44x/warp/warp.c

Almost...

http://svn.pikatech.com/appliance/branches/linux-2.6/arch/powerpc/platforms/44x/warp.c

Hmm, the code there is not exactly nice... Obviously the hwmon and i2c
subsystems were not designed with this use case in mind, there's room
for improvement. But that's a long way to go, and I really don't have
the time to dive into this at the moment. I'll try to keep in mind for
later though.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2008-06-16  6:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14  2:12 [lm-sensors] [PATCH] ad7414 driver Sean MacLennan
2008-06-15  8:09 ` Jean Delvare
2008-06-15 17:13 ` Sean MacLennan
2008-06-15 21:11 ` Jean Delvare
2008-06-15 22:07 ` Sean MacLennan
2008-06-16  6:36 ` Jean Delvare [this message]
2008-06-16 23:11 ` Sean MacLennan
2008-06-19 10:46 ` Jean Delvare
2008-06-19 16:37 ` Sean MacLennan
2008-06-19 17:45 ` Jean Delvare
2008-06-19 18:02 ` Sean MacLennan
2008-06-23 12:33 ` Jean Delvare
2008-08-02  3:52 ` Sean MacLennan
2008-08-08  9:06 ` 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=20080616083616.7418e023@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.