From: Wolfram Sang <wsa@the-dreams.de>
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-i2c@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Alok Chauhan <alokc@codeaurora.org>
Subject: Re: [PATCH v2] i2c: i2c-qcom-geni: Fix runtime PM mismatch with child devices
Date: Fri, 9 Nov 2018 17:04:32 +0100 [thread overview]
Message-ID: <20181109160432.GI1031@kunai> (raw)
In-Reply-To: <20181102205732.116851-1-swboyd@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
On Fri, Nov 02, 2018 at 01:57:32PM -0700, Stephen Boyd wrote:
> We need to enable runtime PM on this i2c controller before populating
> child devices with i2c_add_adapter(). Otherwise, if a child device uses
> runtime PM and stays runtime PM enabled we'll get the following warning
> at boot.
>
> Enabling runtime PM for inactive device (a98000.i2c) with active children
> WARNING: CPU: 4 PID: 1 at drivers/base/power/runtime.c:1300 pm_runtime_enable+0xd8/0xf8
> Modules linked in:
> CPU: 4 PID: 1 Comm: swapper/0 Not tainted 4.19.0 #6
> elants_i2c 14-0010: 14-0010 supply vccio not found, using dummy regulator
> pstate: 60c00089 (nZCv daIf +PAN +UAO)
> pc : pm_runtime_enable+0xd8/0xf8
> lr : pm_runtime_enable+0xd8/0xf8
> sp : ffffffc0de257a30
> x29: ffffffc0de257a30 x28: 0000000000061a80
> x27: ffffff9008ea7118
> x26: ffffffc0d718b058
> x25: ffffff9008ea7000 x24: ffffffc0d718a8dc
> x23: ffffffc0d718a8b0 x22: ffffffc0d823dd58
> x21: 0000000000000000 x20: ffffffc0d823dbc8
> x19: ffffffc0d823da90 x18: 000000007f743d9a
> x17: 0000000000000080 x16: 0000000000000003
> x15: 000000000000003f x14: 0720072007200720
> x13: 0720072007200720 x12: 0720072007200720
> x11: 0720072007200720 x10: 0720072007200720
> x9 : 0720072007200720 x8 : 0720072007200720
> x7 : ffffff900816da30 x6 : 0000000000000000
> x5 : 0000000000000080 x4 : 0000000000000003
> x3 : ffffff900816f304 x2 : ffffffc0de248050
> x1 : 25045a74f48a7400 x0 : 25045a74f48a7400
> Call trace:
> pm_runtime_enable+0xd8/0xf8
> geni_i2c_probe+0x440/0x460
> platform_drv_probe+0x74/0xc8
> really_probe+0x1ac/0x35c
> driver_probe_device+0xd4/0x118
> __driver_attach+0xc8/0x118
> bus_for_each_dev+0xac/0xe8
> driver_attach+0x38/0x44
> bus_add_driver+0x15c/0x294
> driver_register+0x13c/0x198
> __platform_driver_register+0x88/0x94
> geni_i2c_driver_init+0x20/0x28
> do_one_initcall+0x250/0x4ec
> kernel_init_freeable+0x6f0/0x7c4
> kernel_init+0x18/0x120
> ret_from_fork+0x10/0x18
>
> Let's move the runtime PM enabling and setup to before we add the
> adapter, so that this device can respond to runtime PM requests from
> children.
>
> Cc: Douglas Anderson <dianders@chromium.org>
> Cc: Alok Chauhan <alokc@codeaurora.org>
> Fixes: 37692de5d523 ("i2c: i2c-qcom-geni: Add bus driver for the Qualcomm GENI I2C controller")
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-11-09 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 20:57 [PATCH v2] i2c: i2c-qcom-geni: Fix runtime PM mismatch with child devices Stephen Boyd
2018-11-02 21:00 ` Doug Anderson
2018-11-09 16:04 ` Wolfram Sang [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=20181109160432.GI1031@kunai \
--to=wsa@the-dreams.de \
--cc=alokc@codeaurora.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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).