From: Mark Zimmerman <markzimm@frii.com>
To: linux-media@vger.kernel.org
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: DViCO FusionHDTV7 Dual Express I2C write failed
Date: Tue, 25 Jan 2011 07:27:12 -0700 [thread overview]
Message-ID: <20110125142712.GA20868@io.frii.com> (raw)
In-Reply-To: <AANLkTi=UecZQ1pzz+DGbcNKdY6qM3TZJ0+7xKSeXebsL@mail.gmail.com>
On Mon, Jan 24, 2011 at 10:57:02AM -0500, Devin Heitmueller wrote:
> On Mon, Jan 24, 2011 at 10:49 AM, Mark Zimmerman <markzimm@frii.com> wrote:
> > From looking at the code and a dump of the firmware file, the first
> > i2c write would have a length of 3; so this error:
> >
> > xc5000: I2C write failed (len=3)
> >
> > tells me that there were probably no successful i2c transactions on
> > this device. The i2c write call looks the same as that in other
> > drivers, so I wonder if there is an initialization step that is now
> > necessary but which is missing.
> >
> > Still hoping for suggestions...
>
> My guess would be that somebody screwed up either the GPIO config int
> the cx88 board profile, or the i2c gate, which is resulting in not
> being able to reach the tuner at all.
>
> Do you have an oscilloscope? If so, I bet you will find that the
> xc5000 pin is being held in reset.
If I had an oscilloscope I probably wouldn't know where to stick the
probe.
>
> I would probably take a hard look at the board profile in cx88-cards.c
> as well as whether there have been any changes to the GPIO setup and
> power management code.
cx23885-cards.c, actually. I'll see what I can find in there.
Thanks,
-- Mark
next prev parent reply other threads:[~2011-01-25 14:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101207190753.GA21666@io.frii.com>
2011-01-10 2:14 ` DViCO FusionHDTV7 Dual Express I2C write failed Mark Zimmerman
2011-01-19 15:59 ` VDR User
2011-01-19 16:13 ` Devin Heitmueller
2011-01-19 17:22 ` VDR User
2011-01-19 17:39 ` Mark Zimmerman
2011-01-24 15:49 ` Mark Zimmerman
2011-01-24 15:57 ` Devin Heitmueller
2011-01-25 14:27 ` Mark Zimmerman [this message]
2011-01-19 19:01 ` Timothy D. Lenz
2011-01-17 23:12 ` Timothy D. Lenz
2011-02-12 15:29 ` [get-bisect results]: " Mark Zimmerman
2011-02-12 16:27 ` Andy Walls
2011-02-12 16:36 ` Mark Zimmerman
2011-02-12 16:46 ` Andy Walls
2011-02-12 17:03 ` Mark Zimmerman
2011-02-12 19:05 ` Mark Zimmerman
2011-02-12 20:48 ` Andy Walls
2011-02-13 14:47 ` [corrected get-bisect " Mark Zimmerman
2011-02-13 14:52 ` Devin Heitmueller
2011-02-13 20:26 ` Mark Zimmerman
2011-02-13 21:26 ` Andy Walls
2011-02-14 0:16 ` Andy Walls
2011-02-14 14:29 ` Devin Heitmueller
2011-02-14 0:37 ` Mark Zimmerman
2011-02-14 8:05 ` Jean Delvare
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=20110125142712.GA20868@io.frii.com \
--to=markzimm@frii.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.