Hello,
Now that the Gen3 documentation mentions the FCP version register, it's clear
that the SoC instance in which the FCP is integrated can be identified at
runtime without requiring SoC-specific compatible strings.
I've tested R-Car H3 ES1.x and R-Car M3 and the results match the
documentation, so it should be safe to use the generic compatible strings
only.
Laurent Pinchart (2):
dt-bindings: media: renesas-fcp: Remove SoC-specific compatible
strings
arm64: dts: r8a7795: Remove FCP SoC-specific compatible strings
.../devicetree/bindings/media/renesas,fcp.txt | 8 +-------
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 24 +++++++++++-----------
2 files changed, 13 insertions(+), 19 deletions(-)
--
Regards,
Laurent Pinchart
