mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Bogdan Harjoc <harjoc@gmail.com>
To: barebox@lists.infradead.org, u-boot@lists.denx.de
Subject: dwc2 USB host initialization issue
Date: Wed, 29 Aug 2018 17:06:34 +0300	[thread overview]
Message-ID: <CAF4+tmpOXPrW55zBodV7Hv7ixFRzT_0w2Kk7YU2WWQ-g0cJdJQ@mail.gmail.com> (raw)

I am trying to initialize a dwc2 usb otg host using the u-boot dwc2
driver in u-boot and barebox and am trying to get past the port
power-up step. The controller is activated successfully once the Linux
kernel boots up and the mass storage devices are accessible, but in
u-boot and barebox it seems to not receive the

USB_PORT_STAT_C_CONNECTION
nor the
USB_PORT_STAT_C_ENABLE

port change status. In the bootloader, usb_get_port_status returns
0x510 (i.e. HIGH_SPEED | POWER | RESET), while under linux the status
after powering up the port is 0x101 (i.e. POWER | CONNECTION) and the
linux usb core then properly brings up the port.

I looked at the submitted usb requests, and didn't see any relevant
difference (bootloader vs linux). All I could see from the debug
output is that PwrOn2PwrGood time and HubContrCurrent are both zero in
barebox and nonzero in linux.

Could the cause be the fact that in the bootloader the port comes up
with HIGH_SPEED status ? Can I disable this flag during hub
initialization ? Or is there another probable cause for this ?

Regards,
Bogdan

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

                 reply	other threads:[~2018-08-29 14:06 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=CAF4+tmpOXPrW55zBodV7Hv7ixFRzT_0w2Kk7YU2WWQ-g0cJdJQ@mail.gmail.com \
    --to=harjoc@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=u-boot@lists.denx.de \
    /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