From: John Stultz <john.stultz@linaro.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2] i2c: designwear: Fix clk warning on suspend/resume
Date: Thu, 2 Mar 2017 15:39:49 -0800 [thread overview]
Message-ID: <CALAqxLUBBZOPvZ_Lu2X5ygoorubKdRW3GHzv41WHdOJf-z4PZA@mail.gmail.com> (raw)
In-Reply-To: <e0c3968e-cff1-5cc7-9c42-1c3858e76077@linux.intel.com>
On Tue, Feb 14, 2017 at 7:30 AM, Jarkko Nikula
<jarkko.nikula@linux.intel.com> wrote:
> On 14.02.2017 06:05, John Stultz wrote:
>>
>> On my HiKey board, I'm seeing clk warnings on suspend/resume,
>> which seem to be caused by runtime pm suspending the device,
>> then the same suspend hook being called again on suspend time.
>>
>> This patch fixes this by setting the SYSTEM_SLEEP_PM_OPS to
>> using pm_runtime_force_suspend and pm_runtime_force_resume.
>>
>> Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
>> Cc: Wolfram Sang <wsa@the-dreams.de>
>> Cc: linux-i2c@vger.kernel.org
>> Suggested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>> Signed-off-by: John Stultz <john.stultz@linaro.org>
>> ---
>> v2: Switch to suggested fix by Jarkko.
>>
>> drivers/i2c/busses/i2c-designware-platdrv.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c
>> b/drivers/i2c/busses/i2c-designware-platdrv.c
>> index 6ce4313..09f27ec 100644
>> --- a/drivers/i2c/busses/i2c-designware-platdrv.c
>> +++ b/drivers/i2c/busses/i2c-designware-platdrv.c
>> @@ -362,7 +362,7 @@ static int dw_i2c_plat_resume(struct device *dev)
>> static const struct dev_pm_ops dw_i2c_dev_pm_ops = {
>> .prepare = dw_i2c_plat_prepare,
>> .complete = dw_i2c_plat_complete,
>> - SET_SYSTEM_SLEEP_PM_OPS(dw_i2c_plat_suspend, dw_i2c_plat_resume)
>> + SET_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend,
>> pm_runtime_force_resume)
>> SET_RUNTIME_PM_OPS(dw_i2c_plat_suspend, dw_i2c_plat_resume, NULL)
>> };
>
>
> We need to hold this a bit. I've been debugging this on our platforms but
> haven't figured out yet how to fix a regression it is causing with
> drivers/acpi/acpi_lpss.c :-(
>
> With this change in i2c-designware-platdrv.c the suspend path in acpi_lpss.c
> changes. First it saves its the register context in
> acpi_lpss_runtime_suspend() and powers down. Then the device which is now
> off will save again the register context (now reads full of 0xff...) in
> acpi_lpss_suspend_late() and restores wrong context (0xff...) when resuming.
Hey,
Just wanted to follow up to see if any progress was made on this
issue? Anything you need from me?
thanks
-john
prev parent reply other threads:[~2017-03-02 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 4:05 [PATCH v2] i2c: designwear: Fix clk warning on suspend/resume John Stultz
2017-02-14 15:30 ` Jarkko Nikula
2017-03-02 23:39 ` John Stultz [this message]
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=CALAqxLUBBZOPvZ_Lu2X5ygoorubKdRW3GHzv41WHdOJf-z4PZA@mail.gmail.com \
--to=john.stultz@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@the-dreams.de \
/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).