Re: [PATCH 03/16] rcar-vin: fix how pads are handled for v4l2 subdevice operations

2017-03-15 Thread Niklas Söderlund
Hi Sergei, Thanks for your feedback. On 2017-03-15 12:12:21 +0300, Sergei Shtylyov wrote: > Hello! > > On 3/14/2017 9:59 PM, Niklas Söderlund wrote: > > > The rcar-vin driver only uses one pad, pad number 0. > > > > - All v4l2 operations that did not check that the requested operation > >

Re: [PATCH 03/16] rcar-vin: fix how pads are handled for v4l2 subdevice operations

2017-03-15 Thread Sergei Shtylyov
Hello! On 3/14/2017 9:59 PM, Niklas Söderlund wrote: The rcar-vin driver only uses one pad, pad number 0. - All v4l2 operations that did not check that the requested operation was for pad 0 have been updated with a check to enforce this. - All v4l2 operations that stored (and later

[PATCH 03/16] rcar-vin: fix how pads are handled for v4l2 subdevice operations

2017-03-14 Thread Niklas Söderlund
The rcar-vin driver only uses one pad, pad number 0. - All v4l2 operations that did not check that the requested operation was for pad 0 have been updated with a check to enforce this. - All v4l2 operations that stored (and later restore) the requested pad before substituting it for the