From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Tegra: fdt: Add/enhance sdhci (mmc) nodes for all T20 DT files
Date: Mon, 11 Feb 2013 13:48:59 -0600 [thread overview]
Message-ID: <1360612139.8517.5@snotra> (raw)
In-Reply-To: <CAPnjgZ157OR2E+-jh_oH6yQVKKG+D3GSGeezBCtfswR7hoPbgw@mail.gmail.com> (from sjg@chromium.org on Tue Feb 5 22:56:59 2013)
On 02/05/2013 10:56:59 PM, Simon Glass wrote:
> Hi,
>
> On Tue, Feb 5, 2013 at 12:49 PM, Stephen Warren
> <swarren@wwwdotorg.org> wrote:
> > Right now, I believe your/Simon's policy on DT is to only include
> in the
> > U-Boot .dts files what's actually needed for U-Boot. I've asked that
> > this be done on a per-node basis rather than per-property basis in
> order
> > to reduce diffs. If you want to change that, and include nodes that
> > U-Boot doesn't need, that'd be great and assist unification, but
> then
> > I'd recommend simply importing the current kernel .dts files as-is
> > without any changes, rather than adding things piece-meal.
>
> I have to say that within reason I like the idea of bring in the DT
> from the kernel as is, limited perhaps to the nodes that U-Boot
> actually uses.
>
> A separate repo for the DT files seems like something that should
> happen, but I have seen little progress on that front. Still, when it
> happens, it would be nice it we could drop U-Boot's files and just use
> the kernel's. That will be a lot easier if we head in that direction
> now.
I think any device tree that makes assumptions about what U-Boot will
be fixing up, or even what addresses U-Boot will configure devices at,
belongs in the U-Boot tree. Keeping such trees in Linux has been
awkward so far, especially when a change gets made to such an
assumption, or when U-Boot isn't the only supported firmware.
-Scott
next prev parent reply other threads:[~2013-02-11 19:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 23:48 [U-Boot] [PATCH 0/2] Tegra: MMC: Add DT support for MMC to T20 boards Tom Warren
2013-02-04 23:48 ` [U-Boot] [PATCH 1/2] Tegra: fdt: Add/enhance sdhci (mmc) nodes for all T20 DT files Tom Warren
2013-02-05 19:54 ` Stephen Warren
2013-02-05 20:29 ` Tom Warren
2013-02-05 20:49 ` Stephen Warren
2013-02-06 4:56 ` Simon Glass
2013-02-11 19:48 ` Scott Wood [this message]
2013-02-04 23:48 ` [U-Boot] [PATCH 2/2] Tegra: MMC: Add DT support to MMC driver for all T20 boards Tom Warren
2013-02-05 9:28 ` [U-Boot] [PATCH 2/2] Tegra: MMC: Add DT support to MMC driver forall " Marc Dietrich
2013-02-05 15:31 ` Tom Warren
2013-02-05 20:06 ` [U-Boot] [PATCH 2/2] Tegra: MMC: Add DT support to MMC driverforall " Marc Dietrich
2013-02-05 20:41 ` Tom Warren
2013-02-05 20:51 ` Stephen Warren
2013-02-05 20:54 ` [U-Boot] [PATCH 2/2] Tegra: MMC: Add DT support to MMCdriverforall " Marc Dietrich
2013-02-05 21:26 ` Tom Warren
2013-02-05 20:03 ` [U-Boot] [PATCH 2/2] Tegra: MMC: Add DT support to MMC driver for all " Stephen Warren
2013-02-05 21:02 ` Tom Warren
2013-02-05 23:51 ` Stephen Warren
2013-02-12 18:07 ` Simon Glass
2013-02-12 19:05 ` Tom Warren
2013-02-12 19:08 ` Simon Glass
2013-02-12 20:13 ` Stephen Warren
2013-02-12 22:34 ` Simon Glass
2013-02-12 18:05 ` Simon Glass
2013-02-05 0:02 ` [U-Boot] [PATCH 0/2] Tegra: MMC: Add DT support for MMC to " Tom Warren
2013-02-05 10:21 ` Thierry Reding
2013-02-05 15:31 ` 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=1360612139.8517.5@snotra \
--to=scottwood@freescale.com \
--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