From 5d5fb0b5646aed4cb074eb317fc09170645c7a3f Mon Sep 17 00:00:00 2001 From: patacongo Date: Mon, 14 May 2012 21:57:38 +0000 Subject: Improved thresholding logic in the STMPE11 driver; NxWM: Oops minimizing wrong application git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4737 42af7a65-404d-4744-a932-0658087f49c3 --- nuttx/configs/README.txt | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'nuttx/configs/README.txt') diff --git a/nuttx/configs/README.txt b/nuttx/configs/README.txt index 15ff30e11..fc85e89e1 100644 --- a/nuttx/configs/README.txt +++ b/nuttx/configs/README.txt @@ -814,6 +814,13 @@ defconfig -- This is a configuration file similar to the Linux Disable driver temperature sensor functionality. CONFIG_STMPE11_REGDEBUG Enabled very low register-level debug output. Requires CONFIG_DEBUG. + CONFIG_STMPE11_THRESHX and CONFIG_STMPE11_THRESHY + STMPE11 touchscreen data comes in a a very high rate. New touch positions + will only be reported when the X or Y data changes by these thresholds. + This trades reduces data rate for some loss in dragging accuracy. The + STMPE11 is configure for 12-bit values so the raw ranges are 0-4095. So + for example, if your display is 320x240, then THRESHX=13 and THRESHY=17 + would correspond to one pixel. Default: 12 Analog Devices -- cgit v1.2.3