Hi Matt > > 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. Firstly that would make emailing lm-sensors more sensible than linux-input but what the heck, some of us read both. Also for queries like this copy in the maintainer of the driver you are asking about. > > 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. Gah, Not again! So far we have had two patch sets implementing just this. Looking at the latest from Samu, Eric's patch has been sent on to Andrew Morton for the current merge window (and is listed as being in his mm tree). May even have merged since I last pulled mainline. You have my sympathies as the whole duplicating work thing happens to us all from time to time. The answer is as ever, post early and post often to the relevant mailing lists. (though of course hardly anyone actually keeps to this!) I've cc'd in everyone I know has an interest in this driver for any thing else they might want to add. Jonathan -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
