linux-kernel - Re: LIS331DLH accelerometer driver, IIO or not?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FC0C422.8080605@tremplin-utc.net>
Date:	Sat, 26 May 2012 13:53:06 +0200
From:	Éric Piel <eric.piel@...mplin-utc.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	Darren Hart <dvhart@...ux.intel.com>,
	"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 25-05-12 07:10, Greg Kroah-Hartman wrote:
> On Thu, May 24, 2012 at 09:29:53PM -0700, Darren Hart wrote:
>> I'm working to enable the LIS331DLH accelerometer on the Fish River
>> Island II embedded atom development kit.
>>
>> I am more interested in enabling people to do bizarre and interesting
>> things with the device, so I'm leaning toward continuing with my IIO
>> implementation.
>
> 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" ;-) Actually, the 
main problem is that there seemed to be no maintainer interested in 
taking care of accelerometer devices. Now that the IIO subsystem is out 
of staging, it might be a right place. That said, I don't know much 
about the user interface to IIO. I know that I liked the idea of having 
an joystick device created for an accelerometer because that allows to 
get many programs to access the device almost without any modifications.

I'd happy to help merge the lis3lv02d driver into IIO. IMHO, the main 
steps are:
  * make sure all the various buses are supported (e.g., I²C, SPI, and 
also "ACPI-HP")
  * ensure the various versions of the accelerometer are supported 
(there are 3 supported currently)
  * check that the driver is automatically loaded on HP laptops (via 
ACPI entry)
  * for each of the current interfaces decide if they should be ported 
or dropped (/dev/js*, /dev/freefall, sysfs...)

What do you think Jonathan?

Cheers,
Éric
--
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/