public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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: Tue, 12 Feb 2013 12:26:01 -0700	[thread overview]
Message-ID: <511A9749.3050903@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ3zCLazXtoXWFpF1XoLNE2+LXeT=5ZLAjStXL+HOq62RA@mail.gmail.com>

On 02/12/2013 12:17 PM, Simon Glass wrote:
> Hi Tom,
> 
> On Tue, Feb 12, 2013 at 11:13 AM, Tom Warren <twarren.nvidia@gmail.com> wrote:
...
>> That's the current POR for Tegra DT use in upstream U-Boot, assuming I
>> can find an up-to-date kernel with the latest DTS files (I'll use
>> Stephen's swarren/linux-tegra.git/for-next until told otherwise).
> 
> Yes that was always my problem - finding what the kernel actually
> used, might use, etc.

I must say I find this quite puzzling; the kernel repos aren't exactly
hidden.

Tegra's kernel for-next is likely the best place right now as any DT
changes typically go through that tree. However, on the off-chance any
other maintainer picks up any changes, linux-next.git would have the
latest bindings. That's all been true for a year or more.

That said, there is a move to either move the binding definitions and
.dts files out of the kernel tree and/or stop taking changes to them
through individual SoC trees, but perhaps through the device tree repo.
If that does happen, I'll let you know.

  reply	other threads:[~2013-02-12 19:26 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 [this message]
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=511A9749.3050903@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