public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] Re: PSCI for H3
Date: Sun, 27 Dec 2015 18:16:07 +0100	[thread overview]
Message-ID: <20151227171607.GG30359@lukather> (raw)
In-Reply-To: <20151223121415.050a3955@i7>

On Wed, Dec 23, 2015 at 12:14:15PM +0200, Siarhei Siamashka wrote:
> On Tue, 17 Nov 2015 15:32:30 +0100
> Jens Kuske <jenskuske@gmail.com> wrote:
> 
> > On 16/11/15 07:26, Chen-Yu Tsai wrote:
> > > Hi everyone,
> > > 
> > > I got my Orange Pi PC booting U-boot now, using Hans' sunxi-wip branch that
> > > includes Jens' patches.
> > > 
> > > For PSCI and SMP, it seems the H3 follows the structure of previous sun8i SoCs.
> > > The CPUCFG registers line up. The manual doesn't have the PRCM, so I'll have to
> > > dig through the SDK.
> > > 
> > > One other thing is the SMTA, or Secure Memory Touch Arbiter, which we last
> > > encountered issues with on the A31s. This controls non-secure access to a whole
> > > bunch of peripherals, which we'll need to enable for Linux to run non-secure.  
> > 
> > There is also register 0x2f0 in the CCU, it defaults to disabling
> > non-secure access to all clock registers.
> > 
> > Jens
> > 
> 
> How about just enabling SMP on Allwinner H3 in an old unfashionable way
> while all these non-secure access limiters are still being under
> investigation?

I'd really prefer not to.

This ends up being dead code that no-one uses, but we can't really
remove. Adding support for the H3 support would only delay that
removal once again.

What controller are you having issues accessing?

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151227/574480d6/attachment.sig>

  parent reply	other threads:[~2015-12-27 17:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16  6:24 [U-Boot] PSCI for H3 wens Tsai
2015-11-16  6:26 ` [U-Boot] Fwd: " Chen-Yu Tsai
2015-11-17 14:32   ` [U-Boot] " Jens Kuske
2015-12-23 10:14     ` [U-Boot] [linux-sunxi] " Siarhei Siamashka
2015-12-23 14:36       ` Chen-Yu Tsai
2015-12-23 14:56         ` Siarhei Siamashka
2015-12-27 17:16       ` Maxime Ripard [this message]
2016-01-04  4:02         ` Chen-Yu Tsai

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=20151227171607.GG30359@lukather \
    --to=maxime.ripard@free-electrons.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