On Fri, Nov 15, 2024 at 04:29:55PM +0100, Gregory CLEMENT wrote: > Some CM3.5 reports show that Hardware Cache Initialization is > complete, but in reality it's not the case. They also incorrectly > indicate that Hardware Cache Initialization is supported. This > optional property allows warning about this broken feature that cannot > be detected at runtime. > > Signed-off-by: Gregory CLEMENT <gregory.clement@xxxxxxxxxxx> > --- > Documentation/devicetree/bindings/mips/mti,mips-cm.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml b/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml > index 03a5ba5624a429c428ee2afca73b3e29127e02f9..eab31a1022c8cbdee86081110516579ebe99e640 100644 > --- a/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml > +++ b/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml > @@ -23,6 +23,12 @@ properties: > block. It is conventionally decided by the system integrator. > maxItems: 1 > > + cm3-l2-config-hci-broken: > + type: boolean > + description: > + If present, indicates that the HCI (Hardware Cache Initialization) > + information for the L2 cache in multi-cluster configuration is broken. > + This should be implied by a specific compatible. > required: > - compatible > > > -- > 2.45.2 >
