Hi Antoine, On Thu, 3 Apr 2014 01:54:07 -0700 Antoine Ténart <antoine.tenart@xxxxxxxxxxxxxxxxxx> wrote: > Jisheng, > > On 03/04/2014 10:22, Jisheng Zhang wrote: > > Hi, > > > > On Thu, 3 Apr 2014 01:08:15 -0700 > > Antoine Ténart <antoine.tenart@xxxxxxxxxxxxxxxxxx> wrote: > > > >> Signed-off-by: Antoine Ténart <antoine.tenart@xxxxxxxxxxxxxxxxxx> > >> --- > >> Documentation/devicetree/bindings/arm/cpus.txt | 2 ++ > >> 1 file changed, 2 insertions(+) > >> > >> diff --git a/Documentation/devicetree/bindings/arm/cpus.txt > >> b/Documentation/devicetree/bindings/arm/cpus.txt index > >> 333f4aea3029..a9e42a2dbc99 100644 --- > >> a/Documentation/devicetree/bindings/arm/cpus.txt +++ > >> b/Documentation/devicetree/bindings/arm/cpus.txt @@ -185,6 +185,8 @@ > >> nodes to be present and contain the properties described below. > >> "qcom,gcc-msm8660" "qcom,kpss-acc-v1" > >> "qcom,kpss-acc-v2" > >> + "marvell,88de31-smp" - cpu-core handling for > > > > why not "marvell,berlin-smp"? > > We have SMP on the BG2 and the BG2Q currently. Future boards may not be > compatible with this method (BG3 ?), I think "marvell,berlin-smp" is too Yes. It's not compatible. But it will be PSCI. FWICT, current smp method would be only used for BG2/BG2CT. Thanks -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
