From: Beata Michalska <b.k.m.devel@gmail.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: wsa@the-dreams.de, kgene@kernel.org,
linux-samsung-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
lars@metafoo.de
Subject: Re: [PATCH v2] i2c: Mark adapter devices with pm_runtime_no_callbacks
Date: Thu, 16 Apr 2015 14:28:02 +0200 [thread overview]
Message-ID: <552FAAD2.80407@gmail.com> (raw)
In-Reply-To: <1429185919-26098-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On 04/16/2015 02:05 PM, Charles Keepax wrote:
> Commit 523c5b89640e ("i2c: Remove support for legacy PM") removed the PM
> ops from the bus type, which causes the pm operations on the s3c2410
> adapter device to fail (-ENOSUPP in rpm_callback). The adapter device
> doesn't get bound to a driver and as such can't have its own pm_runtime
> callbacks. Previously this was fine as the bus callbacks would have been
> used, but now this can cause devices which use PM runtime and are
> attached over I2C to fail to resume.
>
> This commit fixes this issue by marking all adapter devices with
> pm_runtime_no_callbacks, since they can't have any.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
>
> Changes since v1:
> - Simple mark all adapter devices with pm_runtime_no_callbacks in the i2c
> core
>
> Thanks,
> Charles
>
> drivers/i2c/i2c-core.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> index 1672e6b..eac3331 100644
> --- a/drivers/i2c/i2c-core.c
> +++ b/drivers/i2c/i2c-core.c
> @@ -1410,6 +1410,8 @@ static int i2c_register_adapter(struct i2c_adapter *adap)
>
> dev_dbg(&adap->dev, "adapter [%s] registered\n", adap->name);
>
> + pm_runtime_no_callbacks(&adap->dev);
> +
> #ifdef CONFIG_I2C_COMPAT
> res = class_compat_create_link(i2c_adapter_compat_class, &adap->dev,
> adap->dev.parent);
Thereis at least one more casewhen an I2C device fails to resume due
to bus callbacks being dropped(like fimc-is-i2c driver for exynos4-is,
the same scenario), so I'm glad to see it's being handled in on place
-it saves the trouble.
BR
Beata
next prev parent reply other threads:[~2015-04-16 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 12:05 [PATCH v2] i2c: Mark adapter devices with pm_runtime_no_callbacks Charles Keepax
2015-04-16 12:28 ` Beata Michalska [this message]
2015-04-22 7:55 ` Wolfram Sang
2015-04-22 7:54 ` 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=552FAAD2.80407@gmail.com \
--to=b.k.m.devel@gmail.com \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=kgene@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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).