lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Sep 2017 17:12:48 +0100 From: Mark Rutland <mark.rutland@....com> To: Daniel Thompson <daniel.thompson@...aro.org> Cc: Liviu Dudau <liviu.dudau@....com>, Sudeep Holla <sudeep.holla@....com>, Lorenzo Pieralisi <lorenzo.pieralisi@....com>, Rob Herring <robh+dt@...nel.org>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will.deacon@....com>, linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, patches@...aro.org Subject: Re: [PATCH] arm64: dts: foundation-v8: Enable PSCI mode Hi Daniel, On Mon, Sep 18, 2017 at 04:38:32PM +0100, Daniel Thompson wrote: > Currently if the Foundation model is running ARM Trusted Firmware then > the kernel, which is configured to use spin tables, cannot start secondary > processors or "power off" the simulation. > > Add a couple of labels to the include file, and introduce a new .dts > file that uses these to override the enable-method. > > Signed-off-by: Daniel Thompson <daniel.thompson@...aro.org> This looks good, but has the unfortunate effect of leaving the (irrelevant) cpu-release-addr property in the PSCI dts files, as that's in the underlying dtsi file. Could we split spin-table / PSCI parts into separate dtsi files? e.g. have: * foundation-v8.dtsi * foundation-v8-gicv{2,3}.dtsi * foundation-v8-{psci,spin-table}.dtsi ... and then combine those to build the dts files we want. FWIW, with that: Acked-by: Mark Rutland <mark.rutland@....com> Thanks, Mark.
Powered by blists - more mailing lists