Hello.
On 08/25/2015 05:25 PM, Hans Verkuil wrote:
rcar_vin_set_fmt() defaults to PAL when the subdevice's querystd() method call
fails (e.g. due to I2C error). This doesn't work very well when a camera being
used outputs NTSC which has different order of fields and resolution. Let us
stop
Hi Sergei,
On Tuesday 25 August 2015 00:58:07 Sergei Shtylyov wrote:
> On 08/21/2015 12:51 AM, Laurent Pinchart wrote:
> >> rcar_vin_set_fmt() defaults to PAL when the subdevice's querystd()
> >> method call fails (e.g. due to I2C error). This doesn't work very well
> >> when a camera being used
On 08/19/15 23:02, Sergei Shtylyov wrote:
> rcar_vin_set_fmt() defaults to PAL when the subdevice's querystd() method
> call
> fails (e.g. due to I2C error). This doesn't work very well when a camera
> being
> used outputs NTSC which has different order of fields and resolution. Let
> us
>
hello.
On 08/21/2015 12:51 AM, Laurent Pinchart wrote:
rcar_vin_set_fmt() defaults to PAL when the subdevice's querystd() method
call fails (e.g. due to I2C error). This doesn't work very well when a
camera being used outputs NTSC which has different order of fields and
resolution. Let us
Hi Sergei,
Thank you for the patch.
On Thursday 20 August 2015 00:02:17 Sergei Shtylyov wrote:
> rcar_vin_set_fmt() defaults to PAL when the subdevice's querystd() method
> call fails (e.g. due to I2C error). This doesn't work very well when a
> camera being used outputs NTSC which has differe
rcar_vin_set_fmt() defaults to PAL when the subdevice's querystd() method call
fails (e.g. due to I2C error). This doesn't work very well when a camera being
used outputs NTSC which has different order of fields and resolution. Let us
stop pretending and return the actual error (which would p
