On Thu, Oct 24, 2024 at 02:05:29PM -0300, Cody Eksal wrote: > The A100, similar to the H6 and H616, use an NVMEM value to determine > speed binnings. The method used is similar to that of the H6. However, > the information is stored at a slightly different bit offset. > > Add a new compatible for the A100. > > Signed-off-by: Cody Eksal <masterr3c0rd@epochal.quest> > --- > .../bindings/opp/allwinner,sun50i-h6-operating-points.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/opp/allwinner,sun50i-h6-operating-points.yaml b/Documentation/devicetree/bindings/opp/allwinner,sun50i-h6-operating-points.yaml > index ec5e424bb3c8..603c6c88d080 100644 > --- a/Documentation/devicetree/bindings/opp/allwinner,sun50i-h6-operating-points.yaml > +++ b/Documentation/devicetree/bindings/opp/allwinner,sun50i-h6-operating-points.yaml > @@ -23,6 +23,7 @@ properties: > compatible: > enum: > - allwinner,sun50i-h6-operating-points > + - allwinner,sun50i-a100-operating-points > - allwinner,sun50i-h616-operating-points I have no clue why a100 is between h6 and h616. :/ Best regards, Krzysztof
