From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org,
martin_rysavy@centrum.cz, phone-devel@vger.kernel.org,
maemo-leste@lists.dyne.org
Subject: Droid 4 in next-20201120: cpcap-usb-phy.0: could not initialize VBUS or ID IIO:
Date: Sun, 22 Nov 2020 13:19:40 +0100 [thread overview]
Message-ID: <20201122121940.GA26145@duo.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]
Hi!
I'm getting this warning during boot:
[ 3.413299] gpio gpiochip1: Persistence not supported for GPIO 0
[ 3.419494] cpcap-usb-phy cpcap-usb-phy.0: could not initialize VBUS or ID IIO: -517
[ 3.427398] ------------[ cut here ]------------
[ 3.432067] WARNING: CPU: 0 PID: 1 at drivers/regulator/core.c:2123 _regulator_put.part.2+0x168/0x17c
[ 3.441406] Modules linked in:
[ 3.444519] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-rc4-next-20201120-dirty #198
[ 3.452728] Hardware name: Generic OMAP4 (Flattened Device Tree)
[ 3.458801] [<c010db44>] (unwind_backtrace) from [<c0109ec0>] (show_stack+0x10/0x14)
[ 3.466613] [<c0109ec0>] (show_stack) from [<c095561c>] (dump_stack+0xb8/0xd4)
[ 3.473876] [<c095561c>] (dump_stack) from [<c0953208>] (__warn+0xa8/0xd0)
[ 3.480804] [<c0953208>] (__warn) from [<c095327c>] (warn_slowpath_fmt+0x4c/0x98)
[ 3.488311] [<c095327c>] (warn_slowpath_fmt) from [<c0479b90>] (_regulator_put.part.2+0x168/0x17c)
[ 3.497344] [<c0479b90>] (_regulator_put.part.2) from [<c0479bcc>] (regulator_put+0x28/0x38)
[ 3.505828] [<c0479bcc>] (regulator_put) from [<c053a86c>] (release_nodes+0x1a0/0x248)
[ 3.513793] [<c053a86c>] (release_nodes) from [<c05366b8>] (really_probe+0x104/0x3b4)
[ 3.521667] [<c05366b8>] (really_probe) from [<c0536acc>] (driver_probe_device+0x58/0xb4)
[ 3.529907] [<c0536acc>] (driver_probe_device) from [<c0534b34>] (bus_for_each_drv+0x70/0x94)
[ 3.538482] [<c0534b34>] (bus_for_each_drv) from [<c0536540>] (__device_attach+0xbc/0x128)
(and then cpcap does not work). Is my configuration missing something?
Later I get warnings about framedone interrupt not being done (IIRC)
from HDMI audio module, and I have screen freezing in framebuffer.
Any ideas?
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
reply other threads:[~2020-11-22 12:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201122121940.GA26145@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=maemo-leste@lists.dyne.org \
--cc=martin_rysavy@centrum.cz \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.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 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).