My only complaint with the iio: I have an ancient driver for the lis3l02dq alone in iio from the start that will also get eaten up by Daren’s new driver and the ability to test on that part on spi. I will try to clean it up and get it out for an RFC soon as this is my first real driver, I’m sure your input would be helpful. Product is in design stage Target: Intelligent Pedometer Platform Driver. When adding new entries keep the list in alphabetical order. If so, the module will be called stk
|Date Added:||20 February 2008|
|File Size:||30.93 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
To compile this driver as a module, choose M here: Product is in volume production. The device features ultra low-power operational modes that allow advanced power saving and smart sleep to wake-up functions. As you say, an input wrapper could be provided.
Linux source code: LISDLH identifier (v) – Bootlin
Limited Engineering samples available Preview: To compile this driver as a module, choose M. Press h to open a hovercard with more details. It would be good to get the simple stuff right and in tree so it doesn’t bitrot as I work on the rest. There will be a few iterations of this driver necessary before it can replace the existing one. Will probably start keeping a ‘what changed and how to follow’ document though Computers and Peripherals Data Center. Hence he may initially want to do a separate driver with that keeping in mind the aim of mergining in the existing driver.
This driver is only implementing accelerometer part, which has its own address and register map. Now that the IIO subsystem is out of staging, it might be a right place.
linux-kernel – Re: LISDLH accelerometer driver, IIO or not?
Maybe we leave this question for now I will try to clean it up and get it out for an RFC soon as this is my first real driver, I’m sure your input would be helpful. Thankfully they didn’t manage to block the LIS driver lis331dlg this mess. I believe that should meet with everyone’s suggestions. Not sure if a joystick llnux the right option, but that’s more one for Dmitry to comment on. I’ve rewritten most of the driver to work with the 3. Sure, that was just off the cuff.
The self-test capability allows the user to check the functioning of the sensor in the final application. Say yes here to build support for kis331dlh following Freescale 3-axis. Marketing proposal for customer feedback.
[PATCH] staging: lis331dlh: add lis331dlh driver
This driver is only implementing accelerometer part, which has. You signed out in another tab or window.
I have an ancient driver for the lis3l02dq alone in iio from the start that will also get eaten up by Daren’s new driver and the ability to test on that part on spi.
Like option 2, this driver is not likely to be as configurable as the IIO driver. Product is in volume production only to support customers ongoing production. Gah sounds like a bug snuck in.
I think bizarre and interesting things could certainly be done with the input system, but I’d prefer to expose the lower level features of the chip linuux not dictate how the chip is used. One thing I would like to understand better is what sort of interface does userspace current expect. Just had a look. IMHO, the main steps are: I’m not sure what you mean by “rate of change of acceleration thresholds”, but as the thresholds for this device are per-interrupt not axis nor direction and only 6 bits while the axis values are s I agree that this sort of device should have an input interface.