Hi Peter,
On Wednesday 08 July 2015 07:34 PM, Peter Hurley wrote:
Hi Sekhar,
On 07/06/2015 05:47 AM, Sekhar Nori wrote:
omap_device infrastructure has a suspend_noirq hook which
runtime suspends all devices late in the suspend cycle (see
_od_suspend_noirq() in
Hi Sekhar,
On 07/06/2015 05:47 AM, Sekhar Nori wrote:
omap_device infrastructure has a suspend_noirq hook which
runtime suspends all devices late in the suspend cycle (see
_od_suspend_noirq() in arch/arm/mach-omap2/omap_device.c)
Why is omap2 the only arch/SoC that does this; ie., call the
omap_device infrastructure has a suspend_noirq hook which
runtime suspends all devices late in the suspend cycle (see
_od_suspend_noirq() in arch/arm/mach-omap2/omap_device.c)
This leads to a NULL pointer exception in 8250_omap driver
since by the time omap8250_runtime_suspend() is called,
