linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 00/14] Add support for tegra30 and cardhu
Date: Thu, 15 Dec 2011 10:16:46 -0800	[thread overview]
Message-ID: <20111215181646.GA10631@quad.lixom.net> (raw)
In-Reply-To: <1323875032-18221-1-git-send-email-pdeschrijver@nvidia.com>

On Wed, Dec 14, 2011 at 05:03:12PM +0200, Peter De Schrijver wrote:
> This patchset adds support for the tegra30 SoC and the cardhu development
> board.
> 
> Patchset is on top of linux-next and
> http://www.spinics.net/lists/linux-tegra/msg03016.html.
> 
> Most important changes in v7:
> 
> * split board-dt.c in board-dt-tegra20.c and board-dt-tegra30.c
> * split early init preparation into several patches
> * remove tegra_sdmmc_tap_delay. Drivers should use tegra2_sdmmc_tap_delay as
>   from tegra30 onwards this feature will no longer handled by the clock code
>   as it's implemented in the SDMMC block now.
> * remove CONFIG_CARDHU and the corresponding Kconfig entry

Thanks, this is looking pretty good by now, and remaining rough edges
(if any), can be fixed up over time as well.

I'm ok with it going in but lets have it sit for another day or two until
Stephen is back and has a chance to look it through as well. Colin had
some questions that I want to make sure he's happy with the answers to
as well.


-Olof

  parent reply	other threads:[~2011-12-15 18:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 15:03 [PATCH v7 00/14] Add support for tegra30 and cardhu Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 01/14] arm/tegra: initial device tree for tegra30 Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 02/14] arm/tegra: cleanup tegra20 support Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 03/14] arm/tegra: prepare clock code for multiple tegra variants Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 04/14] arm/tegra: don't export clk_measure_input_freq Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 05/14] arm/tegra: prepare early init for multiple tegra variants Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 06/14] arm/tegra: rename board-dt.c to board-dt-tegra20.c Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 07/14] arm/tegra: use PMC reset Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 08/14] arm/tegra: generalize L2 cache initialization Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 09/14] arm/tegra: rename tegra20 pinmux files Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 10/14] arm/tegra: prepare pinmux code for multiple tegra variants Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 11/14] arm/tegra: add new fields to struct tegra_pingroup_desc Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 12/14] arm/tegra: pinmux tables and definitions for tegra30 Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 13/14] arm/tegra: implement support " Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 14/14] arm/tegra: add support for tegra30 based board cardhu Peter De Schrijver
2011-12-15 18:16 ` Olof Johansson [this message]
2011-12-15 20:54 ` [PATCH v7 00/14] Add support for tegra30 and cardhu Stephen Warren
2011-12-15 22:06 ` Colin Cross
2011-12-18  4:48 ` Olof Johansson
2011-12-19 12:21   ` Peter De Schrijver

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=20111215181646.GA10631@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).