On Wed, Sep 26, 2012 at 2:19 PM, Mark Brown <broo...@opensource.wolfsonmicro.com> wrote: > On Wed, Sep 26, 2012 at 02:17:36PM +0200, Linus Walleij wrote: >> On Wed, Sep 26, 2012 at 1:24 PM, Vipul Kumar Samar > >> > SPI functional clock must be disalble/enable in non RTPM suspend/resume >> > hooks. Currently it is only done for RTPM cases. > >> > This patch add support to disable/enbale clock for conventional >> > suspend/resume calls. > >> Cross dependency between runtime suspend/resume and >> common suspend/resume. Oh the horror ... > > This should be fine, we runtime resume before we suspend. (...) > This was clarified at some point relatively recently with the above > (which is essentially the same as the solution you describe).
Oh. How come that whenever I poke my nose into this stuff I feel like a compleat n00b X-D Can you point me to the relevant posts/doc so I can read up on it, would be much appreciated! Yours, Linus Walleij ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general