From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Martin Michlmayr <tbm-R+vWnYXSFMfQT0dZR+AlfA@public.gmane.org>,
Mikko Perttunen <cyndis-/1wQRMveznE@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Vagrant Cascadian
<vagrant-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>,
Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: Only 1 CPU on Jetson TX1
Date: Mon, 27 Mar 2017 18:58:24 +0200 [thread overview]
Message-ID: <20170327165824.GA10278@ulmo.ba.sec> (raw)
In-Reply-To: <fe29c677-584f-fd1f-d2f8-ff29c8bebf9c-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
On Mon, Mar 27, 2017 at 09:39:43AM -0600, Stephen Warren wrote:
> On 03/26/2017 04:49 PM, Martin Michlmayr wrote:
> > * Mikko Perttunen <cyndis-/1wQRMveznE@public.gmane.org> [2017-03-25 10:32]:
> > > 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.
> >
> > I can confirm that this works with u-boot from L4T R24.2.1.
> >
> > However, it doesn't work with mainling u-boot (grepping for fdt_copy_
> > doesn't show anything in the source code).
> >
> > Does anyone know how to get all 4 CPUs working with mainline u-boot?
>
> Thierry, Jon, do you know?
>
> The "fdt_copy" feature of U-Boot isn't upstreamed since I thought it was
> only required to boot the L4T kernel, not mainline. We're also reworking L4T
> so this feature won't be needed there either, so I don't expect to upstream
> "fdt_copy".
I vaguely remember that we had discussed this a while ago and I think we
decided that we should hardcode the /psci and /cpus nodes within the DTS
file on the basis that firmware would be considered part of the hardware
as far as the device tree description of it is concerned.
Technically, hard-coding isn't quite correct because someone might end
up not using the firmware that ships with L4T and therefore not have a
working PSCI implementation, but I think it's fairly unlikely that
someone will do that.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-27 16:58 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
[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 [this message]
[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=20170327165824.GA10278@ulmo.ba.sec \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=cyndis-/1wQRMveznE@public.gmane.org \
--cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox