All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Jonathan Cameron <jic23@cam.ac.uk>,
	Chris Verges <chrisv@cyberswitching.com>
Cc: linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [PATCH] adxl345 accelerometer hwmon driver
Date: Wed, 01 Jul 2009 19:33:11 +0000	[thread overview]
Message-ID: <20090701213311.04d9a8bd@hyperion.delvare> (raw)
In-Reply-To: <4A4BB4AB.7010003@cam.ac.uk>

On Wed, 01 Jul 2009 19:10:35 +0000, Jonathan Cameron wrote:
> 
> > Hi kernel hackers,
> > 
> > Here is a patch that adds support to the Linux kernel for Analog
> > Device's ADXL345 chip.  It is an accelerometer that uses I2C and HWMON.
> > When I looked into the MAINTAINERS file for the appropriate list, the
> > "Orphan" status of "Hardware Monitoring" confused me as to the proper
> > list for this patch ... please let me know if I need to forward it
> > elsewhere.
> Hi Chris,
> 
> Just for reference this chip is definitely on my list of ones to support
> via the Industrial I/O (iio) framework, I just haven't managed to get hold
> of one as yet!  It's particualrly interesting to me because of the fifo
> buffering functionality as currently I only have access to a VTI chip
> that does something similar.
> 
> A new version of the IIO framework will get posted just
> as soon as I've had a few mins to bring the documentation / demo userspace
> apps up to date with the current code state.
> I've been chasing down bugs for the last week.
> 
> First big question is:
> 
> What are you actually doing with it?  If you aren't doing hardware
> monitoring then I would expect you aren't going to receive a favourable
> response on here.

Absolutely correct. Chris' driver doesn't implement any attribute
listed in Documentation/hwmon/sysfs-interface. The device registers as
a hwmon device for no good reason I can think of, and the driver
includes hwmon headers it doesn't make any use of. So to me it doesn't
look like a good candidate for drivers/hwmon. Chris, I suggest that you
remove all references to hwmon from your driver, and resubmit it to a
different subsystem (iio, misc, input, whatever.)

> (see the original IIO discussion on LKML for why I
> started writing that in the first place.
> http://lkml.org/lkml/2008/5/20/135)
> It's somewhat out of date and incomplete, but there is a white paper draft at
> http://www-sigproc.eng.cam.ac.uk/~jic23/iio.pdf
> 
> I'll take a look at the actual code tomorrow.  Always good to see another
> accelerometer driver.

-- 
Jean Delvare

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

WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Jonathan Cameron <jic23@cam.ac.uk>,
	Chris Verges <chrisv@cyberswitching.com>
Cc: linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [PATCH] adxl345 accelerometer hwmon driver
Date: Wed, 1 Jul 2009 21:33:11 +0200	[thread overview]
Message-ID: <20090701213311.04d9a8bd@hyperion.delvare> (raw)
In-Reply-To: <4A4BB4AB.7010003@cam.ac.uk>

On Wed, 01 Jul 2009 19:10:35 +0000, Jonathan Cameron wrote:
> 
> > Hi kernel hackers,
> > 
> > Here is a patch that adds support to the Linux kernel for Analog
> > Device's ADXL345 chip.  It is an accelerometer that uses I2C and HWMON.
> > When I looked into the MAINTAINERS file for the appropriate list, the
> > "Orphan" status of "Hardware Monitoring" confused me as to the proper
> > list for this patch ... please let me know if I need to forward it
> > elsewhere.
> Hi Chris,
> 
> Just for reference this chip is definitely on my list of ones to support
> via the Industrial I/O (iio) framework, I just haven't managed to get hold
> of one as yet!  It's particualrly interesting to me because of the fifo
> buffering functionality as currently I only have access to a VTI chip
> that does something similar.
> 
> A new version of the IIO framework will get posted just
> as soon as I've had a few mins to bring the documentation / demo userspace
> apps up to date with the current code state.
> I've been chasing down bugs for the last week.
> 
> First big question is:
> 
> What are you actually doing with it?  If you aren't doing hardware
> monitoring then I would expect you aren't going to receive a favourable
> response on here.

Absolutely correct. Chris' driver doesn't implement any attribute
listed in Documentation/hwmon/sysfs-interface. The device registers as
a hwmon device for no good reason I can think of, and the driver
includes hwmon headers it doesn't make any use of. So to me it doesn't
look like a good candidate for drivers/hwmon. Chris, I suggest that you
remove all references to hwmon from your driver, and resubmit it to a
different subsystem (iio, misc, input, whatever.)

> (see the original IIO discussion on LKML for why I
> started writing that in the first place.
> http://lkml.org/lkml/2008/5/20/135)
> It's somewhat out of date and incomplete, but there is a white paper draft at
> http://www-sigproc.eng.cam.ac.uk/~jic23/iio.pdf
> 
> I'll take a look at the actual code tomorrow.  Always good to see another
> accelerometer driver.

-- 
Jean Delvare

  parent reply	other threads:[~2009-07-01 19:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Acn6eDhBoTUmzVqOSVGG9a2LiwqVrA==>
2009-07-01 18:17 ` [lm-sensors] [PATCH] adxl345 accelerometer hwmon driver Chris Verges
2009-07-01 18:17   ` Chris Verges
2009-07-01 19:10   ` [lm-sensors] " Jonathan Cameron
2009-07-01 19:10     ` Jonathan Cameron
2009-07-01 19:19     ` Chris Verges
2009-07-01 19:19       ` Chris Verges
2009-07-01 20:13       ` Jean Delvare
2009-07-01 20:13         ` Jean Delvare
2009-07-01 20:52         ` [lm-sensors] " Chris Verges
2009-07-01 20:52           ` Chris Verges
2009-07-02 11:25           ` [lm-sensors] " Jean Delvare
2009-07-02 11:25             ` Jean Delvare
2009-07-02 13:55             ` [lm-sensors] " Jonathan Cameron
2009-07-02 13:55               ` Jonathan Cameron
2009-07-02  8:04         ` [lm-sensors] " Éric Piel
2009-07-02  8:04           ` Éric Piel
2009-07-01 19:33     ` Jean Delvare [this message]
2009-07-01 19:33       ` [lm-sensors] " Jean Delvare
2009-07-02 14:15   ` Chris Verges
2009-07-02 17:38   ` Jonathan Cameron
2009-07-02 17:38     ` Jonathan Cameron
2009-07-02 17:43     ` Mike Frysinger
2009-07-02 17:43       ` Mike Frysinger
2009-07-02 17:59       ` Jonathan Cameron
2009-07-02 17:59         ` Jonathan Cameron
2009-07-02 18:12         ` Hennerich, Michael
2009-07-02 18:12           ` Hennerich, Michael
2009-07-02 18:15           ` Mike Frysinger
2009-07-02 18:15             ` Mike Frysinger
2009-07-02 17:59       ` Hennerich, Michael
2009-07-02 17:59         ` Hennerich, Michael
2009-08-14 11:05   ` XingChao Wang
2009-08-14 11:05     ` XingChao Wang
2009-08-14 13:48   ` [lm-sensors] " Chris Verges

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=20090701213311.04d9a8bd@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=chrisv@cyberswitching.com \
    --cc=jic23@cam.ac.uk \
    --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 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.