From: Wolfram Sang <wsa@the-dreams.de>
To: skidnik <skidnik@gmail.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH RFT] i2c: designware: ratelimit 'transfer when suspended' errors
Date: Fri, 26 Apr 2019 04:44:31 +0200 [thread overview]
Message-ID: <20190426024431.GA8275@kunai> (raw)
In-Reply-To: <1a8172c8-3d2e-1897-88dd-d86aa0130ed8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
> Patched, biult and tested. This is the new output:
Thank you!
> This solves system journal flooding, but I still have one core under full
Good, so the patch is OK and a first step.
> load after resume from hibernation. The touchpad attached to that bus works
> perfectly fine after resume.
Interesting that the touchpad works. From a first look, I can't tell why
there is the high CPU load. Analyzing the call trace, I can see a flaw
in the designware PCI driver, though. It uses UNIVERSAL_DEV_PM_OPS(),
but should use SET_LATE_SYSTEM_SLEEP_PM_OPS() like the platform driver,
so it will be a bit later and allow regular devices to suspend.
Andy? Jarkko? Mika?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-26 2:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 16:16 [PATCH RFT] i2c: designware: ratelimit 'transfer when suspended' errors Wolfram Sang
2019-04-24 20:54 ` skidnik
2019-04-25 7:47 ` Wolfram Sang
2019-04-25 8:18 ` Jarkko Nikula
2019-04-25 19:21 ` skidnik
2019-04-26 2:44 ` Wolfram Sang [this message]
2019-04-30 14:09 ` Hans de Goede
2019-04-30 20:15 ` skidnik
2019-05-01 13:59 ` Hans de Goede
2019-05-02 16:31 ` Wolfram Sang
2019-04-26 14:29 ` Andy Shevchenko
2019-05-02 16:29 ` Wolfram Sang
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=20190426024431.GA8275@kunai \
--to=wsa@the-dreams.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=skidnik@gmail.com \
--cc=wsa+renesas@sang-engineering.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.