From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/3] Tegra114: fdt: Update DT files with I2C info for T114/Dalmore
Date: Wed, 06 Feb 2013 17:00:19 -0700 [thread overview]
Message-ID: <5112EE93.3070407@wwwdotorg.org> (raw)
In-Reply-To: <1360193208-16055-3-git-send-email-twarren@nvidia.com>
On 02/06/2013 04:26 PM, Tom Warren wrote:
> Note that T114 does not have a separate/different DVC (power I2C)
> controller like T20 - all 5 I2C controllers are identical, but
> I2C5 is used to designate the controller intended for power
> control (PWR_I2C in the schematics).
> diff --git a/arch/arm/dts/tegra114.dtsi b/arch/arm/dts/tegra114.dtsi
> + tegra_car: clock at 60006000 {
> + compatible = "nvidia,tegra114-car, nvidia,tegra30-car";
Only the Tegra114 value should be listed here; the presence of the
Tegra30 value in the upstream kernel is a mistake that will be fixed as
part of the Tegra114 clock driver patches.
> + i2c at 7000c000 {
> + compatible = "nvidia,tegra114-i2c", "nvidia,tegra20-i2c";
Same here; only include the Tegra114 value since the HW isn't 100%
compatible with the Tegra20 HW.
> diff --git a/board/nvidia/dts/tegra114-dalmore.dts b/board/nvidia/dts/tegra114-dalmore.dts
> + i2c at 7000d000 {
> + status = "okay";
> + clock-frequency = <100000>;
> + };
According to our downstream Linux kernel, that I2C controller can run up
to 400KHz on this board.
next prev parent reply other threads:[~2013-02-07 0:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 23:26 [U-Boot] [PATCH v2 0/3] Add I2C driver for T114 Dalmore Tom Warren
2013-02-06 23:26 ` [U-Boot] [PATCH v2 1/3] Tegra: I2C: Add T114 clock support to tegra_i2c driver Tom Warren
2013-02-06 23:50 ` Stephen Warren
2013-02-07 14:52 ` Laxman Dewangan
2013-02-08 9:15 ` Laxman Dewangan
2013-02-08 16:39 ` Tom Warren
2013-02-06 23:26 ` [U-Boot] [PATCH v2 2/3] Tegra114: fdt: Update DT files with I2C info for T114/Dalmore Tom Warren
2013-02-07 0:00 ` Stephen Warren [this message]
2013-02-07 16:14 ` Tom Warren
2013-02-07 18:17 ` Stephen Warren
2013-02-12 18:13 ` Simon Glass
2013-02-12 19:13 ` Tom Warren
2013-02-12 19:17 ` Simon Glass
2013-02-12 19:26 ` Stephen Warren
2013-02-12 19:32 ` Simon Glass
2013-02-12 19:33 ` Tom Warren
2013-02-07 14:57 ` Laxman Dewangan
2013-02-07 16:17 ` Tom Warren
2013-02-07 18:07 ` Stephen Warren
2013-02-07 18:14 ` Tom Warren
2013-02-07 18:20 ` Stephen Warren
2013-02-07 19:05 ` Tom Warren
2013-02-07 19:08 ` Stephen Warren
2013-02-07 19:59 ` Tom Warren
2013-02-06 23:26 ` [U-Boot] [PATCH v2 3/3] Tegra114: I2C: Enable I2C driver on Dalmore E1611 eval board Tom Warren
2013-02-07 0:01 ` Stephen Warren
2013-02-07 14:58 ` Laxman Dewangan
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=5112EE93.3070407@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 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.