RE: isif - debugging on dm365

2010-04-16 Thread Karicheri, Muralidharan
[mailto:lamiapost...@gmail.com] Sent: Monday, April 12, 2010 4:46 AM To: Jean-Philippe François Cc: Karicheri, Muralidharan; davinci-linux-open-source Subject: Re: isif - debugging on dm365 Hi Jean-Philippe, I finally create my patch against f5cef8f45739db4c0c1c346296922cac274c87eb in attachment

Re: isif - debugging on dm365

2010-04-12 Thread Raffaele Recalcati
Hi Jean-Philippe, I finally create my patch against f5cef8f45739db4c0c1c346296922cac274c87eb in attachment, but the problem is that isif_set_hw_if_params is not called by gstreamer. If I set in drivers/media/video/davinci/isif.c (and not in drivers/media/video/davinci/dm365_ccdc.c as I don't

Re: isif - debugging on dm365

2010-04-12 Thread Jean-Philippe François
I suppose it does not work, because isif_set_hw_if params is only called if the user applications is doing a VIDIOC_S_INPUT. based on your log, it seems gstreamer does not do that. I don't know if the driver or the application should be corrected. May be there is a command switch to gstreamer

Re: isif - debugging on dm365

2010-04-07 Thread Raffaele Recalcati
I was adding isif_cfg.y_c_swap variable, but it need a modification inside arch/arm/mach-davinci/dm365.c that I think is not the right direction. I mean, the isif platform data is not board related, but it is cpu related. I'd like to use isif_set_hw_if_params, but I'm not sure that it is really

Re: isif - debugging on dm365

2010-04-07 Thread Jean-Philippe François
Raffaele Recalcati a écrit : I was adding isif_cfg.y_c_swap variable, but it need a modification inside arch/arm/mach-davinci/dm365.c that I think is not the right direction. I mean, the isif platform data is not board related, but it is cpu related. sensor or decoder connection to the isif

Re: isif - debugging on dm365

2010-04-02 Thread Raffaele Recalcati
I ll send a patch tuesday. Today i am on holyday 2010/4/1, Karicheri, Muralidharan m-kariche...@ti.com: Raffaele, [MK] 0 means the interrupt happens right at VD pulse. 1 means after one line. You might want to check the signals received from ADV to input of VPFE to see if adv is doing what

RE: isif - debugging on dm365

2010-04-01 Thread Karicheri, Muralidharan
Raffaele, [MK] 0 means the interrupt happens right at VD pulse. 1 means after one line. You might want to check the signals received from ADV to input of VPFE to see if adv is doing what it is configured to do. My colleague has found how to make the vpfe_isr interrupt working with adv7180. He

RE: isif - debugging on dm365

2010-04-01 Thread Karicheri, Muralidharan
...@linux.davincidsp.com] On Behalf Of Karicheri, Muralidharan Sent: Thursday, April 01, 2010 2:09 PM To: Raffaele Recalcati Cc: davinci-linux-open-source Subject: RE: isif - debugging on dm365 Raffaele, [MK] 0 means the interrupt happens right at VD pulse. 1 means after one line. You might want

Re: isif - debugging on dm365

2010-03-31 Thread Raffaele Recalcati
[MK] 0 means the interrupt happens right at VD pulse. 1 means after one line. You might want to check the signals received from ADV to input of VPFE to see if adv is doing what it is configured to do. My colleague has found how to make the vpfe_isr interrupt working with adv7180. He has made

isif - debugging on dm365

2010-03-30 Thread Raffaele Recalcati
I'm trying to understand why my adv7180 (BT.656) isn't correctly grabbed. The setup is on 2.6.34 davinci git kernel and is similar to evm dm365. I have tried in many ways, also checking hw, but no vpfe_isr happens. I have checked isif registers, but I can't understand if my video is seen from isif

RE: isif - debugging on dm365

2010-03-30 Thread Karicheri, Muralidharan
Sent: Tuesday, March 30, 2010 10:51 AM To: davinci-linux-open-source Subject: isif - debugging on dm365 I'm trying to understand why my adv7180 (BT.656) isn't correctly grabbed. The setup is on 2.6.34 davinci git kernel and is similar to evm dm365. I have tried in many ways, also checking hw

Re: isif - debugging on dm365

2010-03-30 Thread Raffaele Recalcati
Hi Karicheri, there is an optional info that I think is interesting. evm-dm365 and bmx board have 128MB DDR2 RAM. but vpfe_capture.bufsize=4147200 works on evm, but in our board gives this allocation problem: (setting instead vpfe_capture.bufsize=1147200 we obtain the situation of the previous

RE: isif - debugging on dm365

2010-03-30 Thread Karicheri, Muralidharan
[mailto:lamiapost...@gmail.com] Sent: Tuesday, March 30, 2010 12:24 PM To: Karicheri, Muralidharan Cc: davinci-linux-open-source Subject: Re: isif - debugging on dm365 Hi Karicheri, there is an optional info that I think is interesting. evm-dm365 and bmx board have 128MB DDR2 RAM. but vpfe_capture.bufsize

RE: isif - debugging on dm365

2010-03-30 Thread Karicheri, Muralidharan
yes, see the logs below and the attached board file. in evm-dm365 vpfe_capture0 interrupts numbers rise during the grabbing, instead in our board it doesn't happen. VDINT0 is zero in both boards, but looking documentation seems it should contain the number of lines to be received in order to