From: Sam Edwards <cfsworks@gmail.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: u-boot@lists.denx.de, Maksim Kiselev <bigunclemax@gmail.com>,
Sam Edwards <CFSworks@gmail.com>
Subject: [RFC PATCH 0/4] Allwinner R528/T113s PSCI
Date: Thu, 1 Jun 2023 15:48:10 -0600 [thread overview]
Message-ID: <20230601214814.128336-1-CFSworks@gmail.com> (raw)
Hi Andre (and list),
Per our previous discussion, these are my patches to add PSCI support to your
WIP R528/T113s series. I am sending it as RFC because I have CC'd the list and
don't want these changes to be treated as patches against upstream.
The first patch in this series provides a few more register definitions for
cpu_sunxi_ncat2.h. The next two are refactoring, independent of any specific
arch/SoC. The final patch adds PSCI support.
It might or might not be appropriate to split out the refactoring patches for
separate review and inclusion; otherwise, the intent of this patchset is to be
incorporated into the existing R528 series.
Cheers,
Sam
Sam Edwards (4):
SQUASH ME
sunxi: psci: clean away preprocessor macros
sunxi: psci: refactor register access to separate functions
sunxi: psci: implement PSCI on R528
arch/arm/cpu/armv7/sunxi/psci.c | 185 ++++++++++++------
.../include/asm/arch-sunxi/cpu_sunxi_ncat2.h | 7 +-
arch/arm/mach-sunxi/Kconfig | 2 +
include/configs/sunxi-common.h | 8 +
4 files changed, 138 insertions(+), 64 deletions(-)
--
2.39.2
next reply other threads:[~2023-06-01 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 21:48 Sam Edwards [this message]
2023-06-01 21:48 ` [RFC PATCH 1/4] SQUASH ME Sam Edwards
2023-06-01 21:48 ` [RFC PATCH 2/4] sunxi: psci: clean away preprocessor macros Sam Edwards
2023-06-01 21:48 ` [RFC PATCH 3/4] sunxi: psci: refactor register access to separate functions Sam Edwards
2023-06-01 21:48 ` [RFC PATCH 4/4] sunxi: psci: implement PSCI on R528 Sam Edwards
2023-06-02 20:53 ` Maksim Kiselev
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=20230601214814.128336-1-CFSworks@gmail.com \
--to=cfsworks@gmail.com \
--cc=andre.przywara@arm.com \
--cc=bigunclemax@gmail.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.