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 10:19:42 -0600 [thread overview]
Message-ID: <51C32B9E.60608@wwwdotorg.org> (raw)
In-Reply-To: <1371716020-21809-2-git-send-email-jilin@nvidia.com>
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.
> diff --git a/board/nvidia/cardhu/pinmux-config-cardhu.h b/board/nvidia/cardhu/pinmux-config-cardhu.h
> @@ -332,7 +332,9 @@ static struct pingroup_config unused_pins_lowpower[] = {
> DEFAULT_PINMUX(GMI_AD7, NAND, NORMAL, TRISTATE, OUTPUT),
> DEFAULT_PINMUX(GMI_AD9, PWM1, NORMAL, NORMAL, OUTPUT),
> DEFAULT_PINMUX(GMI_AD11, NAND, NORMAL, NORMAL, OUTPUT),
> - DEFAULT_PINMUX(GMI_AD13, NAND, UP, NORMAL, INPUT),
> +
> + /* Beaver, USB13_VBUS_PULLUP GPIO */
> + DEFAULT_PINMUX(GMI_AD13, NAND, NORMAL, NORMAL, OUTPUT),
I assume this table is shared between Cardhu and Beaver. You can't make
Beaver-specific changes to it. If you need to make Beaver-specific
changes, then you need to create a separate pinmux-config-beaver.h, or
use #ifdefs based on the board you're compiling for.
Luckily in this case, GMI_AD13 is not connected on Cardhu, so you
haven't damaged any HW by testing this change on Cardhu.
> diff --git a/drivers/usb/host/ehci-tegra.c b/drivers/usb/host/ehci-tegra.c
> +struct fdt_usb_controller {
> + int compat;
> + /* flag to determine whether controller supports hostpc register */
> + u8 has_hostpc:1;
I'd suggest "bool" here, or at least "u32 has_hostpc:1"; alignment
concerns will pad the storage out to 32-bit anyway, so you may as well
use a 32-bit variable as is normal for bit-fields.
next prev parent reply other threads:[~2013-06-20 16:19 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 [this message]
2013-06-20 17:20 ` Jim Lin
2013-06-20 17:40 ` Stephen Warren
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=51C32B9E.60608@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