Hi Geert,
> >>
> >> Please keep the list sorted by SoC part number.
> >
> > It is sorted, just in descending order. Do you want me to re-order the full
> > list in ascending order?
>
> That may be a good idea, given the current order is non-standard and
> counter-intuitive.
sure, dropping this
Hi Fabrizio,
On Thu, Nov 16, 2017 at 2:45 PM, Fabrizio Castro
<fabrizio.cas...@bp.renesas.com> wrote:
>> Subject: Re: [PATCH 1/2] dt-bindings: media: rcar_vin: add device tree
>> support for r8a774[35]
>>
>> On Thu, Nov 16, 2017 at 1:11 PM, Fabrizio Castro
>
Hello Geert,
thank you for your comment!
> Subject: Re: [PATCH 1/2] dt-bindings: media: rcar_vin: add device tree
> support for r8a774[35]
>
> On Thu, Nov 16, 2017 at 1:11 PM, Fabrizio Castro
> <fabrizio.cas...@bp.renesas.com> wrote:
> > --- a/Documentatio
Hello Geert,
thank you for your comment!
> > Add compatible strings for r8a7743 and r8a7745. No driver change
> > change is needed as "renesas,rcar-gen2-vin" will activate the right
>
> double "change"
ps, do you think a v2 is in order?
Thanks,
Fab
Renesas Electronics Europe Ltd, Dukes
On Thu, Nov 16, 2017 at 1:11 PM, Fabrizio Castro
wrote:
> --- a/Documentation/devicetree/bindings/media/rcar_vin.txt
> +++ b/Documentation/devicetree/bindings/media/rcar_vin.txt
> @@ -14,7 +14,10 @@ channel which can be either RGB, YUYV or BT656.
> -
On Thu, Nov 16, 2017 at 1:11 PM, Fabrizio Castro
wrote:
> Add compatible strings for r8a7743 and r8a7745. No driver change
> change is needed as "renesas,rcar-gen2-vin" will activate the right
double "change"
> code. However, it is good practice to document
Add compatible strings for r8a7743 and r8a7745. No driver change
change is needed as "renesas,rcar-gen2-vin" will activate the right
code. However, it is good practice to document compatible strings
for the specific SoC as this allows SoC specific changes to the
driver if needed, in addition to