Hi Simon, On Tue, 15 Mar 2016, Simon Horman wrote: > Simply document new compatibility string. > As a previous patch adds a generic R-Car Gen2 compatibility string > there appears to be no need for a driver updates. > > By documenting this compat string it may be used in DTSs shipped, for > example as part of ROMs. It must be used in conjunction with the Gen2 > fallback compat string. At this time there are no known differences between > the r8a7792 IP block and that implemented by the driver for the Gen2 > fallback compat string. Thus there is no need to update the driver as the > use of the Gen2 fallback compat string will activate the correct code in > the current driver while leaving the option for r8a7792-specific driver > code to be activated in an updated driver should the need arise. > > Signed-off-by: Simon Horman <horms+renesas@xxxxxxxxxxxx> > Acked-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> Strictly speaking, I see an ack from Geert to patch 1/2, but I don't see one for this patch 2/2. Have I missed it or did Geert mean to ack the whole series and forgot to mention that? Thanks Guennadi > --- > v4 > * s/sting/string/ in changelog > * Added Ack from Geert Uytterhoeven > > v3 > * New patch > --- > Documentation/devicetree/bindings/media/rcar_vin.txt | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/media/rcar_vin.txt b/Documentation/devicetree/bindings/media/rcar_vin.txt > index 4266123888ed..6a4e61cbe011 100644 > --- a/Documentation/devicetree/bindings/media/rcar_vin.txt > +++ b/Documentation/devicetree/bindings/media/rcar_vin.txt > @@ -9,6 +9,7 @@ channel which can be either RGB, YUYV or BT656. > - "renesas,vin-r8a7795" for the R8A7795 device > - "renesas,vin-r8a7794" for the R8A7794 device > - "renesas,vin-r8a7793" for the R8A7793 device > + - "renesas,vin-r8a7792" for the R8A7792 device > - "renesas,vin-r8a7791" for the R8A7791 device > - "renesas,vin-r8a7790" for the R8A7790 device > - "renesas,vin-r8a7779" for the R8A7779 device > -- > 2.1.4 >
