Robin Murphy writes: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > On 2020-05-15 16:09, Lars Povlsen wrote: > [...] >>>> + cpu0: cpu@0 { >>>> + compatible = "arm,cortex-a53", "arm,armv8"; > > Side note: only one compatible string for the real CPU please, running a > DT bindings check should complain about that. > I'll change this. >>>> + device_type = "cpu"; >>>> + reg = <0x0 0x0>; >>>> + enable-method = "spin-table"; >>> >>> Really? This is 2020, not 2012 any more. Surely a new platform >>> boots using PSCI, and not *this*. >>> >> >> We don't currently support PSCI. The platform does not have TrustZone, >> hence we don't use ATF. > AIUI, part of the purpose of ATF is to provide a nice standardised > platform interface regardless of whether you care about Secure software > or not. It shouldn't take much to knock up a trivial ATF port that just > uses an internal spin-table for its PSCI backend - in fact I suspect > that's probably just a copy-paste from the RPi3 port ;) > I'll change this to PSCI if that's whats expected these days. We actually already have an ATF port. I fully understand the desire to standardize on PSCI. > Robin. -- Lars Povlsen, Microchip