aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorVignesh R <vigneshr@ti.com>2018-04-02 08:20:37 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-04-23 04:12:14 -0400
commit09d8b2bdbc5c61dd6289d78ab4cb57d22dd5e0e6 (patch)
treef6a53b5f845efc58e4c1877245ebb160c5ed50a0 /tools/perf/scripts/python/export-to-sqlite.py
parentb7639b0b15ddd1a4686b0142e70dfb122eefc88f (diff)
serial: 8250: omap: Provide ability to enable/disable UART as wakeup source
Enable/Clear module level UART wakeup in UART_OMAP_WER register based on return value of device_may_wakeup() in .suspend(). This allows userspace to use sysfs to control the ability of UART to wakeup the system from deep sleep state. Register is restored back in .startup() call that happens as part of resume sequence. With this patch, userspace can control UART wakeup capability via sysfs: To enable wakeup capability: echo enabled > /sys/class/tty/ttyXX/device/power/wakeup For disabling wakeup capability: echo disabled > /sys/class/tty/ttyXX/device/power/wakeup Note that the UART wakeup events configured in the 8250 hardware only work for idle modes that do not cut off power for the UART. For deeper idle states, dedicated padconf wakeirqs must be used. Or in some cases the UART RX pin can be remuxed to GPIO input if the GPIO block stays powered. Signed-off-by: Vignesh R <vigneshr@ti.com> Tested-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions