All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Perttunen <cyndis-/1wQRMveznE@public.gmane.org>
To: Martin Michlmayr <tbm-R+vWnYXSFMfQT0dZR+AlfA@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Vagrant Cascadian <vagrant-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Subject: Re: Only 1 CPU on Jetson TX1
Date: Sat, 25 Mar 2017 10:32:51 +0200	[thread overview]
Message-ID: <6da81dbc-b070-da0f-1589-ec2cb8f453d5@kapsi.fi> (raw)
In-Reply-To: <20170323001131.GA7507-IRMp5PtgtdoigzW5ZibpNwC/G2K4zDHf@public.gmane.org>

It appears you need to have

   fdt_copy_node_names=/cpus:/psci
   fdt_copy_src_addr=0x83080000

in your U-Boot configuration. This is documented somewhere in the middle 
of http://elinux.org/Jetson/TX1_Upstream_Kernel.

On 03/23/2017 02:11 AM, Martin Michlmayr wrote:
> Vagrant Cascadian observed that only 1 CPU is activated on the Jetson
> TX1 development kit.
>
> I can confirm this with mainline Linux and u-boot from mainline (2016.11)
> or L4T (2016.03-00633-g3ef9cdb from R23.2).
>
> I see the following in dmesg:
>
> [    0.000000] /cpus/cpu@1: missing enable-method property
> [    0.000000] /cpus/cpu@2: missing enable-method property
> [    0.000000] /cpus/cpu@3: missing enable-method property
>
> [    0.052643] Tegra Revision: A02 SKU: 23 CPU Process: 0 SoC Process: -22
> [    0.053149] EFI services will not be available.
> [    0.053316] Brought up 1 CPUs
> [    0.053325] SMP: Total of 1 processors activated.
> [    0.053341] CPU: All CPU(s) started at EL2
>

  parent reply	other threads:[~2017-03-25  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  0:11 Only 1 CPU on Jetson TX1 Martin Michlmayr
     [not found] ` <20170323001131.GA7507-IRMp5PtgtdoigzW5ZibpNwC/G2K4zDHf@public.gmane.org>
2017-03-25  8:32   ` Mikko Perttunen [this message]
     [not found]     ` <6da81dbc-b070-da0f-1589-ec2cb8f453d5-/1wQRMveznE@public.gmane.org>
2017-03-26 22:49       ` Martin Michlmayr
     [not found]         ` <20170326224912.GD4723-IRMp5PtgtdoigzW5ZibpNwC/G2K4zDHf@public.gmane.org>
2017-03-27 15:39           ` Stephen Warren
     [not found]             ` <fe29c677-584f-fd1f-d2f8-ff29c8bebf9c-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2017-03-27 16:04               ` Jon Hunter
2017-03-27 16:58               ` Thierry Reding
     [not found]                 ` <20170327165824.GA10278-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2017-03-27 17:03                   ` Stephen 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=6da81dbc-b070-da0f-1589-ec2cb8f453d5@kapsi.fi \
    --to=cyndis-/1wqrmvezne@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tbm-R+vWnYXSFMfQT0dZR+AlfA@public.gmane.org \
    --cc=vagrant-8fiUuRrzOP0dnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.