public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: only enable SCU on Tegra20
Date: Tue, 04 Jun 2013 13:33:30 -0600	[thread overview]
Message-ID: <51AE410A.1030506@wwwdotorg.org> (raw)
In-Reply-To: <1369347978-31508-1-git-send-email-swarren@wwwdotorg.org>

On 05/23/2013 04:26 PM, Stephen Warren wrote:
> From: Tom Warren <twarren@nvidia.com>
> 
> The non-SPL build of U-Boot on Tegra only runs on a single CPU, and
> hence there is no need to enable the SCU when running U-Boot. If an
> SMP OS is booted, and it needs the SCU enabled, it will enable the SCU
> itself. U-Boot doing so is redundant.
> 
> The one exception is Tegra20, where an enabled SCU is required for some
> aspects of PCIe to work correctly.
> 
> Some Tegra SoCs contain CPUs without a software-controlled SCU. In this
> case, attempting to turn it on actively causes problems. This is the case
> for Tegra114. For example, when running Linux, the first (or at least
> some very early) user-space process will trigger the following kernel
> message:
> 
> Unhandled fault: imprecise external abort (0x406) at 0x00000000
> 
> This is typically accompanied by that process receving a fatal signal,
> and exiting. Since this process is usually pid 1, this causes total
> system boot failure.

Tom, is this patch OK? It's a rather critical bug-fix for Tegra114, so
I'd like to make sure it gets into the upcoming release. Thanks.

  reply	other threads:[~2013-06-04 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 22:26 [U-Boot] [PATCH] ARM: tegra: only enable SCU on Tegra20 Stephen Warren
2013-06-04 19:33 ` Stephen Warren [this message]
2013-06-04 20:33   ` Tom Warren

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=51AE410A.1030506@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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