On 3/2/22 3:10 PM, Paul Kocialkowski wrote: > Since the V3s uses the internal mbus for DMA with multimedia devices, > document its compatible in accordance with the extended mbus binding. > > This will enable adding support for the V3s in the full-fledged > devfreq driver eventually. > > Signed-off-by: Paul Kocialkowski <paul.kocialkowski@xxxxxxxxxxx> > --- > .../devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml b/Documentation/devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml > index 8eee312c2e6f..e7f3f798491a 100644 > --- a/Documentation/devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml > +++ b/Documentation/devicetree/bindings/arm/sunxi/allwinner,sun4i-a10-mbus.yaml > @@ -31,6 +31,7 @@ properties: > - allwinner,sun5i-a13-mbus > - allwinner,sun8i-h3-mbus > - allwinner,sun8i-r40-mbus > + - allwinner,sun8i-v3s-mbus > - allwinner,sun50i-a64-mbus > - allwinner,sun50i-h5-mbus > > @@ -88,6 +89,7 @@ if: > - allwinner,sun8i-h3-mbus > - allwinner,sun50i-a64-mbus > - allwinner,sun50i-h5-mbus > + - allwinner,sun8i-v3s-mbus This should be sorted, though it can be fixed when applying the patch. With that: Reviewed-by: Samuel Holland <samuel@xxxxxxxxxxxx> > > then: > properties: >