From: Wei Xu <xuwei5@hisilicon.com>
To: David Yang <mmyangfl@gmail.com>
Cc: Russell King <linux@armlinux.org.uk>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <xuwei5@hisilicon.com>
Subject: Re: [PATCH 0/3] ARM: hisi: Support Hi3798 SoC
Date: Thu, 16 Mar 2023 20:22:10 +0800 [thread overview]
Message-ID: <641309F2.8050503@hisilicon.com> (raw)
In-Reply-To: <20230316051936.1775033-1-mmyangfl@gmail.com>
Hi David,
On 2023/3/16 13:19, David Yang wrote:
> This series enables booting Hi3798 SoCs.
>
> David Yang (3):
> ARM: hisi: Add S40 IO map
> ARM: hisi: Add S5 IO map
> ARM: hisi: Support Hi3798 SoC
>
> arch/arm/mach-hisi/Makefile | 2 +-
> arch/arm/mach-hisi/core.h | 6 ++
> arch/arm/mach-hisi/headsmp.S | 36 ++++++++++
> arch/arm/mach-hisi/hisilicon.c | 70 ++++++++++++++++++
> arch/arm/mach-hisi/hotplug.c | 120 +++++++++++++++++++++++++++++--
> arch/arm/mach-hisi/platsmp.c | 128 +++++++++++++++++++++++++++++++++
> 6 files changed, 357 insertions(+), 5 deletions(-)
> create mode 100644 arch/arm/mach-hisi/headsmp.S
>
Thanks!
Series are fine to me.
Please add the device tree as well.
And I am not sure whether the ARMv7 based Hi3798 SoCs are out of support or not.
I checked our website and it seems current generation SoCs are based on ARMv8.
Best Regards,
Wei
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-16 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 5:19 [PATCH 0/3] ARM: hisi: Support Hi3798 SoC David Yang
2023-03-16 5:19 ` [PATCH 1/3] ARM: hisi: Add S40 IO map David Yang
2023-03-16 5:19 ` [PATCH 2/3] ARM: hisi: Add S5 " David Yang
2023-03-16 5:19 ` [PATCH 3/3] ARM: hisi: Support Hi3798 SoC David Yang
2023-03-16 12:22 ` Wei Xu [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=641309F2.8050503@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mmyangfl@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).