From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/3] ARM: Tegra: USB: EHCI: Add support for Tegra30/Tegra114
Date: Thu, 20 Jun 2013 11:40:50 -0600 [thread overview]
Message-ID: <51C33EA2.2090908@wwwdotorg.org> (raw)
In-Reply-To: <4B9C9637D5087840A465BDCB251780E9E30ADFCE63@HKMAIL02.nvidia.com>
On 06/20/2013 11:20 AM, Jim Lin wrote:
>
>> On 06/20/2013 02:13 AM, Jim Lin wrote:
>>> Tegra30 and Tegra114 are compatible except PLL parameters.
>>>
>>> Tested on Tegra30 Cardhu, and Tegra114 Dalmore
>>> platforms. All works well.
>>> Changes in v4:
>>
>>> - In pinmux-config-cardhu.h, chnage GMI_AD13 pinmux state to be OUTPUT
>>> in order to be driven HIGH for Beaver board.
>>
>> That should be reverted. As I mentioned in my previous response,
>> GMI_AD13 is the wrong pin.
>
> Please help me, test this v4 patch set on Beaver board, and
> tell me result.
It will possibly work since the pin you selected for VBUS does pull up
(weakly) the VBUS line. However, I'm not going to actually bother
testing it, since the code is doing the wrong thing.
next prev parent reply other threads:[~2013-06-20 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 8:13 [U-Boot] [PATCH v4 1/3] ARM: Tegra: FDT: Add USB EHCI function for T30/T114 Jim Lin
2013-06-20 8:13 ` [U-Boot] [PATCH v4 2/3] ARM: Tegra: USB: EHCI: Add support for Tegra30/Tegra114 Jim Lin
2013-06-20 16:19 ` Stephen Warren
2013-06-20 17:20 ` Jim Lin
2013-06-20 17:40 ` Stephen Warren [this message]
2013-06-20 8:13 ` [U-Boot] [PATCH v4 3/3] Tegra: Config: Enable Tegra30/Tegra114 USB function Jim Lin
2013-06-20 11:17 ` [U-Boot] [PATCH v4 1/3] ARM: Tegra: FDT: Add USB EHCI function for T30/T114 Thierry Reding
2013-06-20 15:56 ` Stephen Warren
2013-06-20 16:00 ` Stephen Warren
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=51C33EA2.2090908@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