linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Matt Hsu <matt@0xlab.org>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
	Samu Onkalo <samu.p.onkalo@nokia.com>,
	Eric Piel <eric.piel@tremplin-utc.net>,
	"Trisal, Kalhan" <kalhan.trisal@intel.com>,
	LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: Duplicated driver for LIS302-like device.
Date: Fri, 11 Dec 2009 12:57:52 +0000	[thread overview]
Message-ID: <4B2241D0.3050504@cam.ac.uk> (raw)
In-Reply-To: <4B21B40B.2010007@0xlab.org>

Hi Matt
> 
> Recently I was managed to make LIS302DL device work on Beagleboard.
> It's almost done.
> 
> The last thing I would like to do is to commit the driver to upstream.
> Here comes a problem. I found there's a similar driver named lis3lv02d.c.
> which is located drivers/hwmon/. They are pretty much the same.
> Only registers mapping is different slightly.
Firstly that would make emailing lm-sensors more sensible than linux-input
but what the heck,  some of us read both. Also for queries like this copy
in the maintainer of the driver you are asking about.
> 
> Originally, I plan to use this driver directly instead of implementing
> another lis302dl-like driver.
> Unfortunately, this driver is dependent on ACPI subsystem.
> The target platform for this device is based on ARM.
> Therefore, I could not re-use this driver for my work
> and re-implement it based on I2C interface.
Gah, Not again!  So far we have had two patch sets implementing just
this.  Looking at the latest from Samu, Eric's patch has been sent on
to Andrew Morton for the current merge window (and is listed as being in
his mm tree).  May even have merged since I last pulled mainline.

You have my sympathies as the whole duplicating work thing happens to
us all from time to time.  The answer is as ever, post early and post
often to the relevant mailing lists. (though of course hardly anyone
actually keeps to this!)

I've cc'd in everyone I know has an interest in this driver for any
thing else they might want to add.

Jonathan

  reply	other threads:[~2009-12-11 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11  2:52 Duplicated driver for LIS302-like device Matt Hsu
2009-12-11 12:57 ` Jonathan Cameron [this message]
2009-12-11 13:16   ` Éric Piel
2009-12-14  3:57     ` Matt Hsu
2009-12-14  3:29   ` Matt Hsu

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=4B2241D0.3050504@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=kalhan.trisal@intel.com \
    --cc=linux-input@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=matt@0xlab.org \
    --cc=samu.p.onkalo@nokia.com \
    /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;
as well as URLs for NNTP newsgroup(s).