Re: [PATCH 3/6] media: rcar-vin: Handle data-active property

2018-05-17 Thread Sergei Shtylyov
Hello! On 5/16/2018 7:32 PM, Jacopo Mondi wrote: The data-active property has to be specified when running with embedded Prop names are typically enclosed in "". synchronization. The VIN peripheral can use HSYNC in place of CLOCKENB CLKENB, maybe? when the CLOCKENB pin is not conn

Re: [PATCH 3/6] media: rcar-vin: Handle data-active property

2018-05-17 Thread jacopo mondi
Hi Niklas, On Wed, May 16, 2018 at 11:58:47PM +0200, Niklas Söderlund wrote: > Hi Jacopo, > > Thanks for your work. > > On 2018-05-16 18:32:29 +0200, Jacopo Mondi wrote: > > The data-active property has to be specified when running with embedded > > synchronization. The VIN peripheral can use HSYN

Re: [PATCH 3/6] media: rcar-vin: Handle data-active property

2018-05-16 Thread Niklas Söderlund
Hi Jacopo, Thanks for your work. On 2018-05-16 18:32:29 +0200, Jacopo Mondi wrote: > The data-active property has to be specified when running with embedded > synchronization. The VIN peripheral can use HSYNC in place of CLOCKENB > when the CLOCKENB pin is not connected, this requires explicit >

[PATCH 3/6] media: rcar-vin: Handle data-active property

2018-05-16 Thread Jacopo Mondi
The data-active property has to be specified when running with embedded synchronization. The VIN peripheral can use HSYNC in place of CLOCKENB when the CLOCKENB pin is not connected, this requires explicit synchronization to be in use. Now that the driver supports 'data-active' property, it makes