public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Chris Hudson <chudson@kionix.com>
Cc: Jean Delvare <khali@linux-fr.org>,
	linux-omap@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [RFC PATCH 1/3] hwmon:driver support for Kionix kxte9 accelerometer
Date: Tue, 10 Nov 2009 19:00:23 +0000	[thread overview]
Message-ID: <4AF9B847.3070008@cam.ac.uk> (raw)
In-Reply-To: <4AF9B5E3.1060902@kionix.com>

Chris Hudson wrote:
> 
> 
> Jean Delvare wrote:
>> On Tue, 10 Nov 2009 13:28:47 -0500, chudson@kionix.com wrote:
>>  
>>> From: Chris Hudson <chudson@kionix.com>
>>>
>>> This is a request for comments for adding driver support for the
>>> Kionix KXTE9 digital tri-axis accelerometer.  This part features
>>> built-in tilt position (orientation), wake-up and back-to-sleep
>>> algorithms, which can trigger a user-configurable physical
>>> interrupt.  The driver uses i2c for device communication, a misc node
>>> for IOCTLs, and input nodes for reporting acceleration data and
>>> interrupt status information.
>>>
>>> Signed-off-by: Chris Hudson <chudson@kionix.com>
>>>     
>>
>> Nack. We want less accelerometer drivers polluting drivers/hwmon, not
>> more.
>>
>>   
> Thank you Jean for your quick reply.  I have seen some accelerometer
> drivers in drivers/staging/iio/accel; is this where they are all being
> moved to?
> 
Sorry Chris, meant to send my reply to the list as this question keeps
coming up.

That somewhat depends on the intended application.  The purpose of IIO
is to provide a more general sensors framework, handling reasonably high
capture speeds and things like triggering and ring buffers.  As things
currently stand it isn't the place for devices that are principally being
used for input or as wake up triggers. I'd be perfectly happy if there
was a driver in IIO for this chip, (we already have a basic kxsd9 driver)
but the support for much of what you describe in your summary would be
pretty much unconnected to that subsystem. Not necessarily a problem
though handling exactly what was getting the data at a given moment
might get fiddly.
 
Jonathan

  reply	other threads:[~2009-11-10 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 18:28 [RFC PATCH 1/3] hwmon:driver support for Kionix kxte9 accelerometer chudson
2009-11-10 18:28 ` [RFC PATCH 2/3] mach-omap2:kxte9 accelerometer support for OMAP ZoomII chudson
2009-11-10 18:28   ` [RFC PATCH 3/3] mach-omap2:mux support for kxte9 accelerometer on " chudson
2009-11-10 18:35 ` [lm-sensors] [RFC PATCH 1/3] hwmon:driver support for Kionix kxte9 accelerometer Jean Delvare
2009-11-10 18:50   ` Chris Hudson
2009-11-10 19:00     ` Jonathan Cameron [this message]
2009-11-10 20:32       ` Chris Hudson
2009-11-10 21:39         ` Jean Delvare
2009-11-10 21:54           ` Chris Hudson
2009-11-11 14:14             ` Jonathan Cameron
2009-11-11 14:21               ` Chris Hudson
2009-11-12 21:10 ` Jonathan Cameron

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=4AF9B847.3070008@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=chudson@kionix.com \
    --cc=khali@linux-fr.org \
    --cc=linux-omap@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