From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v2 7/8] arm/tegra: implement support for tegra30
Date: Mon, 7 Nov 2011 14:47:46 +0200 [thread overview]
Message-ID: <20111107124746.GP29978@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173F9A4E4F@HQMAIL01.nvidia.com>
On Fri, Nov 04, 2011 at 09:43:57PM +0100, Stephen Warren wrote:
> Peter De Schrijver wrote at Wednesday, November 02, 2011 8:09 AM:
> > Add support for tegra30 SoC. This includes a device tree compatible type for
> > this SoC ("nvidia,tegra30") and adds L2 cache initialization for this new SoC.
> > The clock framework is still missing, which prevents most drivers from working.
> ...
> > diff --git a/arch/arm/mach-tegra/Kconfig b/arch/arm/mach-tegra/Kconfig
> ...
> > @@ -17,7 +14,18 @@ config ARCH_TEGRA_2x_SOC
> > Support for NVIDIA Tegra AP20 and T20 processors, based on the
> > ARM CortexA9MP CPU and the ARM PL310 L2 cache controller
> >
> > -endchoice
> > +config ARCH_TEGRA_3x_SOC
>
> Wasn't that config option already used earlier in the series, e.g. in
> [PATCH v2 6/8] arm/tegra: pinmux tables and definitions for tegra30.
It is. Is that a problem?
Cheers,
Peter.
next prev parent reply other threads:[~2011-11-07 12:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 14:08 [PATCH v2 0/8] Add support for tegra30 and cardhu Peter De Schrijver
2011-11-02 14:09 ` [PATCH v2 1/8] arm/tegra: initial device tree for tegra30 Peter De Schrijver
2011-11-04 20:29 ` Stephen Warren
2011-11-02 14:09 ` [PATCH v2 2/8] arm/tegra: prepare early init for multiple tegra variants Peter De Schrijver
2011-11-02 18:30 ` Colin Cross
2011-11-03 9:21 ` Peter De Schrijver
2011-11-03 10:02 ` Russell King - ARM Linux
2011-11-04 15:09 ` Olof Johansson
2011-11-04 16:30 ` Russell King - ARM Linux
2011-11-07 12:36 ` Peter De Schrijver
2011-11-02 14:09 ` [PATCH v2 3/8] arm/tegra: rename tegra20 pinmux files Peter De Schrijver
2011-11-02 14:09 ` [PATCH v2 4/8] arm/tegra: prepare pinmux code for multiple tegra variants Peter De Schrijver
2011-11-04 20:35 ` Stephen Warren
2011-11-02 14:09 ` [PATCH v2 5/8] arm/tegra: add new fields to struct tegra_pingroup_desc Peter De Schrijver
2011-11-04 21:06 ` Olof Johansson
2011-11-02 14:09 ` [PATCH v2 6/8] arm/tegra: pinmux tables and definitions for tegra30 Peter De Schrijver
2011-11-02 14:09 ` [PATCH v2 7/8] arm/tegra: implement support " Peter De Schrijver
2011-11-04 20:43 ` Stephen Warren
2011-11-07 12:47 ` Peter De Schrijver [this message]
2011-11-02 14:09 ` [PATCH v2 8/8] arm/tegra: add support for tegra30 based board cardhu Peter De Schrijver
2011-11-02 15:46 ` Peter De Schrijver
2011-11-02 16:07 ` Stephen Warren
2011-11-02 16:19 ` Peter De Schrijver
2011-11-02 16:24 ` 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=20111107124746.GP29978@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=ccross@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=swarren@nvidia.com \
/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
all inboxes | Powered by JetHome®