public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 00/15] Add PSCI support for Jetson TK1/Tegra124 + CNTFRQ fix
Date: Fri, 17 Apr 2015 08:47:07 +0200	[thread overview]
Message-ID: <5530AC6B.7010707@siemens.com> (raw)
In-Reply-To: <1429021814.15516.72.camel@hellion.org.uk>

On 2015-04-14 16:30, Ian Campbell wrote:
> On Tue, 2015-04-14 at 16:12 +0200, Jan Kiszka wrote:
>> On 2015-04-14 16:06, Stephen Warren wrote:
>>> On 04/14/2015 07:46 AM, Tom Rini wrote:
>>>> On Mon, Apr 13, 2015 at 06:48:05AM +0200, Jan Kiszka wrote:
>>>>
>>>>> Changes in v6:
>>>>>   - rebased over master
>>>>>   - included Thierry's SMMU enabling patch
>>>>>   - moved activation patch at the end so that it can be held back
>>>>>
>>>>> This version can also be found at
>>>>> https://github.com/siemens/u-boot/tree/jetson-tk1-v6.
>>>>
>>>> So what level of coordination do we need on applying this series so that
>>>> kernels (both old and new) can continue to function?  And perhaps README
>>>> updates or similar?  Thanks!
>>>
>>> Hopefully this series doesn't change anything by default, and simply
>>> allows people to turn on support for booting kernels in non-secure mode
>>> if they want to? If so, there shouldn't be any co-ordination required.
>>> If it changes the default behaviour, co-ordination is probably required,
>>> and that'd be a bad thing.
>>
>> Sorry, forgot to mention: I can't flip the default behaviour to leave
>> virtualization support off only for the TK1. That's a generic default.
> 
> Would enabling it in the compile but adding "bootm_boot_mode=sec" to the
> default environment (so it isn't used by default) be considered
> sufficiently backwards compatible?

This turned out to not work as expected: booting in secure mode seems
to prevent that Linux can bring up CPUs 1-3. Not sure if this is to be
expected or a bug, but I will now take a different route:

diff --git a/arch/arm/cpu/armv7/Kconfig b/arch/arm/cpu/armv7/Kconfig
index 61e7c82..e5d4dcc 100644
--- a/arch/arm/cpu/armv7/Kconfig
+++ b/arch/arm/cpu/armv7/Kconfig
@@ -27,7 +27,7 @@ config ARMV7_BOOT_SEC_DEFAULT
 config ARMV7_VIRT
 	boolean "Enable support for hardware virtualization" if EXPERT
 	depends on CPU_V7_HAS_VIRT && ARMV7_NONSEC
-	default y
+	default y if !TEGRA
 	---help---
 	Say Y here to boot in hypervisor (HYP) mode when booting non-secure.
 

A patch to be inserted before the last one (and to be reverted once
Linux is fixed) will follow.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2015-04-17  6:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13  4:48 [U-Boot] [PATCH v6 00/15] Add PSCI support for Jetson TK1/Tegra124 + CNTFRQ fix Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 01/15] sun7i: Remove duplicate call to psci_arch_init Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 02/15] ARM: Factor out common psci_get_cpu_id Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 03/15] ARM: Factor out reusable psci_cpu_off_common Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 04/15] ARM: Factor out reusable psci_cpu_entry Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 05/15] ARM: Factor out reusable psci_get_cpu_stack_top Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 06/15] ARM: Put target PC for PSCI CPU_ON on per-CPU stack Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 07/15] tegra124: Add more registers to struct mc_ctlr Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 08/15] virt-dt: Allow reservation of secure region when in a RAM carveout Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 09/15] tegra: Make tegra_powergate_power_on public Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 10/15] tegra: Add ap_pm_init hook Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 11/15] tegra124: Add PSCI support for Tegra124 Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 12/15] tegra124: Reserve secure RAM using MC_SECURITY_CFG{0, 1}_0 Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 13/15] tegra: Set CNTFRQ for secondary CPUs Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 14/15] ARM: tegra: Enable SMMU when going non-secure Jan Kiszka
2015-04-13  4:48 ` [U-Boot] [PATCH v6 15/15] jetson-tk1: Add PSCI configuration options and reserve secure code Jan Kiszka
2015-04-14 13:46 ` [U-Boot] [PATCH v6 00/15] Add PSCI support for Jetson TK1/Tegra124 + CNTFRQ fix Tom Rini
2015-04-14 14:06   ` Stephen Warren
2015-04-14 14:12     ` Jan Kiszka
2015-04-14 14:21       ` Stephen Warren
2015-04-14 14:30       ` Ian Campbell
2015-04-14 14:33         ` Jan Kiszka
2015-04-14 14:40           ` Ian Campbell
2015-04-14 14:45             ` Jan Kiszka
2015-04-14 14:50               ` Stephen Warren
2015-04-14 15:05                 ` Jan Kiszka
2015-04-14 14:35         ` Stephen Warren
2015-04-17  6:47         ` Jan Kiszka [this message]
2015-04-17 13:57           ` Stephen Warren
2015-04-17 14:02             ` Jan Kiszka
2015-04-17 14:12               ` Stephen Warren
2015-04-17 14:20                 ` Jan Kiszka
2015-04-17 14:43                   ` Stephen Warren
2015-04-18 11:42                     ` Jan Kiszka
2015-04-17 14:04             ` Ian Campbell
2015-04-17  6:56 ` [U-Boot] [PATCH 14.5/15] tegra: Keep virt support disabled by default Jan Kiszka

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=5530AC6B.7010707@siemens.com \
    --to=jan.kiszka@siemens.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