From: Chris Hudson <chudson@kionix.com>
To: Tony Lindgren <tony@atomide.com>,
Chris Hudson <chudson@kionix.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
amit.kucheria@verdurent.com
Subject: Re: Driver Merge Questions
Date: Mon, 09 Nov 2009 09:54:31 -0500 [thread overview]
Message-ID: <4AF82D27.2010705@kionix.com> (raw)
In-Reply-To: <20091109092621.GY1773@smtp.gmail.com>
Hello Amit,
Thank you for the information.
The driver is just about finished actually; I was going to do some final
testing and pull and submit the patches today. I read the lkml.org
source and it definitely seems like things are in a state of limbo at
the moment (well, as of a few months ago) with regard to sensor
drivers. So, should I submit the code as-is and work on changing it as
necessary with the help of the community, or do I step back and modify
for the iio subsystem before submission? Alternatively, since the code
was originally written for the 2.6.29 Android kernel, should I submit
the current version of the driver to that branch first? Please let me know.
Thank you,
Chris
Amit Kucheria wrote:
> On 09 Nov 03, Tony Lindgren wrote:
>
>> * Chris Hudson <chudson@kionix.com> [091103 06:48]:
>>
>>> Hello all,
>>>
>>> I've never submitted any software to Linux before, but I've been
>>> working on some new accelerometer drivers that should be ready for
>>> review soon (pending company approval). I've read lots of
>>> documentation on patch and driver submissions, but I still have some
>>> questions that I was hoping someone could help me find the answers
>>> to.
>>>
>>> 1- My drivers use i2c for hardware communications, miscdevice for
>>> IOCTLs, and input_dev for data and interrupt status outputs. Most
>>> of the other accelerometer drivers that I've looked at use similar
>>> designs and are located in drivers/hwmon, but I just wanted to
>>> confirm that this is the correct location currently.
>>>
>> Sounds correct.
>>
>
> Unfortunately it will probably get rejected in drivers/hwmon. The maintainer,
> Jean Delavare wants them out of hwmon[1]. It seems that everyone (for the
> moment) is leaning towards a new subsystem called industrial IO
> (drivers/staging/iio) for such drivers.
>
> Please ask Jean before you do the work to make your driver behave like a hwmon
> driver.
>
> Regards,
> Amit
>
>
> [1] http://lkml.org/lkml/2009/7/2/153
>
next prev parent reply other threads:[~2009-11-09 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 14:40 Driver Merge Questions Chris Hudson
2009-11-03 16:58 ` Tony Lindgren
2009-11-09 9:26 ` Amit Kucheria
2009-11-09 12:07 ` Amit Kucheria
2009-11-09 14:54 ` Chris Hudson [this message]
2009-11-09 17:09 ` Amit Kucheria
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=4AF82D27.2010705@kionix.com \
--to=chudson@kionix.com \
--cc=amit.kucheria@verdurent.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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