From: Matt Hsu <matt@0xlab.org>
To: linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com
Subject: Duplicated driver for LIS302-like device.
Date: Fri, 11 Dec 2009 10:52:59 +0800 [thread overview]
Message-ID: <4B21B40B.2010007@0xlab.org> (raw)
Hi all,
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.
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.
My question is, is this a duplicated driver for upstream
if I send patches for this driver without any ACPI dependency?
Cheers,
Matt
next reply other threads:[~2009-12-11 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 2:52 Matt Hsu [this message]
2009-12-11 12:57 ` Duplicated driver for LIS302-like device Jonathan Cameron
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=4B21B40B.2010007@0xlab.org \
--to=matt@0xlab.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@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 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).