From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: Pavel Machek <pavel@denx.de>, Bin Liu <b-liu@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
Jacopo Mondi <jacopo@jmondi.org>, Marcel Partap <mpartap@gmx.net>,
Merlijn Wajer <merlijn@wizzup.org>,
Michael Scott <hashcode0f@gmail.com>, NeKit <nekit1000@gmail.com>,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH 0/4] musb host improvments mostly for omap2430 glue
Date: Tue, 3 Sep 2019 10:07:25 +0200 [thread overview]
Message-ID: <20190903080725.GA26076@amd> (raw)
In-Reply-To: <20190902160651.GI52127@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 2608 bytes --]
Hi!
On Mon 2019-09-02 09:06:51, Tony Lindgren wrote:
> * Pavel Machek <pavel@denx.de> [190902 09:44]:
> > On Mon 2019-09-02 11:23:44, Pavel Machek wrote:
> > Hmm. I guess CONFIG_USB_MUSB_DUAL_ROLE=y might be useful.
> >
> > And now... if I unplug/replug the usb after the boot, USB hub and
> > mouse are recognized. Good!
> >
> > Less than minute later:
> >
> > mmusb-hdrc.0.auto: Babble
> > USB disconnect
>
> The babble is most likely caused by some kind of signaling issue.
>
> > I unplug, replug usb (not at the phone, between hub and dongle, and
> > green LED indincating charging starts blinking rapidly.
> >
> > cpcap-core spi0.0: EOT timed out.
> >
> > I try plug/replug, and now green led is on.
> >
> > I unplug replug at the phone, and get bunch more of messages:
> >
> > musm _set_peripheral: already in peripheral mode: 99
> > musm _set_peripheral: already in peripheral mode: 81
> > musm _set_peripheral: already in peripheral mode: 81
> >
> > musb_set_host: could not set host: 99
> > musb_set_host: could not set host: 99
> > musb_set_host: could not set host: 99
> > musb_set_host: could not set host: 99
> > musb_set_host: could not set host: 99
> > musb_set_host: could not set host: 99
> > musb_set_host: could not set host: 99
> > musb_set_host: could not set host: 99
> >
> > Unplug/replug at host, and again, hub+mouse is detected.
> >
> > I unplug power connected to one of USB hub's ports... and find out
> > that phone was _not_ powering it.
> >
> > Ok... so something somehow works.... sometimes :-).
>
> My guess is you're missing a USB micro-B cable with ID pin
> grounded, with that things should just work automagically.
>
> So no need for hubs feeding back VBUS and no need to
> try to force host mode via sysfs unlike on n900.
I don't think so... I got it to run in the end (and I have to
apologize, it seems to work at least as long as it is plugged it an
boot and not touched).
So... I actually have two cables.
#1 definitely does not have ID pin grounded. That does not work, not
even in original android.
#2 definitely has _something_, because it does work in original
android. But not even original android provides VBUS (5V on USB) in
that configuration. It also looks like hardware _can_ provide at
least VBAT on VBUS, because I seen that during some of the crashes.
Thanks for the patches, BTW.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-09-03 8:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 23:20 [PATCH 0/4] musb host improvments mostly for omap2430 glue Tony Lindgren
2019-08-30 23:20 ` [PATCH 1/4] usb: musb: omap2430: Wait on enable to avoid babble Tony Lindgren
2019-08-30 23:20 ` [PATCH 2/4] usb: musb: omap2430: Handle multiple ID ground interrupts Tony Lindgren
2019-08-30 23:20 ` [PATCH 3/4] usb: musb: Add musb_set_host and peripheral and use them for omap2430 Tony Lindgren
2019-08-30 23:20 ` [PATCH 4/4] usb: musb: omap2430: Clean up enable and remove devctl tinkering Tony Lindgren
2019-09-01 19:39 ` next-20190830 on Droid 4 was Re: [PATCH 0/4] musb host improvments mostly for omap2430 glue Pavel Machek
2019-09-01 19:49 ` Pavel Machek
2019-09-02 9:23 ` Pavel Machek
2019-09-02 9:44 ` Pavel Machek
2019-09-02 16:06 ` Tony Lindgren
2019-09-03 8:07 ` Pavel Machek [this message]
2019-09-16 1:20 ` Tony Lindgren
2019-09-16 1:26 ` Tony Lindgren
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=20190903080725.GA26076@amd \
--to=pavel@ucw.cz \
--cc=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=hashcode0f@gmail.com \
--cc=jacopo@jmondi.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@denx.de \
--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).