[PATCH v9 1/3] PSCI: Add initial support for PSCIv0.2 functions
ashwin.chaugule at linaro.org
Mon May 12 07:02:16 PDT 2014
On 12 May 2014 05:10, Mark Rutland <mark.rutland at arm.com> wrote:
> Hi Ashwin,
> On Wed, May 07, 2014 at 03:27:25PM +0100, Ashwin Chaugule wrote:
>> The PSCIv0.2 spec defines standard values of function IDs
>> and introduces a few new functions. Detect version of PSCI
>> and appropriately select the right PSCI functions.
>> Signed-off-by: Ashwin Chaugule <ashwin.chaugule at linaro.org>
>> Reviewed-by: Rob Herring <robh at kernel.org>
> Other than those issues pointed out by Anup, this looks good to me,
> though I'd like to see the cpu_kill callbacks for arm (and arm64) go
> though at the same time (possibly folded in) so that implementations are
> exercised from the start and we don't have to add properties to later
> bodge around any current brokenness.
Yea. I'll fold it in the next revision.
> Have these patches been tested against an implementation?
Only boot tested on the ARMv8 FVP.
> Which tree are you planning on merging this through? Do we need to split
> the arm and arm64 parts?
IIRC all this PSCI work originally came via Catalins tree(?). But now,
these patches depend on a header introduced by Anups KVM patchset
which is merged in -
In a previous discussion (everyone here is CC'd) with Christoffer and
Paolo the 2nd option of the following was chosen:
1) Catalin can apply "Add common header for PSCI related defines", or
Ashwin can resend his series with the patch at the beginning.
Duplicate commits are fine, especially for seldom-modified files where
they do not cause conflicts.
2) Send Anup's patchset as a pull request to both me and Catalin,
relative to v3.16-rc1, both of us can apply it and Ashwin's series can
be commit on top.
To keep it simple it'd be better if it all goes via one tree, but if
there are objections or other suggestions, I'm happy to split this up.
More information about the linux-arm-kernel