public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/1] USB: EHCI: Initialize multiple USB controllers at once
Date: Fri, 10 Aug 2012 10:07:56 -0600	[thread overview]
Message-ID: <502531DC.4050907@wwwdotorg.org> (raw)
In-Reply-To: <1344591399-10131-1-git-send-email-jilin@nvidia.com>

On 08/10/2012 03:36 AM, Jim Lin wrote:
> Add support for command line "usb reset" or "usb start" to initialize
> , "usb stop" to stop multiple USB controllers at once.
> Other command like "usb tree" also supports multiple controllers.

I assume these were reposted because you rebased on the latest
u-boot-tegra/master branch. It's usual to includes details of why you're
reposting.

I applied these two patches, without changing the Seaboard config file,
and built. I got the following warnings:

ehci-hcd.c: In function 'ehci_submit_async':
ehci-hcd.c:250:6: warning: assignment from incompatible pointer type
ehci-hcd.c: In function 'usb_lowlevel_multi_init':
ehci-hcd.c:800:20: warning: assignment discards qualifiers from pointer
target type

I tested the patches in this case and found no regressions on a regular
Seaboard.

I get slightly different warnings if I do enable the feature in the
Seaboard config file:

ehci-hcd.c: In function 'ehci_submit_async':
ehci-hcd.c:250:6: warning: assignment from incompatible pointer type
ehci-hcd.c: In function 'usb_lowlevel_multi_init':
ehci-hcd.c:800:20: warning: assignment discards qualifiers from pointer
target type
ehci-tegra.c: In function 'ehci_hcd_init':
ehci-tegra.c:56:2: warning: passing argument 2 of 'tegrausb_start_port'
from incompatible pointer type
/home/swarren/shared/git_wa/u-boot/include/asm/arch/usb.h:243:5: note:
expected 'u32 *' but argument is of type 'struct ehci_hccr **'
ehci-tegra.c:56:2: warning: passing argument 3 of 'tegrausb_start_port'
from incompatible pointer type
/home/swarren/shared/git_wa/u-boot/include/asm/arch/usb.h:243:5: note:
expected 'u32 *' but argument is of type 'struct ehci_hcor **'

I tested the patches on a regular Seaboard, and found that both USB
ports now work (great!).

However, this patch breaks the "enterrcm" command if "usb start" has
been run, I assume since the VBUS GPIO is asserted to USB port 1. Can we
add some hook into that command to shut down the USB1 VBUS GPIO? I can
live with this patch being applied before that's fixed though.

I also tested Springbank, and found that this also enables the USB port
there, but strangely "enterrcm" following "usb start" does still seem to
work on that board!

So overall, once the warnings are fixed, I'm OK with these patches,
assuming some followup work on "enterrcm" will happen.

  reply	other threads:[~2012-08-10 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10  9:36 [U-Boot] [PATCH v2 1/1] USB: EHCI: Initialize multiple USB controllers at once Jim Lin
2012-08-10 16:07 ` Stephen Warren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-08  9:48 Jim Lin
2012-08-11 23:46 ` Marek Vasut
2012-08-13 10:25   ` Jim Lin
2012-08-14 17:29     ` Marek Vasut
2012-08-14  4:22   ` Jim Lin
2012-08-14 16:18     ` Stephen Warren
2012-08-14 17:30       ` Marek Vasut

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=502531DC.4050907@wwwdotorg.org \
    --to=swarren@wwwdotorg.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