From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: tegra: Fix build error w/ ARCH_TEGRA_114_SOC w/o ARCH_TEGRA_3x_SOC
Date: Wed, 06 Feb 2013 11:05:52 -0700 [thread overview]
Message-ID: <51129B80.9090907@wwwdotorg.org> (raw)
In-Reply-To: <1360167030-14159-1-git-send-email-hdoyu@nvidia.com>
On 02/06/2013 09:10 AM, Hiroshi Doyu wrote:
> This patch fixes the build error when ARCH_TEGRA_114_SOC is enabled
> and ARCH_TEGRA_3x_SOC is disabled.
>
> This provides Tegra114 with its own tegra114_init_early() instead of
> making use of tegra30_init_early() so that T114 build doesn't depend
> on T3x anymore.
Olof, Arnd,
This patch fixes the (well, an) issue for me. Can you apply it directly
to the arm-soc tree. I believe it should apply on top of the
tegra-for-3.9-soc-t114 pull request I sent.
Let me know if you need a resend, although it was CC'd to LAKML, so I
assume you have it in your email history.
BTW, I anticipate a few more fixes coming down the line:
1) Clock-related patch from Laxman so that UART C clock on Cardhu is set
up correctly for Bluetooth. v1 was posted already, but I think a v2 is
needed here.
2) Another fix for Tegra20+Tegra114 w/o Tegra30 build fix from Hiroshi,
related to drivers/amba/tegra-ahb.c, although there aren't any
dependencies there, so perhaps that can go through Russell since he
maintains that tree.
3) Something related to fb2229a "ARM: 7634/1: uncompress debug support
for multiplatform build" since that breaks tegra_defconfig, but I
haven't had a chance to look into that yet.
4) Something related to a boot failure related to crash in
tegra_timer_interrupt(), which I'm just about to go investigate.
Hopefully that's it...
next prev parent reply other threads:[~2013-02-06 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 16:10 [PATCH 1/1] ARM: tegra: Fix build error w/ ARCH_TEGRA_114_SOC w/o ARCH_TEGRA_3x_SOC Hiroshi Doyu
2013-02-06 18:05 ` Stephen Warren [this message]
2013-02-10 1:51 ` Olof Johansson
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=51129B80.9090907@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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).