From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/7] tegra: fdt: add apbdma node
Date: Fri, 11 Jan 2013 19:19:00 -0800 [thread overview]
Message-ID: <20130112031900.GA27011@badger> (raw)
In-Reply-To: <50F0A997.3080603@wwwdotorg.org>
On Fri, Jan 11, 2013 at 04:08:55PM -0800, Stephen Warren wrote:
> On 01/11/2013 11:44 AM, Allen Martin wrote:
> > Add apbdma node for tegra20 and tegra30, copied directly from tegra
> > Linux dtsi files.
>
> > diff --git a/arch/arm/dts/tegra20.dtsi b/arch/arm/dts/tegra20.dtsi
>
> > + apbdma: dma {
> > + compatible = "nvidia,tegra20-apbdma";
> > + reg = <0x6000a000 0x1200>;
> ...
> > intc: interrupt-controller at 50041000 {
>
> Can the nodes be kept sorted by address?
>
They're already unsorted. I'll add a new patch to sort them, then add
this one on top.
-Allen
--
nvpublic
next prev parent reply other threads:[~2013-01-12 3:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 18:44 [U-Boot] [PATCH 0/7] tegra: SPI drivers Allen Martin
2013-01-11 18:44 ` [U-Boot] [PATCH 1/7] tegra: fdt: add apbdma node Allen Martin
2013-01-12 0:08 ` Stephen Warren
2013-01-12 3:19 ` Allen Martin [this message]
2013-01-12 6:07 ` Stephen Warren
2013-01-12 6:49 ` Allen Martin
2013-01-11 18:44 ` [U-Boot] [PATCH 2/7] tegra: spi: add fdt support to tegra SPI SFLASH driver Allen Martin
2013-01-12 0:13 ` Stephen Warren
2013-01-12 3:40 ` Allen Martin
2013-01-11 18:44 ` [U-Boot] [PATCH 3/7] tegra30: add SBC1 to periph id mapping table Allen Martin
2013-01-11 18:44 ` [U-Boot] [PATCH 4/7] tegra30: fdt: add SPI SLINK nodes Allen Martin
2013-01-12 0:17 ` Stephen Warren
2013-01-12 3:42 ` Allen Martin
2013-01-11 18:44 ` [U-Boot] [PATCH 5/7] tegra: add addresses of SPI SLINK controllers Allen Martin
2013-01-11 18:44 ` [U-Boot] [PATCH 6/7] tegra: add SPI SLINK driver Allen Martin
2013-01-12 0:22 ` Stephen Warren
2013-01-12 3:58 ` Allen Martin
2013-01-11 18:44 ` [U-Boot] [PATCH 7/7] tegra: cardhu: config: enable SPI Allen Martin
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=20130112031900.GA27011@badger \
--to=amartin@nvidia.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