On Thu, 2009-07-16 at 11:32 +0530, Ravi A wrote: > On Tue, Jul 14, 2009 at 6:07 AM, Andy Walls<[email protected]> wrote: > > > Hi Ravi, > > > > OK. I thought I saw in the picture Line In on Y1 and FM (from where the > > TEA5767 should be) going into Y2. Thanks for confirming. > > > > > >> The MUX select final connections are not visible when they enter the > >> BGA area. So could not check the GPIO connections. But they seem to be > >> going to the general area where GPIO14/15 (balls B12/C11) are located, > >> but that is probably not enough to confirm. > > > > Yes, I didn't expect tracing over to the BGA pins to be easy. Oh well. > > > > > >> Anyhow, I think it is not a MUX problem, because I was looking at this > >> block diagram and realized the tuner audio is a totally separate path. > >> However the tuner audio also behaves the same erratic way as Line-in > >> on the card (choppy/intermittent or totally silent). > > > > The CX25841 can only decode BTSC (basic and dbx) broodcast audio. > > Unless you have an NTSC RF source, I doubt the analog tuner assembly is > > outputing valid SIF carrying BTSC. The Audio Standard Autodetection > > microcontroller program inside the CX25841 will unmute the decoded and > > dematrixed SIF audio only when it thinks it has valid audio (it can't > > recall if it automatically mutes when good audio goes away). Without an > > NTSC RF source, I'm afraid we can't entrirely eliminate the 4:1 Mux or > > the WM8739. > > > > I'm leaning towards the CX23481 configuration or the WM8739 causing line > > in audio problems. > > > > For the WM8739 volume control, mutes, master clock mode vs slave clock > > mode are the only things I can think of right now. It's a pretty simple > > chip. > > > > For the CX25481 A/V lock of the Video and Aux PLLs might make things > > better (in my test change for the cx25840 I have registers programed > > with good values, but the AV lock bit set to disabled). And again > > programming the the I2S clock on the I2S input to be in a different > > mode. master or slave mode, might make a difference. I'll have to think > > about it. > > > > > > Can you use v4l2-dbg to dump all the CX25841 and WM8739 registers for > > the case when line-in audio is working and for the case when it is not: > > > > # su - root > > # v4l2-dbg -d /dev/video0 -c cx25840 --list-registers > > # v4l2-dbg -d /dev/video0 -c wm8739 --list-registers > > > > maybe some differential analysis will help us see where a problem could > > be. > > > >> So could it be > >> something to do with CX23416 itself? > > > > I doubt it. The I2S input of the CX23416 is so simple and > > non-configurable, it is probably something upstream from it. > > > > > > Regards, > > Andy > > > >> > >> Regards > >> Ravi > >> > > > > > > Hi Andy, > > Sorry I could not get this done yet, as the entire setup was > disassembled for the HT installation! I will do further debug today > and tomorrow and report back the results. > > PS: where do I set the CONFIG_ADV_DEBUG option when compiling? I tried > to google it but came up with just a couple of hits and no other > information.
When compiling my ivtv repository snapshot (tip.tar.bz2) or cloned tree, if you don't run 'make config', then this hsould be set in v4l/.config: CONFIG_VIDEO_ADV_DEBUG=y (If you do run 'make config' then make sure you set it.) Then 'make' and 'make install'. Look to see that the modules that we care about - wm8739, cx25840, ivtv - get compiled and installed. Then 'make unload; make unload' and 'modprobe ivtv'. Regards, Andy > Thanks > Ravi > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
