On Tue, Feb 04, 2020 at 03:55:51PM -0800, Florian Fainelli wrote: > diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml > index c23c24ff7575..d7b181a44789 100644 > --- a/Documentation/devicetree/bindings/arm/cpus.yaml > +++ b/Documentation/devicetree/bindings/arm/cpus.yaml > @@ -272,6 +272,39 @@ properties: > While optional, it is the preferred way to get access to > the cpu-core power-domains. > > + secondary-boot-reg: > + $ref: '/schemas/types.yaml#/definitions/uint32' > + description: | > + Required for systems that have an "enable-method" property value of > + "brcm,bcm11351-cpu-method", "brcm,bcm23550" or "brcm,bcm-nsp-smp". > + > + This includes the following SoCs: | > + BCM11130, BCM11140, BCM11351, BCM28145, BCM28155, BCM21664, BCM23550 > + BCM58522, BCM58525, BCM58535, BCM58622, BCM58623, BCM58625, BCM88312 > + > + The secondary-boot-reg property is a u32 value that specifies the > + physical address of the register used to request the ROM holding pen > + code release a secondary CPU. The value written to the register is > + formed by encoding the target CPU id into the low bits of the > + physical start address it should jump to. > + > +if: > + # If the enable-method property contains one of those values > + properties: > + enable-method: > + contains: > + enum: > + - brcm,bcm11351-cpu-method > + - brcm,bcm23550 > + - brcm,bcm-nsp-smp > + # and if enable-method is present Those comments were purely for the explanation, but you can keep them I guess :) Regardless on whether or not you keep them, for the whole series Acked-by: Maxime Ripard <mripard@xxxxxxxxxx> Maxime
Attachment:
signature.asc
Description: PGP signature
