[PATCH 5/5]: lis302dl-wakeup-configuration.patch

Simon Kagstrom simon.kagstrom at gmail.com
Fri Oct 17 22:18:37 CEST 2008

On Fri, 17 Oct 2008 20:31:47 +0200
Harald Welte <laforge at openmoko.org> wrote:

> > Perhaps it's OK to allow only setting of e.g., the threshold value
> > and let the others be "implicit", i.e., less configurability but
> > leaner interface. Or alternatively put everything in a hex value.
> I don't see anything wrong with first writing to the threshold, etc.
> values and then after all values are set you enable it by writing '1'
> to the x, y or z files.  If there is a problam updating the threshold
> after the wakeup setting is active, you can also reject sysfs writes
> depending on which overall state you are in.

It's no problem as such, just a lot of sysfs files. The wakeups are
only "committed" when the device suspends, so I don't think atomicity
is an issue anyway. Perhaps a subdirectory could be used to keep the
wakeup files and not clutter the rest of the directory.

The wakeup doesn't currently work anyhow on the freerunner for other
(unknown) reasons.

// Simon

More information about the openmoko-kernel mailing list