On Thu, May 26, 2011 at 09:27:30PM +0300, Alberto Mardegan wrote: > I would use this code as a starting point (kudos to Javier): > http://gitorious.org/iaps/lsrot/blobs/master/lsrot.c > The code uses the WMI interfaces to get notified of coarse orientation > changes. > But how should these changes be reported to userspace? Should they go > through the input subsystem (I didn't find any suitable key codes to > report these events), or via the /sys filesystem? In the latter case, is > there a convention on naming and reporting data from devices of this kind? If we're not interested in providing continual fine-grained data then the easiest approach may be to present as an input device and then just send updated values whenever you receive the coarse udpate signal. But you probably want to bring this up on LKML so we can make sure everyone's exposing this in the same way. > Secondly, I'd like to add support for reading the accelerometer values, > as it's done here (again, kudos to Javier): > http://gitorious.org/iaps/iaps/blobs/master/iaps.c > I know that no one is happy of directly accessing the raw I/O ports, but > all my attempts of reading these values through the ACPI interfaces or > the EC fields have failed: the fields are always set to 0. Does the accelerometer appear as an ACPI device? > And finally: should the changes above be made to the existing > ideapad-laptop.c file, or should they go to a separate file/module? ideapad-laptop seems appropriate, unless the accelerometer is its own ACPI device that appears in other hardware as well. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
