On Mon, Oct 28, 2024 at 06:59:32PM +0100, Aleksandar Rikalo wrote: > From: Gregory CLEMENT <gregory.clement@xxxxxxxxxxx> > > 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> > Signed-off-by: Aleksandar Rikalo <arikalo@xxxxxxxxx> > Tested-by: Gregory CLEMENT <gregory.clement@xxxxxxxxxxx> > --- > Documentation/devicetree/bindings/mips/cpus.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > I cannot find this patch in v6, nothing in changelog explaining what happened here. > diff --git a/Documentation/devicetree/bindings/mips/cpus.yaml b/Documentation/devicetree/bindings/mips/cpus.yaml > index a85137add668..57e93c07ab1b 100644 > --- a/Documentation/devicetree/bindings/mips/cpus.yaml > +++ b/Documentation/devicetree/bindings/mips/cpus.yaml > @@ -47,6 +47,12 @@ properties: > clocks: > maxItems: 1 > > + cm3-l2-config-hci-broken: Are these names - cm3, l2, hci - obvious and known in MIPS? HCI usually means something else - see drivers/bluetooth/ and drivers/nfc/ Is this property applicable for all MIPS vendors? There is no vendor prefix here, so this is generic for this architecture, right? Best regards, Krzysztof
