From: Catalin Marinas <catalin.marinas@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Matheus Castello" <matheus@castello.eng.br>,
"Olof Johansson" <olof@lixom.net>,
"Andreas Färber" <afaerber@suse.de>,
"Mark Rutland" <mark.rutland@arm.com>,
"Rob Herring" <robh+dt@kernel.org>,
edgar.righi@lsitec.org.br, igor.lima@lsitec.org.br,
"Helen Koike" <helen.koike@collabora.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-actions@lists.infradead.org,
"Will Deacon" <will@kernel.org>
Subject: Re: [PATCH v7 4/4] arm64: dts: Add Caninos Loucos Labrador v3
Date: Tue, 22 Sep 2020 11:26:05 +0100 [thread overview]
Message-ID: <20200922102605.GE15643@gaia> (raw)
In-Reply-To: <CAK8P3a0yGN80nJU0kcrvYGsSjpaNpU_nmu-ENwE3GMC_9DNBhg@mail.gmail.com>
On Tue, Sep 22, 2020 at 10:32:06AM +0200, Arnd Bergmann wrote:
> On Tue, Sep 22, 2020 at 8:15 AM Manivannan Sadhasivam
> <manivannan.sadhasivam@linaro.org> wrote:
> > On Mon, Sep 21, 2020 at 11:43:02PM -0300, Matheus Castello wrote:
> > > + /* Labrador v3 firmware does not support PSCI */
> >
> > Oops. This is unfortunate... I'm not sure if this is even acceptable for
> > ARM64 machines.
> >
> > Let me add Olof and Arnd...
>
> Adding Catalin and Will for additional input as well, this is more their
> area than ours.
>
> I don't think we have formalized this as a policy, but we clearly don't
> want new boards to use the spin table hack. As there are other
> boards using psci on the same chip, I don't think this is a
> hardware bug.
I fully agree, we shouldn't allow new boards to use the spin-table
method unless EL3 is missing on the CPU implementation (not the case
here; only the APM hardware has this issue). Unfortunately we missed
another platform with A53, see commit bc66392d8258 ("arm64: dts: fsl:
Add device tree for S32V234-EVB").
The kernel relies on firmware for other things (power management, errata
workarounds), so an SMC calling convention compliant firmware is highly
recommended. I also don't see why it would be that hard to add PSCI.
Even if you don't port something like Trusted Firmware, U-Boot has basic
support for PSCI.
So from my perspective, NAK on this patch.
I'm tempted to also modify smp_spin_table_cpu_init() to print a big
warning and return an error if this is attempted on new platforms. IOW,
we make it a policy from now on.
--
Catalin
next prev parent reply other threads:[~2020-09-22 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 2:42 [PATCH v7 0/4] Add Caninos Loucos Labrador CoM and Base Board Device Tree Matheus Castello
2020-09-22 2:42 ` [PATCH v7 1/4] dt-bindings: Add vendor prefix for Caninos Loucos Matheus Castello
2020-09-22 6:25 ` Manivannan Sadhasivam
2020-09-22 8:14 ` Manivannan Sadhasivam
2020-09-22 2:43 ` [PATCH v7 2/4] dt-bindings: arm: actions: Document Caninos Loucos Labrador Matheus Castello
2020-09-22 6:27 ` Manivannan Sadhasivam
2020-09-22 2:43 ` [PATCH v7 3/4] ARM: dts: Add Caninos Loucos Labrador v2 Matheus Castello
2020-09-22 6:27 ` Manivannan Sadhasivam
2020-09-22 2:43 ` [PATCH v7 4/4] arm64: dts: Add Caninos Loucos Labrador v3 Matheus Castello
2020-09-22 6:14 ` Manivannan Sadhasivam
2020-09-22 8:32 ` Arnd Bergmann
2020-09-22 10:26 ` Catalin Marinas [this message]
2020-10-15 23:57 ` Matheus Castello
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=20200922102605.GE15643@gaia \
--to=catalin.marinas@arm.com \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=edgar.righi@lsitec.org.br \
--cc=helen.koike@collabora.com \
--cc=igor.lima@lsitec.org.br \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=matheus@castello.eng.br \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=will@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).