From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Tegra114: fdt: Update DT files with I2C info for T114/Dalmore
Date: Tue, 29 Jan 2013 13:09:20 -0700 [thread overview]
Message-ID: <51082C70.3040108@wwwdotorg.org> (raw)
In-Reply-To: <1359487175-21064-2-git-send-email-twarren@nvidia.com>
On 01/29/2013 12:19 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).
>
> Signed-off-by: Tom Warren <twarren@nvidia.com>
> ---
> arch/arm/dts/tegra114.dtsi | 93 +++++++++++++++++++++++++++++++++
> board/nvidia/dts/tegra114-dalmore.dts | 33 ++++++++++++
> 2 files changed, 126 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/dts/tegra114.dtsi b/arch/arm/dts/tegra114.dtsi
> index d06cd12..76fc83b 100644
> --- a/arch/arm/dts/tegra114.dtsi
> +++ b/arch/arm/dts/tegra114.dtsi
> @@ -2,4 +2,97 @@
>
> / {
> compatible = "nvidia,tegra114";
> +
> + tegra_car: clock at 60006000 {
> + compatible = "nvidia,tegra114-car", "nvidia,tegra20-car";
I don't believe the Tegra114 CAR is backwards-compatible enough with
Tegra20 to include the Tegra20 entry in compatible. In other words, just:
compatible = "nvidia,tegra114-car";
> + reg = <0x60006000 0x1000>;
> + #clock-cells = <1>;
> + };
> + apbdma: dma {
> + compatible = "nvidia,tegra114-apbdma", "nvidia,tegra20-apbdma";
Same here; it isn't fully backwards-compatible according to Laxman's
kernel patches.
I don't think you need the APB DMA node for I2C though; perhaps just
drop it.
If you do keep this node, it needs the clocks property filled in.
> + i2c at 7000c000 {
> + compatible = "nvidia,tegra114-i2c", "nvidia,tegra20-i2c";
The I2C nodes also aren't backwards-compatible.
> + reg = <0x7000c000 0x100>;
The interrupts property is missing here.
> diff --git a/board/nvidia/dts/tegra114-dalmore.dts b/board/nvidia/dts/tegra114-dalmore.dts
Board changes would usually be a separate patch to an SoC change, but I
guess not a big deal.
All 5 I2C ports are used on the board and only support 100KHz? That
seems unusual, but I suppose it's possible.
next prev parent reply other threads:[~2013-01-29 20:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 19:19 [U-Boot] [PATCH 0/2] Add I2C driver for Tegra114 Dalmore Tom Warren
2013-01-29 19:19 ` [U-Boot] [PATCH 1/2] Tegra114: fdt: Update DT files with I2C info for T114/Dalmore Tom Warren
2013-01-29 20:09 ` Stephen Warren [this message]
2013-01-29 20:40 ` Tom Warren
2013-01-29 21:08 ` Stephen Warren
2013-01-29 21:57 ` Tom Warren
2013-01-29 22:13 ` Stephen Warren
2013-01-30 7:01 ` Laxman Dewangan
2013-01-30 15:20 ` Tom Warren
2013-01-30 0:16 ` Stephen Warren
2013-01-29 19:19 ` [U-Boot] [PATCH 2/2] Tegra114: I2C: Enable I2C driver on Dalmore E1611 eval board Tom Warren
2013-01-29 20:11 ` Stephen Warren
2013-01-29 20:42 ` Tom 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=51082C70.3040108@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