From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: "Felipe Balbi" <felipe.balbi@linux.intel.com>,
"Tony Lindgren" <tony@atomide.com>,
"Pali Rohár" <pali.rohar@gmail.com>
Cc: joerg Reisenweber <joerg@openmoko.org>,
Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>, Pavel Machek <pavel@ucw.cz>,
Nishanth Menon <nm@ti.com>
Subject: Re: Nokia N900: musb is in wrong state after boot
Date: Wed, 8 Jun 2016 15:04:02 +0300 [thread overview]
Message-ID: <71cb45ec-a269-d510-df34-eb6eaa781da8@cogentembedded.com> (raw)
In-Reply-To: <87h9d49exz.fsf@linux.intel.com>
On 6/8/2016 1:02 PM, Felipe Balbi wrote:
>> * Pali Rohár <pali.rohar@gmail.com> [160607 05:53]:
>>>> Tony, what do you think about that patch?
>>>>
>>>
>>> Tony, PING
>>
>> Yeah I don't know, AFAIK we don't have a generic way to
>> force MUSB to change mode without ID pin. If you have figured
>> something generic for that which does not actually tinker with
>> the PHY registers directly, that should be the generic
>> musb_set_mode() that we've been wondering about for years.
>
> #define MUSB_TEST_FORCE_HOST 0x80
>
> Can someone confirm on MUSB's docs (and actual running system) that this
> does what's supposed to do?
The MUSB programmer's guide says the CID (sic) input is ignored when the
Force_Host bit is set. The host mode is entered when the Session bit is set.
But I don't have a MUSB hardware readily available to confirm.
MBR, Sergei
next prev parent reply other threads:[~2016-06-08 12:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 15:16 Pali Rohár
2016-01-19 20:33 ` Tony Lindgren
2016-01-21 8:40 ` Pali Rohár
2016-01-21 9:57 ` Ivaylo Dimitrov
2016-01-21 10:23 ` Pali Rohár
2016-01-21 10:27 ` Ivaylo Dimitrov
2016-01-21 10:29 ` joerg Reisenweber
2016-01-21 17:41 ` Tony Lindgren
2016-01-21 18:44 ` joerg Reisenweber
2016-01-21 19:21 ` Tony Lindgren
2016-01-21 19:34 ` joerg Reisenweber
2016-01-21 20:30 ` Tony Lindgren
2016-01-26 14:34 ` Pali Rohár
2016-01-26 17:26 ` Tony Lindgren
2016-02-21 11:12 ` Pali Rohár
2016-02-22 7:31 ` Felipe Balbi
2016-02-22 8:34 ` Pali Rohár
2016-02-22 8:54 ` Felipe Balbi
2016-02-22 8:54 ` Felipe Balbi
2016-02-22 15:36 ` Bin Liu
2016-02-22 15:49 ` Adam Ford
2016-01-23 12:57 ` Pali Rohár
2016-05-29 10:38 ` Pali Rohár
2016-06-07 12:50 ` Pali Rohár
2016-06-08 9:53 ` Tony Lindgren
2016-06-08 10:02 ` Felipe Balbi
2016-06-08 10:19 ` Pali Rohár
2016-06-08 10:20 ` joerg Reisenweber
2016-06-08 12:04 ` Sergei Shtylyov [this message]
2016-06-08 12:18 ` joerg Reisenweber
2016-06-08 12:32 ` Sergei Shtylyov
2016-06-09 21:09 ` Bin Liu
2016-06-09 20:58 ` Bin Liu
2016-06-09 21:25 ` joerg Reisenweber
2016-06-10 15:08 ` Bin Liu
2016-06-10 15:23 ` joerg Reisenweber
2016-06-10 15:59 ` Bin Liu
2016-06-10 16:15 ` joerg Reisenweber
2016-06-10 17:04 ` Nishanth Menon
2016-06-10 17:21 ` joerg Reisenweber
2016-06-10 17:37 ` Bin Liu
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=71cb45ec-a269-d510-df34-eb6eaa781da8@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=joerg@openmoko.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--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
Powered by JetHome