From: <achew@nvidia.com>
To: <grant.likely@secretlab.ca>, <olof@lixom.net>,
<swarren@nvidia.com>, <dwillemsen@nvidia.com>,
<rklein@nvidia.com>, <mogantyv@nvidia.com>
Cc: <devicetree-discuss@lists.ozlabs.org>,
<linux-tegra@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Andrew Chew <achew@nvidia.com>
Subject: [PATCH 3/3 v2] dt: tegra20: Add ehci overrides to Seaboard.
Date: Wed, 20 Jul 2011 12:38:10 -0700 [thread overview]
Message-ID: <1311190690-18334-3-git-send-email-achew@nvidia.com> (raw)
In-Reply-To: <1311190690-18334-1-git-send-email-achew@nvidia.com>
From: Andrew Chew <achew@nvidia.com>
Seaboard has different values for some of the utmi properties.
Signed-off-by: Andrew Chew <achew@nvidia.com>
---
arch/arm/boot/dts/tegra-seaboard.dts | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/tegra-seaboard.dts b/arch/arm/boot/dts/tegra-seaboard.dts
index 5a99b4c..f8737ed 100644
--- a/arch/arm/boot/dts/tegra-seaboard.dts
+++ b/arch/arm/boot/dts/tegra-seaboard.dts
@@ -31,4 +31,16 @@
sdhci@c8000600 {
status = "ok";
};
+
+ ehci@c5000000 {
+ hssync_start_delay = < 0 >;
+ xcvr_setup = < 15 >;
+ xcvr_lsfslew = < 2 >;
+ xcvr_lsrslew = < 2 >;
+ };
+
+ ehci@c5008000 {
+ hssync_start_delay = < 0 >;
+ xcvr_setup = < 8 >;
+ };
};
--
1.7.6
next prev parent reply other threads:[~2011-07-20 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 19:38 [PATCH 1/3 v2] usb: tegra20-ehci: Add devicetree support achew
2011-07-20 19:38 ` [PATCH 2/3 v2] dt: tegra20: Add ehci host controller nodes achew
2011-07-20 19:52 ` Stephen Warren
2011-07-20 20:03 ` Grant Likely
2011-07-20 19:38 ` achew [this message]
2011-07-20 19:51 ` [PATCH 1/3 v2] usb: tegra20-ehci: Add devicetree support Stephen Warren
2011-07-20 20:02 ` Grant Likely
2011-07-20 20:16 ` Andrew Chew
2011-07-20 20:19 ` Grant Likely
2011-07-20 20:27 ` Andrew Chew
2011-07-20 20:28 ` Grant Likely
2011-07-20 22:23 ` Andrew Chew
2011-07-20 22:57 ` Andrew Chew
2011-07-20 22:52 ` Andrew Chew
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=1311190690-18334-3-git-send-email-achew@nvidia.com \
--to=achew@nvidia.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwillemsen@nvidia.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mogantyv@nvidia.com \
--cc=olof@lixom.net \
--cc=rklein@nvidia.com \
--cc=swarren@nvidia.com \
/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
all inboxes | Powered by JetHome®