[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FC19C86.7040904@linux.intel.com>
Date: Sat, 26 May 2012 20:16:22 -0700
From: Darren Hart <dvhart@...ux.intel.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Éric Piel <eric.piel@...mplin-utc.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"lkml, " <linux-kernel@...r.kernel.org>,
Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Carmine Iascone <carmine.iascone@...com>,
Matteo Dameno <matteo.dameno@...com>
Subject: Re: LIS331DLH accelerometer driver, IIO or not?
On 05/26/2012 06:59 AM, Alan Cox wrote:
>>> Make it an IIO driver and then we can delete the misc driver, which
>>> shouldn't have snuck in there in the first place :)
>>>
>>
>> To be more fair to the misc driver, I wouldn't say it snucked in there,
>> but more "it ended up there as the least worse place" ;-)
>
> Because IIO spent forever in staging, as well as blocking lots of other
> driver work and meaning tons of drivers are now not to be found anywhere
> but obscure git trees. Thankfully they didn't manage to block the LIS
> driver during this mess.
>
> Until all the needed support for the LIS IIO driver exists outside of
> staging the driver needs to stay where it is and without IIO
> dependancies. It is not acceptable to cripple existing working code with
> staging tree dependencies.
Agreed. There will be a few iterations of this driver necessary before
it can replace the existing one.
>
> Hopefully commit a980e046098b0a40eaff5e4e7fcde6cf035b7c06 has finally set
> the basis for this happening when it hits mainline.
Yes, after dusting off the 2.6.34 based IIO driver I started with and
moving it forward to 3.2, I am THRILLED to see the IIO core now in
mainline :-)
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists