From: Steen Hegelund <steen.hegelund@microchip.com>
To: Robert Marko <robert.marko@sartura.hr>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <lars.povlsen@microchip.com>,
<daniel.machon@microchip.com>, <UNGLinuxDriver@microchip.com>,
<arnd@arndb.de>, <alexandre.belloni@bootlin.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <luka.perkov@sartura.hr>
Subject: Re: [PATCH v2 1/3] arm64: dts: microchip: sparx5: do not use PSCI on reference boards
Date: Tue, 21 Feb 2023 14:59:56 +0100 [thread overview]
Message-ID: <b90c582b8ddf0429058361ff42dc63ad1337bf43.camel@microchip.com> (raw)
In-Reply-To: <20230221105039.316819-1-robert.marko@sartura.hr>
Hi Robert,
I find this very useful since the Sparx5 SoC does not support TFA and therefore
cannot provide PSCI on its own, as you also state below.
Acked-by: Steen Hegelund <Steen.Hegelund@microchip.com>
On Tue, 2023-02-21 at 11:50 +0100, Robert Marko wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> PSCI is not implemented on SparX-5 at all, there is no ATF and U-boot that
> is shipped does not implement it as well.
>
> I have tried flashing the latest BSP 2022.12 U-boot which did not work.
> After contacting Microchip, they confirmed that there is no ATF for the
> SoC nor PSCI implementation which is unfortunate in 2023.
>
> So, disable PSCI as otherwise kernel crashes as soon as it tries probing
> PSCI with, and the crash is only visible if earlycon is used.
>
> Since PSCI is not implemented, switch core bringup to use spin-tables
> which are implemented in the vendor U-boot and actually work.
>
> Tested on PCB134 with eMMC (VSC5640EV).
>
> Fixes: 6694aee00a4b ("arm64: dts: sparx5: Add basic cpu support")
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> ---
> Changes in v2:
> * As suggested by Arnd, disable PSCI only on reference boards
> ---
> arch/arm64/boot/dts/microchip/sparx5.dtsi | 2 +-
> arch/arm64/boot/dts/microchip/sparx5_pcb_common.dtsi | 12 ++++++++++++
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/microchip/sparx5.dtsi
> b/arch/arm64/boot/dts/microchip/sparx5.dtsi
> index 0367a00a269b3..5eae6e7fd248e 100644
> --- a/arch/arm64/boot/dts/microchip/sparx5.dtsi
> +++ b/arch/arm64/boot/dts/microchip/sparx5.dtsi
> @@ -61,7 +61,7 @@ arm-pmu {
> interrupt-affinity = <&cpu0>, <&cpu1>;
> };
>
> - psci {
> + psci: psci {
> compatible = "arm,psci-0.2";
> method = "smc";
> };
> diff --git a/arch/arm64/boot/dts/microchip/sparx5_pcb_common.dtsi
> b/arch/arm64/boot/dts/microchip/sparx5_pcb_common.dtsi
> index 9d1a082de3e29..32bb76b3202a0 100644
> --- a/arch/arm64/boot/dts/microchip/sparx5_pcb_common.dtsi
> +++ b/arch/arm64/boot/dts/microchip/sparx5_pcb_common.dtsi
> @@ -6,6 +6,18 @@
> /dts-v1/;
> #include "sparx5.dtsi"
>
> +&psci {
> + status = "disabled";
> +};
> +
> +&cpu0 {
> + enable-method = "spin-table";
> +};
> +
> +&cpu1 {
> + enable-method = "spin-table";
> +};
> +
> &uart0 {
> status = "okay";
> };
> --
> 2.39.2
>
BR
Steen
next prev parent reply other threads:[~2023-02-21 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 10:50 [PATCH v2 1/3] arm64: dts: microchip: sparx5: do not use PSCI on reference boards Robert Marko
2023-02-21 10:50 ` [PATCH v2 2/3] arm64: dts: microchip: sparx5: correct CPU address-cells Robert Marko
2023-05-17 12:26 ` Krzysztof Kozlowski
2023-02-21 10:50 ` [PATCH v2 3/3] arm64: dts: microchip: sparx5: add missing L1/L2 cache information Robert Marko
2023-05-17 12:26 ` Krzysztof Kozlowski
2023-02-21 13:59 ` Steen Hegelund [this message]
2023-05-17 12:25 ` [PATCH v2 1/3] arm64: dts: microchip: sparx5: do not use PSCI on reference boards Krzysztof Kozlowski
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=b90c582b8ddf0429058361ff42dc63ad1337bf43.camel@microchip.com \
--to=steen.hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).