linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: tegra: Enable all cores on Jetson TX1
Date: Thu, 30 Jun 2016 11:22:31 +0200	[thread overview]
Message-ID: <20160630092231.GA1776@ulmo.ba.sec> (raw)
In-Reply-To: <20160630080119.27090-1-acourbot@nvidia.com>

On Thu, Jun 30, 2016 at 05:01:19PM +0900, Alexandre Courbot wrote:
> Enable PSCI firmware and all 4 cores of T210 on Jetson TX1.
> 
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> ---
> Not sure why this was not done - in any case this seems to work fine
> and performance is obviously improved (especially boot time).
> 
>  arch/arm64/boot/dts/nvidia/tegra210-p2371-2180.dts | 23 ++++++++++++++++++++++
>  1 file changed, 23 insertions(+)

The reason why this wasn't done initially is because the firmware was
supposed to copy this data into the device tree before passing it to the
kernel. The rationale for this decision was that we can't make any
assumptions about the firmware and any potential PSCI implementation.

I suppose the firmware interface could be argued to be part of the
hardware and therefore having it statically in DT would be okay. The one
remaining issue is that it is possible to boot a Tegra X1 without any
secure firmware that might provide PSCI, in which case the DT would now
be lying.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160630/a45956b2/attachment.sig>

      reply	other threads:[~2016-06-30  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30  8:01 [PATCH] arm64: tegra: Enable all cores on Jetson TX1 Alexandre Courbot
2016-06-30  9:22 ` Thierry Reding [this message]

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=20160630092231.GA1776@ulmo.ba.sec \
    --to=thierry.reding@gmail.com \
    --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).