From: mika.westerberg@linux.intel.com (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: designware: separate ops for system_sleep_pm and runtime_pm
Date: Mon, 18 May 2015 11:28:23 +0300 [thread overview]
Message-ID: <20150518082823.GH1490@lahna.fi.intel.com> (raw)
In-Reply-To: <1431693099-2292-1-git-send-email-jszhang@marvell.com>
On Fri, May 15, 2015 at 08:31:39PM +0800, Jisheng Zhang wrote:
> Commit 1fc2fe204cb9 ("i2c: designware: Add runtime PM hooks") adds
> runtime pm support using the same ops for system sleep and runtime pm.
> When suspend to ram, the i2c host may have been runtime suspended, thus
> i2c_dw_disable() hangs.
It hangs because it has already been powered off, right?
> This patch fixes this issue by separating ops for system sleep pm and
> runtime pm, and in the system suspend/resume path, runtime pm apis are
> used to ensure the device is at correct state.
I can see that this fixes the issue with the platform driver (as the
platform bus core doesn't power on the device automatically as opposed
to other buses, like PCI). However, I'm thinking that can we do better
here.
Instead of powering the device on again, can't we leave it in low power
state? Recently added 'dev->power.direct_complete' may be used to
achieve that, I think.
next prev parent reply other threads:[~2015-05-18 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 12:31 [PATCH] i2c: designware: separate ops for system_sleep_pm and runtime_pm Jisheng Zhang
2015-05-18 8:28 ` Mika Westerberg [this message]
2015-05-19 12:32 ` Jisheng Zhang
2015-05-19 13:15 ` Mika Westerberg
2015-05-20 11:34 ` Jisheng Zhang
2015-05-20 12:05 ` Jisheng Zhang
2015-05-20 12:15 ` Mika Westerberg
2015-05-20 12:34 ` Jisheng Zhang
2015-05-20 12:38 ` Jisheng Zhang
2015-05-20 12:55 ` Mika Westerberg
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=20150518082823.GH1490@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.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).