public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Thierry Reding <treding@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 0/4] Jetson-TK1 support for PSCI
Date: Wed, 14 Jan 2015 08:57:25 +0100	[thread overview]
Message-ID: <20150114075724.GD9491@ulmo.nvidia.com> (raw)
In-Reply-To: <1421178290.11796.159.camel@hellion.org.uk>

On Tue, Jan 13, 2015 at 07:44:50PM +0000, Ian Campbell wrote:
> Hi Thierry,
> 
> I needed to boot my Jetson in NS mode (in order to boot Xen) and was
> investigating the possibility of PSCI support when I discovered that you
> had already started on it[0]. Hurrah!
> 
> I cherry-picked the relevant commit onto u-boot-tegra#master and added a
> few more patches and now it boots correctly for me, both running Xen
> (some Xen side patches are needed too) and native Linux.
> 
> The main things which was needed was to rebase for some recent Kconfig
> changes relating to virt and nonsec mode and to arrange for the RAM used
> by the secure code to be reserved in the FDT. I also reserved the RAM
> using the hardware MC_SECURITY_CFG registers for good measure.

Great, those were all things that I had wanted to do but never got
around to.

> I also pushed my tree to gitorious:
>         https://gitorious.org/ijc/u-boot jetson-psci-v1
> 
> I would Ack your patch, but I don't think you've posted it and it has no
> S-o-b so that would seem a bit premature/rude of me. For the same reason
> I've not actually included it in the series posted (but it is in the
> gitorious branch).

Feel free to take ownership of that patch. I currently don't have the
time to work on this and it seems you've made good progress on it.

It could probably use some cleanup because there's a bit of debug output
still in there. Also...

> FWIW I think you could drop your stub versions of psci_cpu_off and
> psci_cpu_suspend (assuming you don't want to implement them) since the
> common code has stubs.

... I'd think you'd need to implement these so that you can get proper
suspend/resume support in the kernel. I've had to disable cpuidle (via
#undef CONFIG_PM_SLEEP in arch/arm/mach-tegra/cpuidle-tegra114.c) in the
kernel to make that code not powergate CPUs. Ideally I think the kernel
would check that it's running with PSCI support and disable the cpuidle
driver. Maybe that could be done by introducing a new cpuidle driver
that checks for PSCI availability and uses it when present.

Adding Stephen and Tom for visibility.

Thanks,
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150114/be89bdb9/attachment.pgp>

  parent reply	other threads:[~2015-01-14  7:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 19:44 [U-Boot] [PATCH v1 0/4] Jetson-TK1 support for PSCI Ian Campbell
2015-01-13 19:45 ` [U-Boot] [PATCH v1 1/4] tegra124: Add more registers to struct mc_ctlr Ian Campbell
2015-01-15 23:37   ` Stephen Warren
2015-01-16  9:32     ` Ian Campbell
2015-01-13 19:45 ` [U-Boot] [PATCH v1 2/4] virt-dt: Allow reservation of the secure region when it is in a RAM carveout Ian Campbell
2015-01-15 23:49   ` Stephen Warren
2015-01-16  9:33     ` Ian Campbell
2015-01-18 18:06     ` Ian Campbell
2015-01-13 19:45 ` [U-Boot] [PATCH v1 3/4] jetson-tk1: Add PSCI configuration options and reserve secure code Ian Campbell
2015-01-15 23:59   ` Stephen Warren
2015-01-16  8:52     ` Thierry Reding
2015-01-16  9:39       ` Ian Campbell
2015-01-19 17:17         ` Stephen Warren
2015-01-13 19:46 ` [U-Boot] [PATCH v1 4/4] tegra124: Reserve secure RAM using MC_SECURITY_CFG{0, 1}_0 Ian Campbell
2015-01-14  7:57 ` Thierry Reding [this message]
2015-01-14  8:58   ` [U-Boot] [PATCH v1 0/4] Jetson-TK1 support for PSCI Ian Campbell
2015-01-15 14:55     ` Thierry Reding
2015-01-16  9:43       ` Ian Campbell
2015-01-16 10:05         ` Thierry Reding
2015-01-16 10:24           ` Ian Campbell
2015-01-16 16:03             ` Thierry Reding
2015-01-16 16:11               ` Ian Campbell
2015-01-19  9:25                 ` Thierry Reding
2015-01-19 12:09                   ` Ian Campbell
2015-01-15 19:19   ` Mark Rutland
2015-01-16  9:12     ` Thierry Reding
2015-01-22 19:20       ` Mark Rutland
2015-01-23 10:10         ` Thierry Reding
2015-01-23 12:37           ` Mark Rutland
2015-01-23 14:08             ` Mark Rutland
2015-01-30 12:20             ` Thierry Reding
2015-02-05 11:44             ` Thierry Reding
2015-02-05 12:01               ` Ian Campbell
2015-02-05 12:37               ` Mark Rutland
2015-02-05 13:55                 ` Thierry Reding
2015-02-05 14:37                   ` Ian Campbell
2015-02-09 11:26                   ` Mark Rutland
2015-02-14 15:08                     ` Jan Kiszka
2015-02-19  9:20                       ` Ian Campbell

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=20150114075724.GD9491@ulmo.nvidia.com \
    --to=treding@nvidia.com \
    --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