On Nov 17, 2009, at 1:03 AM, Robert Cicconetti wrote: > On Tue, Nov 17, 2009 at 12:55 AM, Michael Krufky <mkrufky@xxxxxxxxxxx> wrote: >>>>>>> [ 812.465930] tda18271: performing RF tracking filter calibration >>>>>>> [ 818.572446] tda18271: RF tracking filter calibration complete >>>>>>> [ 818.953946] tda18271: performing RF tracking filter calibration >>>>>>> [ 825.093211] tda18271: RF tracking filter calibration complete >> >> >> If you see this happen more than once consecutively, and there is only 1 >> silicon tuner present, then it means something very bad is happening, and >> there is a chance of burning out a part. I still wouldnt not recommend any >> mainline merge until you can prevent this behavior -- I suspect that a GPIO >> reset is being toggled where it shouldnt be, which should be harmless ... >> but until we fix it, we cant be sure what damage might get done... >> >> The RF tracking filter calibration is a procedure that should only happen >> once while the tuner is powered on -- it should *only* be repeated if the >> tuner indicated that calibration is necessary, and that would only happen >> after a hardware reset. >> >> This still looks fishy to me... Agreed. I did manage to dig into this some more last night, something is definitely still awry. Here's a dmesg dump with some extra debug spew added in key spots: ... em28xx driver loaded tda18271 4-0060: creating new instance TDA18271HD/C2 detected @ 4-0060 tda18271: R_EP1 is 0xce cal is not initialized (cal_initialized=false)... tda18271: performing RF tracking filter calibration tda18271: RF tracking filter calibration complete (0xde) DVB: registering new adapter (em28xx #0) DVB: registering adapter 0 frontend 0 (LG Electronics LGDT3304 VSB/QAM Frontend)... em28xx #0: Successfully loaded em28xx-dvb Em28xx: Initialized (Em28xx dvb Extension) extension 1st tuning attempt tda18271: R_EP1 is 0x00 cal is not initialized (cal_initialized=true)... tda18271: performing RF tracking filter calibration tda18271: RF tracking filter calibration complete (0x00) tda18271: R_EP1 is 0x00 cal is not initialized (cal_initialized=true)... tda18271: performing RF tracking filter calibration tda18271: RF tracking filter calibration complete (0x00) 2nd tuning attempt tda18271: R_EP1 is 0x00 cal is not initialized (cal_initialized=true)... tda18271: performing RF tracking filter calibration tda18271: RF tracking filter calibration complete (0x00) tda18271: R_EP1 is 0x00 cal is not initialized (cal_initialized=true)... tda18271: performing RF tracking filter calibration tda18271: RF tracking filter calibration complete (0x00) I'll try tweaking the GPIO reset mask and whatnot, definitely does seem like something's getting reset that shouldn't, because you can clearly see that cal *was* initialized, then R_EP1 got zeroed out. > It happened at every tuning operation, and made mythfrontend unhappy > (unable to tune after the first channel). I disabled the check for > RF_CAL_OK which triggered the recalibration, and mythfrontend worked. Yeah, tuning is much quicker here if I skip that check as well, but its definitely not the proper fix. > The stick has been plugged in for a few months, so presumably would've > caught on fire by now if it was going to. It would be nice if the > tuning delay went away, though.. it still takes ~6 seconds to switch > frequencies. Wait, it still takes that long with the check gone? I didn't poke for very long with the check disabled, mostly focusing on trying to figure out why things are going haywire. > I have not yet compiled and tested the lastest patches from Jarod. Really shouldn't be any difference from what you've got, they're just rebased to the latest v4l-dvb tree. -- Jarod Wilson jarod@xxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
