On Wed, 2010-02-10 at 15:29 -0500, Andy Walls wrote: > On Tue, 2010-02-09 at 10:25 -0500, Devin Heitmueller wrote: > > > > Are we sure the zl10353 is being reset at all? > > Devin, > > I know for a fact it is not. > > > > I've seen cases before > > where the zl10353 can hang the entire i2c bus ( in particular with the > > i2c_gate_ctrl issue), and the only path to recovery is strobing the > > chip reset. It's possible that the GPIO for resetting the zl10353 is > > just *wrong* because somebody copied it from some other board profile, > > and the chip is never being reset. > > I have no information of the GPIO line that would be used to reset the > ZL10353. We can narrow the field with some differential analysis. > > Patrick, > > For every LeadTek 3100 H you have, could you, as root, run > > # v4l2-dbg -d /dev/videoN -c host0 -g 0x2c72010 > ioctl: VIDIOC_DBG_G_REGISTER > Register 0x02c72010 = 96ff13h (9895699d 00000000 10010110 11111111 00010011b) > > And record the register value and whether or not the card initialized > DVB properly or had the error. Patrick, Bah, what was I thinking? You can only record the GPIO levels of cards that initialize properly with that command. Of all the working cards, all the GPIO "1" bits that line up between all the cards are the likely candidates for the ZL10353 reset line. Regards, Andy > It would be better to log out the contents of this register immediately > after the zl10353_attach fails in cx18-dvb.c, but we'll hopefully get > close enough without doing that. > > Regards, > Andy > -- 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
