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 17:16:50 -0700 [thread overview]
Message-ID: <51086672.3050609@wwwdotorg.org> (raw)
In-Reply-To: <CA+m5__LDE5V8CoZBY_hLrYCoQV2nA-1fahWD7QaiPU4NrQdLRg@mail.gmail.com>
On 01/29/2013 02:57 PM, Tom Warren wrote:
> Stephen,
>
> On Tue, Jan 29, 2013 at 2:08 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 01/29/2013 01:40 PM, Tom Warren wrote:
>>> Stephen,
>>>
>>> On Tue, Jan 29, 2013 at 1:09 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>>> 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).
>>>>> + reg = <0x7000c000 0x100>;
>>>>
>>>> The interrupts property is missing here.
>>>
>>> I didn't have an interrupts property for I2C on the T30 dts files,
>>> either.
>>
>> That sounds like a bug in the DT.
>>
>>> What is it used for in U-Boot?
>>
>> U-Boot doesn't use interrupts at least on Tegra, so it's not used.
>> However, it'd be best to keep the U-Boot DT in line with the kernel DT
>> so we can easily spot differences. There has been talk of trying to use
>> the same DT for both too, although we're a long long way off from that.
>
> I'll add it, but it seems silly to add unused values, especially when
> your past review critiques of DT files have asked for minimum
> functionality, which I agree with.
I meant to mention here that my previous comments were about unused
nodes; it doesn't seem useful to add a bunch of nodes that we aren't
using, until the drivers are ready and we actually end up using those
nodes. However, when a node is added, we should fill it in fully, so the
DT conforms to the binding for that node.
next prev parent reply other threads:[~2013-01-30 0:16 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
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 [this message]
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=51086672.3050609@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