Hello, This series adds bindings and support to rcar-vin for R-Car V4M by the means of adding a Gen4 family fallback compatible. Previous versions of this series added V4M support like done for VIN since the first Gen3 device, by the use of only a single SoC specific compatible value. This was done as in Gen3 almost every new device differed from the others and a family fallback was not very useful. For the Gen4 devices with a video capture pipeline currently documented the VIN instances are very similar and a family fallback can be used. This however requires updating existing DTS files to add this new family fallback. This is done in a backward compatible way and the driver retains the compatible values. See individual patches for changes since previous versions. Niklas Söderlund (6): dt-bindings: media: renesas,vin: Add Gen4 family fallback arm64: dts: renesas: r8a779g0: Add family fallback for VIN IP arm64: dts: renesas: r8a779a0: Add family fallback for VIN IP media: rcar-vin: Add family compatible for R-Car Gen4 family dt-bindings: media: renesas,vin: Add binding for V4M arm64: dts: renesas: r8a779h0: Add family fallback for VIN IP .../bindings/media/renesas,vin.yaml | 4 + arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 96 ++++++++++++------- arch/arm64/boot/dts/renesas/r8a779g0.dtsi | 48 ++++++---- arch/arm64/boot/dts/renesas/r8a779h0.dtsi | 48 ++++++---- .../platform/renesas/rcar-vin/rcar-core.c | 21 ++-- 5 files changed, 141 insertions(+), 76 deletions(-) -- 2.45.2
