From: Oliver Graute <oliver.graute@gmail.com>
To: Dong Aisheng <aisheng.dong@nxp.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>,
Leonard Crestez <leonard.crestez@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
linux-clk@vger.kernel.org, oliver.graute@kococonnector.com
Subject: imx8qxp-lpcg-clk: probe of 5a4a0000.clock-controller failed with error -110
Date: Tue, 21 Apr 2020 16:23:50 +0200 [thread overview]
Message-ID: <20200421142350.GA77260@archlinux.localdomain> (raw)
Hello,
I run into below clock probing issue, after upgrading from next-20200214 to
next-20200420. I use the following patches series ontop:
https://patchwork.kernel.org/patch/11143351/
Some ideas what's the reason for this behavior? or how to fix this?
Best Regards,
Oliver
Linux dmsse20 5.7.0-rc2-next-20200420-00062-gdeb4ab568a65 #29 SMP PREEMPT Tue Apr 21 13:30:56 UTC 2020 aarch64 GNU/Linux
------------[ cut here ]------------
[ 31.817971] imx8qxp-lpcg-clk 5a4a0000.clock-controller: deferred probe timeout, ignoring dependency
[ 31.818035] WARNING: CPU: 0 PID: 122 at drivers/base/dd.c:270 driver_deferred_probe_check_state+0x44/0x68
[ 31.836647] Modules linked in:
[ 31.839709] CPU: 0 PID: 122 Comm: kworker/0:1 Not tainted 5.7.0-rc2-next-20200420-00062-gdeb4ab568a65 #29
[ 31.849276] Hardware name: Advantech iMX8QM DMSSE20 (DT)
[ 31.854593] Workqueue: events deferred_probe_work_func
[ 31.859738] pstate: 60000005 (nZCv daif -PAN -UAO)
[ 31.864532] pc : driver_deferred_probe_check_state+0x44/0x68
[ 31.870198] lr : driver_deferred_probe_check_state+0x44/0x68
[ 31.875859] sp : ffff8000120ebac0
[ 31.879168] x29: ffff8000120ebac0 x28: ffff800011957000
[ 31.884485] x27: 0000000000000000 x26: ffff80001006bce8
[ 31.889792] x25: 0000000000000001 x24: ffff800011ae8d58
[ 31.895109] x23: ffff000975ff7010 x22: fffffffffffffffe
[ 31.900426] x21: ffff000975ec4600 x20: ffff000975ff7010
[ 31.905742] x19: ffff000975ff7010 x18: 0000000000000010
[ 31.911050] x17: 0000000000000000 x16: 0000000000000000
[ 31.916367] x15: ffff000975ec4a70 x14: 6f656d6974206562
[ 31.921684] x13: 6f72702064657272 x12: 65666564203a7265
[ 31.927001] x11: 6c6c6f72746e6f63 x10: 2d6b636f6c632e30
[ 31.932318] x9 : 3030306134613520 x8 : 0000000000000000
[ 31.937634] x7 : 6f6e6769202c7475 x6 : ffff800011b5584f
[ 31.942951] x5 : 0000000000000000 x4 : 0000000000000000
[ 31.948268] x3 : 00000000ffffffff x2 : ffff80096d9d0000
[ 31.953584] x1 : cda1879e3af41400 x0 : 0000000000000000
[ 31.958904] Call trace:
[ 31.961351] driver_deferred_probe_check_state+0x44/0x68
[ 31.966667] __genpd_dev_pm_attach+0x1a4/0x1b0
[ 31.971109] genpd_dev_pm_attach+0x60/0x70
[ 31.975214] dev_pm_domain_attach+0x50/0x58
[ 31.979401] platform_drv_probe+0x3c/0xa8
[ 31.983411] really_probe+0xd8/0x320
[ 31.986990] driver_probe_device+0x58/0xf0
[ 31.991093] __device_attach_driver+0x84/0xc8
[ 31.995454] bus_for_each_drv+0x78/0xc8
[ 31.999292] __device_attach+0xe4/0x140
[ 32.003131] device_initial_probe+0x14/0x20
[ 32.007310] bus_probe_device+0x9c/0xa8
[ 32.011141] deferred_probe_work_func+0x74/0xb0
[ 32.015683] process_one_work+0x1a0/0x328
[ 32.019692] worker_thread+0x1f8/0x428
[ 32.023447] kthread+0x138/0x158
[ 32.026680] ret_from_fork+0x10/0x1c
[ 32.030256] ---[ end trace 33d4174015850150 ]---
[ 32.034947] imx8qxp-lpcg-clk: probe of 5a4a0000.clock-controller failed with error -110
[ 32.046365] platform lvds_backlight@1: deferred probe pending
[ 32.052154] platform 5b130000.cdns3: deferred probe pending
next reply other threads:[~2020-04-21 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 14:23 Oliver Graute [this message]
2020-04-23 14:16 ` imx8qxp-lpcg-clk: probe of 5a4a0000.clock-controller failed with error -110 Aisheng Dong
2020-04-23 19:47 ` Oliver Graute
2020-04-23 19:59 ` John Stultz
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=20200421142350.GA77260@archlinux.localdomain \
--to=oliver.graute@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=oliver.graute@kococonnector.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.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