summaryrefslogtreecommitdiff
path: root/drivers/input/misc/twl6040-vibra.c
diff options
context:
space:
mode:
authorMark Brown <broonie@linaro.org>2014-04-25 10:37:56 +0400
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2014-05-15 03:39:47 +0400
commitc728601ea3531dc1f0dcd74c1db1e85e59f2be68 (patch)
tree2dda2b29bb64297694edea6c4e96d5bdca8bd343 /drivers/input/misc/twl6040-vibra.c
parentd0f0a1601449ded5a7bcaf954f9c75e6fd9d5183 (diff)
downloadlinux-c728601ea3531dc1f0dcd74c1db1e85e59f2be68.tar.xz
Input: ads7877 - remove bitrotted comment
While searching for users of spi_async() I found a reference in the ad7877 driver to using it to initiate data transfer from the interrupt handler. However there is no code for this, instead the interrupt handler is a threaded handler and uses spi_sync() instead. Remove the bitrotted comment, though in actual fact the use case mentioned is a great use for spi_async() since it would cut down on latency handling the interrupt by saving us a context switch before we start SPI. This was previously implemented, it was removed in commit b534422b2d11 (Input: ad7877 - switch to using threaded IRQ) for code complexity reasons. It may be better to revert that commit instead. Signed-off-by: Mark Brown <broonie@linaro.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input/misc/twl6040-vibra.c')
0 files changed, 0 insertions, 0 deletions