From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] sunxi: PSCI support for H3
Date: Thu, 21 Jan 2016 19:02:11 +0100 [thread overview]
Message-ID: <56A11D23.3020707@redhat.com> (raw)
In-Reply-To: <1452064389-14816-1-git-send-email-wens@csie.org>
Hi,
On 01/06/2016 08:13 AM, Chen-Yu Tsai wrote:
> Hi everyone,
>
> This series enables PSCI support for the H3. Like other Allwinner SoCs,
> the implementation only supports PSCI 0.1, specifically only secondary
> CPU boot/hotplug.
>
> Patch 1 supports the SMTA (previously called TZPC) TrustZone hardware
> on H3. This controls non-secure access to some important hardware blocks.
>
> Patch 2 supports the security switch in H3's CCU. This is H3 only. No
> other SoCs have this feature.
>
> Patch 3 supports H3 using sun6i PSCI implementation. H3 uses the same
> power sequence as sun6i, including the power clamps. This is shown in
> Allwinner's SDK, and confirmed / tested by Siarhei.
>
> Patch 4 enables PSCI support for the H3 in Kconfig.
>
>
> I've only tested booting HYP/SMP on my Orange Pi PC. Hotplugging was not
> tested, but should work.
Many thanks for this patch-set, I've applied this to my tree, and it will
be part of the pull-req I plan to send out this weekend.
Regards,
Hans
prev parent reply other threads:[~2016-01-21 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 7:13 [U-Boot] [PATCH 0/4] sunxi: PSCI support for H3 Chen-Yu Tsai
2016-01-06 7:13 ` [U-Boot] [PATCH 1/4] sunxi: Support Secure Memory Touch Arbiter (SMTA) in sun8i H3 Chen-Yu Tsai
2016-01-21 18:25 ` Hans de Goede
2016-01-06 7:13 ` [U-Boot] [PATCH 2/4] sunxi: Support H3 CCU security switches Chen-Yu Tsai
2016-01-06 7:13 ` [U-Boot] [PATCH 3/4] sunxi: Support PSCI ops on Allwinner H3 Chen-Yu Tsai
2016-01-06 7:13 ` [U-Boot] [PATCH 4/4] sunxi: Enable booting non-secure and virtualization for H3 Chen-Yu Tsai
2016-01-06 10:45 ` [U-Boot] [PATCH 0/4] sunxi: PSCI support " Jens Kuske
2016-01-21 18:02 ` Hans de Goede [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=56A11D23.3020707@redhat.com \
--to=hdegoede@redhat.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 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.