From: Stephen Warren <swarren@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>,
Peter De Schrijver <pdeschrijver@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 v3 0/8] Add support for tegra30 and cardhu
Date: Mon, 7 Nov 2011 11:10:29 -0800 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF173F9A50F3@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <1320675617-20751-1-git-send-email-pdeschrijver@nvidia.com>
Peter De Schrijver wrote at Monday, November 07, 2011 7:20 AM:
> This patchset adds support for the tegra30 SoC and the cardhu development
> board.
>
> Pathset is on top of Will Deacon's ARM reset work.
A few minor issues:
1) If I enable just ARCH_TEGRA_3x_SOC, but not ARCH_TEGRA_2x_SOC, the
kernel fails to build because arch/arm/mach-tegra/include/mach/irqs.h
only defines NR_IRQS if ARCH_TEGRA_2x_SOC is defined.
2) All the Tegra20 boards don't depend on ARCH_TEGRA_2x_SOC, so they can
be enabled even if only Tegra30 support is enabled.
3) I notice that in "arm/tegra: pinmux tables and definitions for tegra30",
you ifdef'd the two entries in tegra_pinmux_of_match[] based on which SoCs
were enabled, but in "arm/tegra: implement support for tegra30", you didn't
do the same for the two entries in early_init[] (board-dt.c). I'm not sure
how far we want to take only-Tegra20 or only-Tegra30 support, but perhaps
we should be consistent here?
I've tested this series on Harmony both booting with a board file and booting
using device-tree and don't see any issues. I'll try to test it on Cardhu
later today.
--
nvpublic
next prev parent reply other threads:[~2011-11-07 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 14:20 Peter De Schrijver
2011-11-07 14:20 ` [PATCH v3 1/8] arm/tegra: initial device tree for tegra30 Peter De Schrijver
2011-11-07 14:20 ` [PATCH v3 2/8] arm/tegra: prepare early init for multiple tegra variants Peter De Schrijver
2011-11-07 19:03 ` Stephen Warren
2011-11-07 14:20 ` [PATCH v3 3/8] arm/tegra: rename tegra20 pinmux files Peter De Schrijver
2011-11-07 14:20 ` [PATCH v3 4/8] arm/tegra: prepare pinmux code for multiple tegra variants Peter De Schrijver
2011-11-07 14:20 ` [PATCH v3 5/8] arm/tegra: add new fields to struct tegra_pingroup_desc Peter De Schrijver
2011-11-07 14:20 ` [PATCH v3 6/8] arm/tegra: pinmux tables and definitions for tegra30 Peter De Schrijver
2011-11-07 14:20 ` [PATCH v3 7/8] arm/tegra: implement support " Peter De Schrijver
2011-11-07 14:20 ` [PATCH v3 8/8] arm/tegra: add support for tegra30 based board cardhu Peter De Schrijver
2011-11-07 19:10 ` Stephen Warren [this message]
2011-11-08 11:45 ` [PATCH v3 0/8] Add support for tegra30 and cardhu Peter De Schrijver
2011-11-08 11:51 ` Peter De Schrijver
2011-11-08 15:56 ` Stephen Warren
2011-11-07 23:03 ` Stephen Warren
2011-11-07 23:08 ` Russell King - ARM Linux
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=74CDBE0F657A3D45AFBB94109FB122FF173F9A50F3@HQMAIL01.nvidia.com \
--to=swarren@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=pdeschrijver@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®