summaryrefslogtreecommitdiffstats
path: root/drivers/staging/fbtft/fbtft.h
diff options
context:
space:
mode:
authorAndy Shevchenko2017-01-19 11:45:41 +0100
committerGreg Kroah-Hartman2017-01-19 12:50:27 +0100
commit9ed2bfb3e39bfbe79ddcf2d03eef28242ea60253 (patch)
tree2322a2986a6509c2067cd25644f519b6f4f83afa /drivers/staging/fbtft/fbtft.h
parentstaging: rtl8188eu: core: Remove NULL test before vfree (diff)
downloadkernel-qcow2-linux-9ed2bfb3e39bfbe79ddcf2d03eef28242ea60253.tar.gz
kernel-qcow2-linux-9ed2bfb3e39bfbe79ddcf2d03eef28242ea60253.tar.xz
kernel-qcow2-linux-9ed2bfb3e39bfbe79ddcf2d03eef28242ea60253.zip
staging: fbtft: convert fbtft_reset() to be non-atomic
First of all, fbtft in current state doesn't allow to override GPIOs to be optional, like "reset" one. It might be a bug somewhere, but rather out of scope of this fix. Second, not all GPIOs available on the board would be SoC based, some of them might sit on I2C GPIO expanders, for example, on Intel Edison/Arduino, and thus any communication with them might sleep. Besides that using udelay() and mdelay() is kinda resource wasteful. Summarize all of the above, convert fbtft_reset() function to non-atomic variant by using gpio_set_value_cansleep(), usleep_range(), and msleep(). Reviewed-by: Noralf Trønnes <noralf@tronnes.org> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/fbtft/fbtft.h')
0 files changed, 0 insertions, 0 deletions