aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/media/v4l2-core/v4l2-subdev.c
diff options
context:
space:
mode:
authorYoshihiro Kaneko <[email protected]>2016-03-15 00:40:26 +0000
committerMauro Carvalho Chehab <[email protected]>2016-04-13 20:17:56 +0000
commitbd546882ff3476718d6df872c1c95aedcc5ed37d (patch)
tree42c6d64e61bca27bd278d48d358751cf6d91146f /drivers/media/v4l2-core/v4l2-subdev.c
parent[media] sh_mobile_ceu_camera: Remove dependency on SUPERH (diff)
downloadkernel-bd546882ff3476718d6df872c1c95aedcc5ed37d.tar.gz
kernel-bd546882ff3476718d6df872c1c95aedcc5ed37d.zip
[media] soc_camera: rcar_vin: add R-Car Gen 2 and 3 fallback compatibility strings
Add fallback compatibility string for R-Car Gen 1 and 2. In the case of Renesas R-Car hardware we know that there are generations of SoCs, e.g. Gen 2 and 3. But beyond that it's unclear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than r8a7791 but that doesn't imply that the latter is a descendant of the former or vice versa. We can, however, by examining the documentation and behaviour of the hardware at run-time observe that the current driver implementation appears to be compatible with the IP blocks on SoCs within a given generation. For the above reasons and convenience when enabling new SoCs a per-generation fallback compatibility string scheme being adopted for drivers for Renesas SoCs. Signed-off-by: Yoshihiro Kaneko <[email protected]> Signed-off-by: Simon Horman <[email protected]> Acked-by: Geert Uytterhoeven <[email protected]> Signed-off-by: Guennadi Liakhovetski <[email protected]> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'drivers/media/v4l2-core/v4l2-subdev.c')
0 files changed, 0 insertions, 0 deletions