From: Ayan Kumar Halder <ayankuma@amd.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
geert+renesas@glider.be, magnus.damm@gmail.com,
konrad.dybcio@linaro.org, andersson@kernel.org,
mazziesaccount@gmail.com, conor.dooley@microchip.com,
j@jannau.net, mailingradian@gmail.com, me@iskren.info,
lpieralisi@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-renesas-soc@vger.kernel.org, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Michal Orzel <michal.orzel@amd.com>,
Michal Simek <michal.simek@xilinx.com>
Subject: Need suggestions for smp related properties in cpus.yaml to support smpboot for cortex-r52 based platform
Date: Thu, 11 May 2023 10:35:37 +0100 [thread overview]
Message-ID: <c5ed90c7-7126-0757-a0e3-e3d1fcab2ecc@amd.com> (raw)
Hi Device Tree engineers,
Recently I have ported Xen on Cortex-R52 (AArch32-V8R processor) for our
AMD platform.
I was discussing with xen-devel community about how we can properly
support smpboot when I was suggested that this might be the correct
forum for discussion.
Please refer
https://lists.xenproject.org/archives/html/xen-devel/2023-05/msg00224.html
and the follow-ups for context.
The way smpboot works on our platform is as follows:-
1. core0 writes to register (say regA) the address of the secondary core
initialization routine.
2. core0 writes to another register (say regB) the value "0x1" to put
the secondary core in reset mode.
3. core0 writes to regB the value "0x0" to pull the secondary core out
of reset mode.
regA, regB will differ for core1, core2, core3 and so on.
Currently, I am trying to bringup core1 only.
I am thinking to use "enable-method=spin-table" in the cpu node for
core1. So that I can use "cpu-release-address" for regA.
For regB, I am thinking of introducing a new property
"amd-cpu-reset-addr" in the cpu node.
Please let me know your thoughts on this approach. I am also open to any
alternative suggestions.
Also I see that in
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/devicetree/bindings/arm/cpus.yaml#L87
, "arm,cortex-r52" is missing.
Can I submit a patch (a one line change) to add this ?
Kind regards,
Ayan
next reply other threads:[~2023-05-11 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 9:35 Ayan Kumar Halder [this message]
2023-05-11 17:17 ` Need suggestions for smp related properties in cpus.yaml to support smpboot for cortex-r52 based platform Krzysztof Kozlowski
2023-05-15 10:08 ` Sudeep Holla
2023-05-18 18:37 ` Ayan Kumar Halder
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=c5ed90c7-7126-0757-a0e3-e3d1fcab2ecc@amd.com \
--to=ayankuma@amd.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=j@jannau.net \
--cc=julien@xen.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mailingradian@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=mazziesaccount@gmail.com \
--cc=me@iskren.info \
--cc=michal.orzel@amd.com \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--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