summaryrefslogtreecommitdiff
path: root/nuttx/drivers/input
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2014-07-10 08:42:25 -0600
committerGregory Nutt <gnutt@nuttx.org>2014-07-10 08:42:25 -0600
commit17b702fc22453e1e5dd577355da802014d3dc98d (patch)
treedabba34559bc7899b784e7e0302591e3c4c6713d /nuttx/drivers/input
parent9c95662cd3e400ea0d0251240e82750de655657c (diff)
downloadpx4-nuttx-17b702fc22453e1e5dd577355da802014d3dc98d.tar.gz
px4-nuttx-17b702fc22453e1e5dd577355da802014d3dc98d.tar.bz2
px4-nuttx-17b702fc22453e1e5dd577355da802014d3dc98d.zip
SAMA5D4-EK: The maXTouch controller and test is now enabled by default in the NSH configuration
Diffstat (limited to 'nuttx/drivers/input')
-rw-r--r--nuttx/drivers/input/mxt.c11
1 files changed, 11 insertions, 0 deletions
diff --git a/nuttx/drivers/input/mxt.c b/nuttx/drivers/input/mxt.c
index 653973017..0105bf119 100644
--- a/nuttx/drivers/input/mxt.c
+++ b/nuttx/drivers/input/mxt.c
@@ -761,6 +761,17 @@ static void mxt_touch_event(FAR struct mxt_dev_s *priv,
ivdbg("ndx=%u status=%02x pos(%u,%u) area=%u pressure=%u\n",
ndx, status, x, y, area, pressure);
+ /* The normal sequence that we would see for a touch would be something
+ * like:
+ *
+ * 1. MXT_DETECT + MXT_PRESS
+ * 2. MXT_DETECT + MXT_AMP
+ * 3. MXT_DETECT + MXT_MOVE + MXT_AMP
+ * 4. MXT_RELEASE
+ *
+ * So we really only need to check MXT_DETECT to drive this state machine.
+ */
+
/* Is this a loss of contact? */
sample = &priv->sample[ndx];