From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] sun7i: Add support for taking CPUs offline via PSCI
Date: Mon, 29 Dec 2014 14:08:44 +0000 [thread overview]
Message-ID: <1419862124.13595.103.camel@hellion.org.uk> (raw)
In-Reply-To: <d2b19b1ac8ffbe535a44334edf929c1e5903a97a.1418643457.git.jan.kiszka@siemens.com>
On Mon, 2014-12-15 at 12:37 +0100, Jan Kiszka wrote:
> + movw r8, #(GICC_BASE & 0xffff)
> + movt r8, #(GICC_BASE >> 16)
> + ldr r9, [r8, #GICC_IAR]
> + movw r10, #0x3ff
> + movt r10, #0
> + cmp r9, r10
> + beq out
> + movw r10, #0x3fe
> + cmp r9, r10
> + beq out
> + str r9, [r8, #GICC_EOIR]
> + dsb
This block could do with a leading comment like the others. It is
reading IAR and discarding any spurious interrupts (1022+1023), but not
explicitly checking for SGI15, presumably because it can be asserted
that there is no other possible interrupt which can end up here, is that
right?
> +
> +.globl psci_cpu_off
> +psci_cpu_off:
> + mrc p15, 0, r0, c1, c0, 0 @ SCTLR
> + bic r0, r0, #(1 << 2) @ Clear C bit
> + mcr p15, 0, r0, c1, c0, 0 @ SCTLR
> + isb
> + dsb
> +
> + bl v7_flush_dcache_all
> +
> + clrex @ Why???
Anyone got any clues? (Just curiosity, not a blocker)
Apart from the comment:
Acked-by: Ian Campbell <ijc@hellion.org.uk>
Ian.
next prev parent reply other threads:[~2014-12-29 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 11:37 [U-Boot] [PATCH 0/2] sun7i: PSCI enhancements Jan Kiszka
2014-12-15 11:37 ` [U-Boot] [PATCH 1/2] sun7i: Add support for taking CPUs offline via PSCI Jan Kiszka
2014-12-29 14:08 ` Ian Campbell [this message]
2014-12-31 11:57 ` Jan Kiszka
2014-12-15 11:37 ` [U-Boot] [PATCH 2/2] sun7i: Add PSCI v0.2 support Jan Kiszka
2014-12-15 11:44 ` Hans de Goede
2014-12-15 15:27 ` Jan Kiszka
2014-12-15 15:48 ` Hans de Goede
2014-12-29 14:12 ` Ian Campbell
2014-12-31 11:57 ` Jan Kiszka
2015-01-07 18:41 ` 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=1419862124.13595.103.camel@hellion.org.uk \
--to=ijc@hellion.org.uk \
--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