From: Ondrej Zary <linux@rainbow-software.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: AverMedia Satelllite Hybrid+FM A706
Date: Thu, 20 Dec 2012 22:37:11 +0100 [thread overview]
Message-ID: <201212202237.12376.linux@rainbow-software.org> (raw)
In-Reply-To: <201212182245.50722.linux@rainbow-software.org>
Update:
GPIO 9 is CE6313 SLEEP signal
GPIO 23 is CE5039 SLEEP signal
GPIO 25 is CE6313 RESET# signal - this one needs to be set high for CE6313 to
appear on I2C bus
But there is a problem with CE5039 (zl10039) - the I2C bus breaks during its
initialization (SDA stuck low):
Here it works (communication with CE6313):
[ 921.556682] start xfer
[ 921.556684] send address
[ 921.556687] saa7133[0]: i2c data => 0x1c
[ 921.556690] saa7133[0]: i2c stat <= BUSY
[ 921.556725] saa7133[0]: i2c stat <= BUSY
[ 921.556759] saa7133[0]: i2c stat <= BUSY
[ 921.556794] saa7133[0]: i2c stat <= BUSY
[ 921.556828] saa7133[0]: i2c stat <= DONE_WRITE
[ 921.556831] saa7133[0]: i2c stat <= DONE_WRITE
[ 921.556833] write bytes
[ 921.556836] saa7133[0]: i2c data => 0x14
[ 921.556838] saa7133[0]: i2c stat <= BUSY
[ 921.556873] saa7133[0]: i2c stat <= BUSY
[ 921.556907] saa7133[0]: i2c stat <= BUSY
[ 921.556942] saa7133[0]: i2c stat <= DONE_WRITE
[ 921.556945] saa7133[0]: i2c stat <= DONE_WRITE
[ 921.556948] saa7133[0]: i2c data => 0x40
[ 921.556950] saa7133[0]: i2c stat <= BUSY
[ 921.556985] saa7133[0]: i2c stat <= BUSY
[ 921.557019] saa7133[0]: i2c stat <= BUSY
[ 921.557054] saa7133[0]: i2c stat <= DONE_WRITE
[ 921.557057] saa7133[0]: i2c stat <= DONE_WRITE
[ 921.557058] xfer done
[ 921.557060] saa7133[0]: i2c attr => STOP
[ 921.557064] saa7133[0]: i2c stat <= BUSY
[ 921.557098] saa7133[0]: i2c stat <= DONE_STOP
[ 921.557101] saa7133[0]: i2c stat <= DONE_STOP
Here starts CE5039 communication:
[ 921.564672] zl10039_read
[ 921.564677] saa7133[0]: i2c stat <= DONE_STOP
[ 921.564679] start xfer
[ 921.564681] send address
[ 921.564684] saa7133[0]: i2c data => 0xc0
[ 921.564686] saa7133[0]: i2c stat <= BUSY
[ 921.564721] saa7133[0]: i2c stat <= BUSY
[ 921.564755] saa7133[0]: i2c stat <= BUSY
[ 921.564790] saa7133[0]: i2c stat <= BUSY
And here it breaks:
[ 921.564824] saa7133[0]: i2c stat <= ARB_LOST
[ 921.564827] saa7133[0]: i2c stat <= ARB_LOST
[ 921.564829] zl10039_read: i2c read error
[ 921.564833] saa7133[0]: i2c stat <= ARB_LOST
[ 921.564834] saa7133[0]: i2c reset
[ 921.564837] saa7133[0]: i2c stat <= ARB_LOST
[ 921.564839] saa7133[0]: i2c stat => ARB_LOST
[ 921.564843] saa7133[0]: i2c stat <= ARB_LOST
[ 921.564877] saa7133[0]: i2c stat <= IDLE
[ 921.564879] saa7133[0]: i2c attr => NOP
And everything is broken now (until reloading saa7134 module):
[ 921.564882] start xfer
[ 921.564883] send address
[ 921.564886] saa7133[0]: i2c data => 0x1c
[ 921.564889] saa7133[0]: i2c stat <= BUSY
[ 921.564923] saa7133[0]: i2c stat <= BUSY
[ 921.564958] saa7133[0]: i2c stat <= BUSY
[ 921.564992] saa7133[0]: i2c stat <= BUSY
[ 921.565026] saa7133[0]: i2c stat <= BUSY
[ 921.565061] saa7133[0]: i2c stat <= BUSY
[ 921.565095] saa7133[0]: i2c stat <= BUSY
[ 921.565130] saa7133[0]: i2c stat <= BUSY
[ 921.565164] saa7133[0]: i2c stat <= BUSY
[ 921.565199] saa7133[0]: i2c stat <= BUSY
[ 921.565233] saa7133[0]: i2c stat <= BUSY
[ 921.565268] saa7133[0]: i2c stat <= BUSY
[ 921.565302] saa7133[0]: i2c stat <= BUSY
[ 921.565336] saa7133[0]: i2c stat <= BUSY
[ 921.565371] saa7133[0]: i2c stat <= BUSY
[ 921.565405] saa7133[0]: i2c stat <= BUSY
[ 921.565440] mt312_read: ret == -5
[ 921.565450] saa7133[0]/dvb: dvb_init: No zl10039 found!
--
Ondrej Zary
next prev parent reply other threads:[~2012-12-20 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 21:45 AverMedia Satelllite Hybrid+FM A706 Ondrej Zary
2012-12-20 21:37 ` Ondrej Zary [this message]
2012-12-21 22:00 ` Ondrej Zary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201212202237.12376.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).