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: Thu, 07 Feb 2013 11:07:14 -0700 [thread overview]
Message-ID: <5113ED52.4040306@wwwdotorg.org> (raw)
In-Reply-To: <CA+m5__JrvRRtOeneY-Li5P=Gcz7VVbBJY12rsXBivat+JzjjNA@mail.gmail.com>
On 02/07/2013 09:17 AM, Tom Warren wrote:
> Laxman,
>
> On Thu, Feb 7, 2013 at 7:57 AM, Laxman Dewangan <ldewangan@nvidia.com> wrote:
>> On Thursday 07 February 2013 04:56 AM, 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>
>>> ---
>>
>>
>>
>>> diff --git a/board/nvidia/dts/tegra114-dalmore.dts
>>> b/board/nvidia/dts/tegra114-dalmore.dts
>>> index 7315577..13b07f3 100644
>>> --- a/board/nvidia/dts/tegra114-dalmore.dts
>>> +++ b/board/nvidia/dts/tegra114-dalmore.dts
>>> @@ -6,8 +6,41 @@
>>> model =NVIDIA Dalmore";
>>> compatible =nvidia,dalmore", "nvidia,tegra114";
>>>
>>> + aliases {
>>> + i2c0 =/i2c at 7000d000";
>>> + i2c1 =/i2c at 7000c000";
>>> + i2c2 =/i2c at 7000c400";
>>> + i2c3 =/i2c at 7000c500";
>>> + i2c4 =/i2c at 7000c700";
>>> + };
>>
>>
>> Can we move this to tegar114.dtsi file.
>
> I could, but why? Most, if not all, of the U-Boot boards that use DT
> are putting their aliases in the .dts file in the board directory.
Laxman, the issue here is that right now in U-Boot, I believe, if a
particular board only uses I2C adapters 0, 2, and 4, then only U-Boot
device IDs 0, 1, and 2 are defined, rather than IDs 0, 2, and 4. That's
why the aliases are in the per-board file for now, because the actual
set of I2C adapters enabled is board-specific.
Tom, as background for Laxman's request, for other devices (e.g. serial
ports), customer engineers have pushed back on that naming scheme, and
always want a specific HW device to end up with a static name,
irrespective of which other devices of the same type are used, if any.
For that reason, in the kernel, we have aliases for the serial ports in
tegra*.dtsi rather than in per-board files, and the names are static.
So I wonder if in U-Boot we really have to have IDs 0..n rather than
e.g. IDs 0, 2, 4 for the I2C ports (when some aren't used). Then, we
could just put the aliases in tegra*.dtsi, which makes life simpler when
creating board .dts files...
next prev parent reply other threads:[~2013-02-07 18:07 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
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 [this message]
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=5113ED52.4040306@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