Hello guys,
I am sorry to bother you, just wondering if this patch has any chance to end
up in v4.16?
Thanks,
Fabrizio
> Subject: [PATCH v2 2/4] dt-bindings: media: rcar_vin: add device tree support
> for r8a774[35]
>
> Add compatible strings for r8a7743 and r8a7745. No d
Hello Mauro,
does this patch look ok to you?
Thanks,
Fab
> Subject: [PATCH v2 2/4] dt-bindings: media: rcar_vin: add device tree support
> for r8a774[35]
>
> Add compatible strings for r8a7743 and r8a7745. No driver change
> is needed as "renesas,rcar-gen2-vin" wil
On 2017-11-16 18:22:49 +, Fabrizio Castro wrote:
> Add compatible strings for r8a7743 and r8a7745. No driver 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
On Thu, Nov 16, 2017 at 7:22 PM, Fabrizio Castro
wrote:
> Add compatible strings for r8a7743 and r8a7745. No driver change
> is needed as "renesas,rcar-gen2-vin" will activate the right code.
> However, it is good practice to document compatible strings for the
>
On Thu, Nov 16, 2017 at 06:22:49PM +, Fabrizio Castro wrote:
> Add compatible strings for r8a7743 and r8a7745. No driver 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
On Thu, Nov 16, 2017 at 06:22:49PM +, Fabrizio Castro wrote:
> Add compatible strings for r8a7743 and r8a7745. No driver 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
Add compatible strings for r8a7743 and r8a7745. No driver 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 document