summaryrefslogtreecommitdiff
path: root/drivers/crypto/omap-sham.c
diff options
context:
space:
mode:
authorJuergen Beisert <jbe@pengutronix.de>2014-02-24 14:39:00 +0000
committerJonathan Cameron <jic23@kernel.org>2014-02-24 21:55:50 +0000
commit760dbe1dcb6d3dd3ead73dc69b23f206b52273bb (patch)
tree2ee320fa5e1768c9374cc73bb64503440e6cbde3 /drivers/crypto/omap-sham.c
parente194fd8a5d8e0a7eeed239a8534460724b62fe2d (diff)
staging:iio:adc:MXS:LRADC: fix touchscreen statemachinefixes-for-3.14d
Releasing the touchscreen lets the internal statemachine left in a wrong state. Due to this the release coordinate will be reported again by accident when the next touchscreen event happens. This change sets up the correct state when waiting for the next touchscreen event. This has led to reported issues with calibrating the touchscreen. Bug was introduced somewhere in the series that began with 18da755de59b406ce2371a55fb15ed676eb08ed2 Staging/iio/adc/touchscreen/MXS: add proper clock handling in which the way this driver worked was substantially changed to be interrupt driven rather than relying on a busy loop. This was a regression in the 3.13 kernel. Signed-off-by: Juergen Beisert <jbe@pengutronix.de> Tested-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> Cc: stable@vger.kernel.org Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Diffstat (limited to 'drivers/crypto/omap-sham.c')
0 files changed, 0 insertions, 0 deletions