hi all, Im working with the adv7180(freescale version) on kernel 3.0.35, Im loosing vertical synchro. when switching adv's input which are both PAL camera sources, I already tried fast switch script from https://ez.analog.com/docs/DOC-2643 but I still have the issue, anyone have faced this before ? kbo: o: too bad you didnt stick around oh, you did.. are you using the parallel or CSI version? dongs: Im uising parralel csi version (8bit) :) no, you're using just parallel. 7180M is csi, and has no parallel dongs: yes it's the parralel 8/16 bit version dongs: Im still trying to get the fast script work but without success ... whats "wrong" with the script? you know what it does right? just i2c writes it seems its also doing a bunch of redundant writes unless subaddress 0E is liek for reset or something dongs: Yes, are facing the same issue ? you* I have some 7180M's here that I need to finish making pcb for and try out, but I have a feeling I wont be able to use them properly wiht rageberry since their CSI drivers are closedsores no i mean, tell me waht the problem is? the script looks ok, did you rewrite it as array of i2c writes or something? dongs: Yes I first tried with i2c-tools from userspace then I tried replacing the adv's init from kernel driver but still getting scrolling video at screen my two input camera's are PAL did you read hte pdf? it says using fast switching disables hsync pll and some extra checks for "not compliant" signals is it possible that your input is just shitty enough that it confused the chip? er pdf = ppt https://ez.analog.com/servlet/JiveServlet/download/67024-12431/ADV7180_Fast_switching.pdf this ? ya that Using the fast switching script disables blocks that provide robustness for non-standard signals but allow very fast acquisition to nominal signals i presume it works without fast switch? robustness ? means, blocks that can help lockign even on shitty signal did you configure it properly for pal? :) I would say yes because the video is good at screen 56 80 10 ; SSAF Luma filter enabled, NTSC mode what is this? check register manual for that subaddress and make sure youre not turning on NTSC after configuring it for pal properly I don't have any device at this i2c address im pasting from the script. those are subaddress under the main 7180 address. but looks liek 2 lines below it enables automatic pal/ntcs anyway maybe try forcing that to pal instead ot autodetect? is tehre a register you can read to see if its in pal or ntsc mode? ^ these would be things I'd be trying yes 0x10 it says 0x47 (PAL B/G/H..;) this is with fast mode and video scrolling badly on screen? yep 42 37 81 ; HS polarity how does this compare with normal init script? (the one in driver) 0x37 = 0x01 well then tehere's maybe your problem set it to 01 in the fast one as well. if you have wrong sync polarity, whatever is getting parallel data will be confused. I set it in the fast script and runned it from user shell script but nothing changed well, i donno. keep playing with it and comparing what works this is clearly not lunix stuff try using slow switch, and change hsync polarity to opposite, does it make screen go bad? etc. experiment. dongs: it's seems that I made a mistake when switching input I was using PAL B/G/H/I for both input but In fact one of my two input is a secam well then who the hell even uses that stuff anymore? :) dongs: :) i can't say you that...