summaryrefslogtreecommitdiffstats
path: root/Documentation/input
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/input')
-rw-r--r--Documentation/input/event-codes.rst5
-rw-r--r--Documentation/input/ff.rst5
-rw-r--r--Documentation/input/input-programming.rst4
3 files changed, 9 insertions, 5 deletions
diff --git a/Documentation/input/event-codes.rst b/Documentation/input/event-codes.rst
index 00b88f1..a8c0873 100644
--- a/Documentation/input/event-codes.rst
+++ b/Documentation/input/event-codes.rst
@@ -350,7 +350,10 @@ 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
diff --git a/Documentation/input/ff.rst b/Documentation/input/ff.rst
index c30f185..6a265a6 100644
--- a/Documentation/input/ff.rst
+++ b/Documentation/input/ff.rst
@@ -126,8 +126,9 @@ allocate a new effect.
Effects are file descriptor specific.
-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
diff --git a/Documentation/input/input-programming.rst b/Documentation/input/input-programming.rst
index 57dbab6..45a4c6e 100644
--- a/Documentation/input/input-programming.rst
+++ b/Documentation/input/input-programming.rst
@@ -172,8 +172,8 @@ It's reported to the input system via::
input_report_key(struct input_dev *dev, int code, int value)
-See linux/input.h for the allowable values of code (from 0 to KEY_MAX).
-Value is interpreted as a truth value, ie any nonzero value means key
+See uapi/linux/input-event-codes.h for the allowable values of code (from 0 to
+KEY_MAX). Value is interpreted as a truth value, ie any nonzero value means key
pressed, zero value means key released. The input code generates events only
in case the value is different from before.
OpenPOWER on IntegriCloud