summaryrefslogtreecommitdiffstats
path: root/scripts/checkincludes.pl
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2013-06-10 07:39:09 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-06-17 12:49:44 -0700
commita630fbfbb1beeffc5bbe542a7986bf2068874633 (patch)
tree5697270282fb15c8a6bfe218f1b031046fb62f52 /scripts/checkincludes.pl
parent80c48497f279a7ca25bfc6d2f9cae335a018ae17 (diff)
downloadop-kernel-dev-a630fbfbb1beeffc5bbe542a7986bf2068874633.zip
op-kernel-dev-a630fbfbb1beeffc5bbe542a7986bf2068874633.tar.gz
serial: omap: Fix device tree based PM runtime
In the runtime_suspend function pdata is not being used, and also blocks the function in device tree based booting. Fix it by removing the unused pdata from the runtime_suspend function. Further, context loss count is not being passed in pdata, so let's just reinitialize the port every time for those case. This can be further optimized later on for the device tree case by adding detection for the hardware state and possibly by adding a driver specific autosuspend timeout. And doing this, we can then make the related dev_err into a dev_dbg message instead of an error. In order for the wake-up events to work, we also need to set autosuspend_timeout to -1 if 0, and also device_init_wakeup() as that's not being done by the platform init code for the device tree case. Note that this does not affect legacy booting, and in fact might make it work for the cases where the context loss info is not being passed in pdata. Thanks to Kevin Hilman <khilman@linaro.org> for debugging and suggesting fixes for the autosuspend_timeout and device_init_wakeup() related initializiation. Reviewed-by: Kevin Hilman <khilman@linaro.org> Tested-by: Kevin Hilman <khilman@linaro.org> Signed-off-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/checkincludes.pl')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud