From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Wolfram Sang <wsa@the-dreams.de>, Len Brown <lenb@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 1/2] i2c: designware: Never suspend i2c-busses used for accessing the system PMIC
Date: Thu, 9 Mar 2017 16:24:22 +0200 [thread overview]
Message-ID: <728a5859-c4fe-b22c-0dd2-94c48e131134@linux.intel.com> (raw)
In-Reply-To: <20170308084713.4815-2-hdegoede@redhat.com>
On 03/08/17 10:47, Hans de Goede wrote:
> Currently we are already setting a pm_runtime_disabled flag and disabling
> runtime-pm for i2c-busses used for accessing the system PMIC on x86.
> But this is not enough, there are ACPI opregions which may want to access
> the PMIC during late-suspend and early-resume, so we need to completely
> disable pm to be safe.
>
> This commit renames the flag from pm_runtime_disabled to pm_disabled and
> adds the following new behavior if the flag is set:
>
> 1) Call dev_pm_syscore_device(dev, true) which disables normal suspend /
> resume and remove the pm_runtime_disabled check from dw_i2c_plat_resume
> since that will now never get called. This fixes suspend_late handlers
> which use ACPI PMIC opregions causing errors like these:
>
> PM: Suspending system (freeze)
> PM: suspend of devices complete after 1127.751 msecs
> i2c_designware 808622C1:06: timeout waiting for bus ready
> ACPI Exception: AE_ERROR, Returned by Handler for [UserDefinedRegion]
> acpi 80860F14:02: Failed to change power state to D3hot
> PM: late suspend of devices failed
>
> 2) Set IRQF_NO_SUSPEND irq flag. This fixes resume_early handlers which
> handlers which use ACPI PMIC opregions causing errors like these:
>
> PM: resume from suspend-to-idle
> i2c_designware 808622C1:06: controller timed out
> ACPI Exception: AE_ERROR, Returned by Handler for [UserDefinedRegion]
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/i2c/busses/i2c-designware-baytrail.c | 2 +-
> drivers/i2c/busses/i2c-designware-core.c | 11 +++++++++--
> drivers/i2c/busses/i2c-designware-core.h | 4 ++--
> drivers/i2c/busses/i2c-designware-platdrv.c | 10 ++++------
> 4 files changed, 16 insertions(+), 11 deletions(-)
>
Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2017-03-09 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 8:47 [PATCH v2 0/2] i2c: designware: Never suspend i2c-busses used for system PMICs Hans de Goede
2017-03-08 8:47 ` [PATCH v2 1/2] i2c: designware: Never suspend i2c-busses used for accessing the system PMIC Hans de Goede
2017-03-09 14:24 ` Jarkko Nikula [this message]
2017-03-09 14:39 ` Wolfram Sang
2017-03-09 15:02 ` Jarkko Nikula
2017-03-08 8:47 ` [PATCH v2 2/2] i2c: designware: Disable pm for PMIC i2c-bus even if there is no _SEM method Hans de Goede
2017-03-09 15:00 ` Jarkko Nikula
2017-03-09 15:02 ` Jarkko Nikula
2017-03-10 2:33 ` Lan Tianyu
2017-03-10 7:49 ` Hans de Goede
2017-03-10 11:34 ` Lan, Tianyu
2017-03-10 20:46 ` Hans de Goede
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=728a5859-c4fe-b22c-0dd2-94c48e131134@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=tiwai@suse.de \
--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).