View Single Post
Old 12-27-2011, 08:55 AM   #3
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
In the embedded market, such sensors are typically connected to the SoC via an I2C bus (sometimes SPI, but since this isn't really a timing critical device, I think it is probably I2C). Linux might offer access via its generic I2C interface.

Also note that the input event interface is quite standardized on Linux. I'd suggest to compile evtest (a quick search retrieves this: http://cgit.freedesktop.org/~whot/evtest/) and have it dump the data. It might make sense at it is already. If so, and if you're working with C/C++ codebases, there's linux/input.h in the kernel headers (though it will probably only provide you a struct and some constants).
hawhill is offline   Reply With Quote