mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Steven Toth <stoth@linuxtv.org>,
	linux-media@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Regression 2.6.31: xc5000 no longer works with Myth-0.21-fixes  branch
Date: Sun, 19 Jul 2009 22:32:10 -0400	[thread overview]
Message-ID: <829197380907191932p56391dedj660d2bfc941a53a8@mail.gmail.com> (raw)
In-Reply-To: <4A63D407.6090109@rtr.ca>

On Sun, Jul 19, 2009 at 10:18 PM, Mark Lord<lkml@rtr.ca> wrote:
> Devin Heitmueller wrote:
>>
>> Yeah, the situation with the seven second firmware load time is well
>> known.  It's actually a result of the i2c's implementation in the
>> au0828 hardware not properly supporting i2c clock stretching.  Because
>> of some bugs in the hardware, I have it clocked down to something like
>> 30KHz as a workaround.  I spent about a week investigating the i2c bus
>> issue with my logic analyzer, and had to move on to other things.  I
>> documented the gory details here back in March if you really care:
>
> ..
>
> From your livejournal comments, it sounded like the slow clock might
> not be necessary until *after* the firmware transfer.
>
> Mmm.. I wonder if perhaps a higher clock speed could be used
> during the firmware download, and then switch to the slower 30KHz
> speed afterward ?
>
> This could reduce the firmware transfer to a couple of seconds,
> much better than the current 6-7 second pause.

I did experiment with introducing a tuner callback to inform the
bridge to enter a high speed mode, which in theory would have allowed
the firmware load at 250Khz (and then revert to the slower speed after
the load finished).  However, for some unknown reason the tuner would
not work after the load.  I would see i2c errors on the bus when doing
the tune, and I was not able to identify the cause.

I spent a couple of nights playing with the idea, but didn't have more
time to spend on it.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

      reply	other threads:[~2009-07-20  2:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 13:15 Mark Lord
2009-07-19 14:06 ` Devin Heitmueller
2009-07-19 14:45   ` Mark Lord
2009-07-19 18:25     ` Mark Lord
2009-07-19 15:12   ` Mark Lord
2009-07-19 15:53     ` Mark Lord
2009-07-19 22:42       ` Mark Lord
2009-07-20  1:12         ` Devin Heitmueller
2009-07-20  1:57           ` Mark Lord
2009-07-20  1:59             ` Devin Heitmueller
2009-07-21  2:38               ` Mark Lord
2009-07-20  2:18           ` Mark Lord
2009-07-20  2:32             ` Devin Heitmueller [this message]

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=829197380907191932p56391dedj660d2bfc941a53a8@mail.gmail.com \
    --to=dheitmueller@kernellabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=stoth@linuxtv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®