linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Enric Balletbo Serra <eballetbo@gmail.com>
To: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	linux-omap@vger.kernel.org, balbi@ti.com
Subject: USB OTG doesn't work in HOST mode on OMAP3 processor on 3.18-rc5
Date: Mon, 17 Nov 2014 16:13:59 +0100	[thread overview]
Message-ID: <CAFqH_53hyYO9DHfhzDhYkTnimKR0FOQuUw4OGCM4myKoOJSQRA@mail.gmail.com> (raw)

 Hi all,

I'm trying to use the USB OTG driver of OMAP3 processor in HOST mode
when it's configured in dual role mode (CONFIG_USB_MUSB_DUAL_ROLE=y)

The test case that I'm trying to solve is as follows.

1) Boot the board.
2) Put the USB ID pin to ground
3) Connect a pendrive.

In such case doesn't work as expected and pendrive is never detected.

Enabling debug information, I see that the phyter (twl4030) is
constantly polling the STS_HW_CONDITIONS register, who reports:

  twl4030_usb 48070000.i2c:twl@48:twl4030-usb: HW_CONDITIONS 0x54/84; link 1

The STS_HW_CONDITIONS register reports:

Bit 2: STS_USB : 1: USB is plugged in.
Bit 4: STS_WAKEUP1: Level status of WAKEUP1 pad (active high) = nSLEEP1
Bit 6: STS_WAKEUP3: Level status of WAKEUP3 pad (active high) = CLKREQ

I guess that in this case the state machine is waiting for VBUS, and
looks for bit 7 STS_VBUS (Level status of VBUS port), but this never
occurs. Using an oscilloscope I checked VBUS level and I can confirm
that it's a 0 level.

My understand is that in this case the driver should enable VBUS but I
didn't find where is the best place to do this and why is not doing
this already. Any clue on this?

Thanks in advance,
   Enric

             reply	other threads:[~2014-11-17 15:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 15:13 Enric Balletbo Serra [this message]
2014-11-17 18:04 ` USB OTG doesn't work in HOST mode on OMAP3 processor on 3.18-rc5 Tony Lindgren
2014-11-18  9:02   ` Enric Balletbo Serra
     [not found]     ` <CAFqH_52LV8k6OyH04dUmhzZChnHrtJR23qu1ewhU49iOVT1Mwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-18 10:42       ` Enric Balletbo Serra
2014-11-18 15:42     ` Tony Lindgren
     [not found]       ` <20141118154204.GI7046-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-11-19 11:12         ` Enric Balletbo Serra
2014-11-19 17:53           ` Tony Lindgren
     [not found]             ` <20141119175348.GK7046-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-11-28 10:35               ` Yegor Yefremov
2014-11-29 15:35                 ` Felipe Balbi
2014-12-01  7:57                   ` Yegor Yefremov
     [not found]                     ` <CAGm1_ku4UYL0DX9DuSJWn9-QKhcq+mUKyVTA433F6XbRe2FnHg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-01 14:35                       ` Felipe Balbi
     [not found] <CAJt7siu_JiSe3CfM2=0UZLQjRevdLuX+=UL566fiW6XefTTWGA@mail.gmail.com>
     [not found] ` <CAJt7siu_JiSe3CfM2=0UZLQjRevdLuX+=UL566fiW6XefTTWGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-19 11:16   ` Eduard Gavin
2014-12-23 18:41     ` Felipe Balbi

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=CAFqH_53hyYO9DHfhzDhYkTnimKR0FOQuUw4OGCM4myKoOJSQRA@mail.gmail.com \
    --to=eballetbo@gmail.com \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.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;
as well as URLs for NNTP newsgroup(s).