From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, 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: Re: droid4 -- weird behaviour when attempting to use usb host
Date: Tue, 26 Sep 2023 10:14:15 +0300 [thread overview]
Message-ID: <20230926071415.GW5285@atomide.com> (raw)
In-Reply-To: <ZRGa+0OFNluV4T5t@localhost>
* Pavel Machek <pavel@ucw.cz> [230925 14:36]:
> Hi!
>
> I'm having some fun with usb host. Good news is it works with
> externally powered hub... after a while. I get some error messages
> about inability to go host mode, but with enough patience it
> eventually does enter host mode and I see my keyboard/mouse.
>
> And usually in that process, one of my cpu cores disappear. top no
> longer shows 2 cores, and I was wondering for a while if d4 is
> single-core system. It is not, my two cores are back after reboot.
>
> That's with 6.1.9 kernel from leste. Ideas how to debug this would be
> welcome. (Do you use usb host?)
You are using a "proper" non-standard usb micro-b cable that grounds
the id pin, right?
If not, try with one of those as it allows the hardware to do what it's
supposed to do.
And presumably you don't have a hacked usb hub that feeds back the
vbus to your phone, right?
If you have, that should not be used as the pmic can feed vbus.
Regards,
Tony
next prev parent reply other threads:[~2023-09-26 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 14:36 droid4 -- weird behaviour when attempting to use usb host Pavel Machek
2023-09-26 7:14 ` Tony Lindgren [this message]
2023-09-27 15:52 ` Pavel Machek
2023-09-27 16:50 ` Unknown
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=20230926071415.GW5285@atomide.com \
--to=tony@atomide.com \
--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=pavel@ucw.cz \
--cc=phone-devel@vger.kernel.org \
--cc=sre@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