From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/7] tegra: SPI drivers
Date: Tue, 29 Jan 2013 16:11:21 -0800 [thread overview]
Message-ID: <20130130001121.GA17672@badger> (raw)
In-Reply-To: <1359503489-17622-1-git-send-email-amartin@nvidia.com>
On Tue, Jan 29, 2013 at 03:51:22PM -0800, Allen Martin wrote:
> This series updates the tegra20 SPI driver to add fdt support and adds
> a new tegra30 SPI driver.
>
> Testing was done on trimslice (tegra20) and cardhu (tegra30).
>
Tom, this series applies cleanly on top of your T114 series.
> Changes in v4:
> -Added support for fdt aliases to slink driver
> -Check "status" field of fdt node to make sure node is enabled
> Changes in v3:
> -Dropped some fdt patches from the series that were picked up in
> u-boot-tegra/next already
> -Removed SPI node from seaboard, added to trimslice
> -Incorporated feedback from Simon Glass and Stephen Warren to slink
> driver
> Changes in v2:
> -Added new patch to sort dts files prior to adding new nodes
> -Moved "max-spi-frequency" out to board dts files
> -Moved tegra20 SFLASH fdt changes out to separate patch
> -Added valid flag to slink driver controller structure
>
>
> Allen Martin (7):
> tegra20: fdt: add SPI SFLASH node
> tegra: spi: add fdt support to tegra SPI SFLASH driver
> tegra30: add SBC1 to periph id mapping table
> tegra30: fdt: add SPI SLINK nodes
> tegra: add addresses of SPI SLINK controllers
> tegra: add SPI SLINK driver
> tegra: cardhu: config: enable SPI
>
> arch/arm/cpu/tegra30-common/clock.c | 2 +-
> arch/arm/dts/tegra20.dtsi | 12 +
> arch/arm/dts/tegra30.dtsi | 72 ++++++
> arch/arm/include/asm/arch-tegra/tegra.h | 6 +
> arch/arm/include/asm/arch-tegra/tegra_slink.h | 84 ++++++
> board/compulab/dts/tegra20-trimslice.dts | 5 +
> board/nvidia/common/board.c | 3 +-
> board/nvidia/dts/tegra30-cardhu.dts | 5 +
> drivers/spi/Makefile | 1 +
> drivers/spi/tegra_slink.c | 343 +++++++++++++++++++++++++
> drivers/spi/tegra_spi.c | 45 +++-
> include/configs/cardhu.h | 11 +
> include/fdtdec.h | 2 +
> lib/fdtdec.c | 2 +
> 14 files changed, 589 insertions(+), 4 deletions(-)
> create mode 100644 arch/arm/include/asm/arch-tegra/tegra_slink.h
> create mode 100644 drivers/spi/tegra_slink.c
>
> --
> 1.7.10.4
>
-Allen
--
nvpublic
prev parent reply other threads:[~2013-01-30 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 23:51 [U-Boot] [PATCH v4 0/7] tegra: SPI drivers Allen Martin
2013-01-29 23:51 ` [U-Boot] [PATCH v4 1/7] tegra20: fdt: add SPI SFLASH node Allen Martin
2013-01-30 0:15 ` Stephen Warren
2013-01-29 23:51 ` [U-Boot] [PATCH v4 2/7] tegra: spi: add fdt support to tegra SPI SFLASH driver Allen Martin
2013-01-29 23:51 ` [U-Boot] [PATCH v4 3/7] tegra30: add SBC1 to periph id mapping table Allen Martin
2013-01-29 23:51 ` [U-Boot] [PATCH v4 4/7] tegra30: fdt: add SPI SLINK nodes Allen Martin
2013-01-29 23:51 ` [U-Boot] [PATCH v4 5/7] tegra: add addresses of SPI SLINK controllers Allen Martin
2013-01-29 23:51 ` [U-Boot] [PATCH v4 6/7] tegra: add SPI SLINK driver Allen Martin
2013-01-29 23:51 ` [U-Boot] [PATCH v4 7/7] tegra: cardhu: config: enable SPI Allen Martin
2013-01-30 0:11 ` Allen Martin [this message]
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=20130130001121.GA17672@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