them as any other INPUT_PROP_BUTTONPAD device.
INPUT_PROP_ACCELEROMETER
- -------------------------
+ ------------------------
+
Directional axes on this device (absolute and/or relative x, y, z) represent
-accelerometer data. All other axes retain their meaning. A device must not mix
+accelerometer data. Some devices also report gyroscope data, which devices
+can report through the rotational axes (absolute and/or relative rx, ry, rz).
+
+All other axes retain their meaning. A device must not mix
regular directional axes and accelerometer axes on the same event node.
- Guidelines:
+ Guidelines
==========
+
The guidelines below ensure proper single-touch and multi-finger functionality.
For multi-touch functionality, see the multi-touch-protocol.txt document for
more information.
Effects are file descriptor specific.
- See <uapi/linux/input.h> for a description of the ff_effect struct. You should
- also find help in a few sketches, contained in files shape.fig and
- interactive.fig. You need xfig to visualize these files.
-See <linux/input.h> for a description of the ff_effect struct. You should also
-find help in a few sketches, contained in files shape.svg and interactive.svg:
++See <uapi/linux/input.h> for a description of the ff_effect struct. You
++should also find help in a few sketches, contained in files shape.svg
++and interactive.svg:
+
+ .. figure:: shape.svg
- 3.3 Removing an effect from the device
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- int ioctl(int fd, EVIOCRMFF, effect.id);
+ Shape
+
+ .. figure:: interactive.svg
+
+ Interactive
+
+
+ Removing an effect from the device
+ ----------------------------------
+
+ ::
+
+ int ioctl(int fd, EVIOCRMFF, effect.id);
This makes room for new effects in the device's memory. Note that this also
stops the effect if it was playing.