From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] spi:pl022: Disable/Enable functional clock from suspend/resume
Date: Wed, 26 Sep 2012 13:19:46 +0100 [thread overview]
Message-ID: <20120926121946.GO4428@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdampxUw0=NO6cs679C-r0_AnPEaTYVc+GppRkKGn32p-w@mail.gmail.com>
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.
> The semantics between runtime suspend/resume and
> ordinary suspend/resume are unclear to me, it seems like
> this is all up to the drivers and busses to figure out. Like
> you weren't supposed to use both at the same time.
This was clarified at some point relatively recently with the above
(which is essentially the same as the solution you describe).
next prev parent reply other threads:[~2012-09-26 12:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 11:24 [PATCH 0/2] ARM: AMBA: Fix clock disable/enable issue in conventional suspend/resume Vipul Kumar Samar
2012-09-26 11:24 ` [PATCH 1/2] spi:pl022: Disable/Enable functional clock from suspend/resume Vipul Kumar Samar
2012-09-26 12:17 ` Linus Walleij
2012-09-26 12:19 ` Mark Brown [this message]
2012-09-26 12:41 ` Linus Walleij
2012-09-27 17:03 ` Mark Brown
2012-09-26 14:08 ` viresh kumar
2012-09-26 14:13 ` Linus Walleij
2012-09-26 11:24 ` [PATCH 2/2] ARM: ABMA: Disable/Enable interface " Vipul Kumar Samar
2012-09-26 12:38 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120926121946.GO4428@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).