public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Ayan Kumar Halder <ayankuma@amd.com>,
	mark.rutland@arm.com, lpieralisi@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: SMP enablement on Cortex-R52 (using PSCI ?)
Date: Tue, 18 Apr 2023 13:14:05 +0100	[thread overview]
Message-ID: <f4227609-ec24-58f8-e4d3-073434fd7ab3@arm.com> (raw)
In-Reply-To: <1cb7d428-c047-1485-e39d-465806f6ef0b@amd.com>

Hi,

On 4/14/23 12:24, Ayan Kumar Halder wrote:
> Hi PSCI developers,
> 
> We have a SoC where there are 4 Cortex-R52 which is distributed in two clusters. So we have 2 Cortex-R52 in one cluster and 2 Cortex-R52 in another cluster.
> 
> We wish to enable SMP on the 2 R52 within a cluster with Xen hypervisor (EL2 software) running on them.
> 
> We are trying to explore if we can use PSCI for booting the secondary cores.
> 

snip

> 
> I wish to know how do we wake up the secondary core if PSCI is not supported.
> 

It looks to me you need to provide/use platform defined method. I see that
Xen provides struct platform_desc with smp_init and cpu_up callbacks...

Cheers
Vladimir

> Kind regards,
> Ayan
> 
> 
> 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-04-18 12:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 11:24 SMP enablement on Cortex-R52 (using PSCI ?) Ayan Kumar Halder
2023-04-18 12:14 ` Vladimir Murzin [this message]
2023-04-19  8:47 ` Sudeep Holla
2023-04-19 17:50   ` Robin Murphy
2023-04-20  9:51     ` Sudeep Holla

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=f4227609-ec24-58f8-e4d3-073434fd7ab3@arm.com \
    --to=vladimir.murzin@arm.com \
    --cc=ayankuma@amd.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=sstabellini@kernel.org \
    /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