From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC 0/2] Enable USB support for Venice2
Date: Tue, 25 Feb 2014 15:23:34 -0700 [thread overview]
Message-ID: <530D17E6.2000905@wwwdotorg.org> (raw)
In-Reply-To: <1393364160-28253-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 02/25/2014 02:35 PM, Thierry Reding wrote:
> From: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Hi,
>
> These two patches add the USB controllers to Tegra124 and enable them on
> Venice2, wiring them up with the corresponding regulators.
>
> Unfortunately the USB1 VBUS regulator seems to be causing problems once
> enabled, causing none of the USB ports to work properly. Commenting out
> the gpio property for that regulator fixes things for me and I can use
> the webcam connected to USB2 as well as any of the peripherals on USB3.
>
> Since GPIO N.04 isn't connected to anything else, I don't understand how
> it could possibly influence any of the other USB busses. I wonder if
> perhaps this is caused by defect hardware, so it would be good if
> somebody could test this on a different Venice2.
I see the same behaviour as you.
prev parent reply other threads:[~2014-02-25 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 21:35 [RFC 0/2] Enable USB support for Venice2 Thierry Reding
[not found] ` <1393364160-28253-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-25 21:35 ` [RFC 1/2] ARM: tegra: Add Tegra124 USB support Thierry Reding
2014-02-25 21:36 ` [RFC 2/2] ARM: tegra: Enable USB on Venice2 Thierry Reding
2014-02-25 22:23 ` Stephen Warren [this message]
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=530D17E6.2000905@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.