Re: S3C244X/S3C64XX SoC camera host interface driver questions

2012-11-17 Thread Andrey Gusakov
Hi. Just have time to test. I apologize for delay. > I'd like to squash all the s3c-camif patches before sending upstream, > if you don't mind. And to add your Signed-off at the final patch. Ok. Squash. > I might have introduced bugs in the image effects handling, hopefully > there is none. I co

Re: S3C244X/S3C64XX SoC camera host interface driver questions

2012-11-11 Thread Andrey Gusakov
Hi. Patch v2 attached. Comments taken into account. >> I often get "VIDIOC_QUERYCAP: failed: Inappropriate ioctl for device" > This is an issue in the v4l2-ctl, it is going to be fixed by adding > VIDIOC_SUBDEV_QUERYCAP ioctl for subdevs. It has been just discussed today. > I guess you get it whe

Re: S3C244X/S3C64XX SoC camera host interface driver questions

2012-11-08 Thread Andrey Gusakov
Hi. On Thu, Nov 8, 2012 at 1:57 AM, Sylwester Nawrocki wrote: > On 11/06/2012 10:34 PM, Andrey Gusakov wrote: >> >> Hi. >> >>> Does the sensor still hang after 0x2f is written to REG_GRCOM instead ? >> >> Work! >> I'm looking at d

Re: S3C244X/S3C64XX SoC camera host interface driver questions

2012-11-06 Thread Andrey Gusakov
Hi. > Does the sensor still hang after 0x2f is written to REG_GRCOM instead ? Work! I'm looking at drivers/media/usb/gspca/m5602/m5602_ov9650.h It use significantly different init sequence. Some of settings described in Application note for ov9650, some look like magic. > Do you have CONFIG_PM_RU

Re: S3C244X/S3C64XX SoC camera host interface driver questions

2012-11-05 Thread Andrey Gusakov
Hi. Thanks all! I make it work! Have to comment out write { REG_GRCOM, 0x3f }, /* Analog BLC & regulator */ and have to enable gate clock for fimc at probe. > Hmm, in my case VER was 0x50. PID, VER = 0x96, 0x50. And this a default > value > after reset according to the datasheet, ver. 1.3. For v

Re: S3C244X/S3C64XX SoC camera host interface driver questions

2012-11-05 Thread Andrey Gusakov
Hi. >> But documentation on ov9650 is too conflicting and did not cover all >> registers used in driver. > Do you mean the OV9650 datasheet, version 1.3, from September 24, 2004 ? Yes. Also I have datasheet version 1.91 from January 28, 2005 and Application note 1.1 from 7 December 2004 All can be