All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-media@vger.kernel.org
Subject: Re: cx5000 default auto sleep mode
Date: Mon, 10 May 2010 18:45:29 -0700	[thread overview]
Message-ID: <4BE8B6B9.1070605@vorgon.com> (raw)
In-Reply-To: <h2h829197381004142139q35705f60q61dd04b05f509af6@mail.gmail.com>



On 4/14/2010 9:39 PM, Devin Heitmueller wrote:
> On Wed, Apr 14, 2010 at 11:44 PM, Andy Walls<awalls@md.metrocast.net>  wrote:
>> On Wed, 2010-04-14 at 13:40 -0400, Devin Heitmueller wrote:
>>> On Wed, Apr 14, 2010 at 1:29 PM, Timothy D. Lenz<tlenz@vorgon.com>  wrote:
>>>> Thanks to Andy Walls, found out why I kept loosing 1 tuner on a FusionHD7
>>>> Dual express. Didn't know linux supported an auto sleep mode on the tuner
>>>> chips and that it defaulted to on. Seems like it would be better to default
>>>> to off.
>>>
>>> Regarding the general assertion that the power management should be
>>> disabled by default, I disagree.  The power savings is considerable,
>>> the time to bring the tuner out of sleep is negligible, and it's
>>> generally good policy.
>>>
>>> Andy, do you have any actual details regarding the nature of the problem?
>>
>> Not really.  DViCo Fusion dual digital tv card.  One side of the card
>> would yield "black video screen" when starting a digital capture
>> sometime after (?) the VDR ATSC EPG plugin tried to suck off data.  I'm
>> not sure there was a causal relationship.
>>
>> I hypothesized that one side of the dual-tuner was going stupid or one
>> of the two channels used in the cx23885 was getting confused.  I was
>> looking at how to narrow the problem down to cx23885 chip or xc5000
>> tuner, or s5h14xx demod when I noted the power managment module option
>> for the xc5000.  I suggested Tim try it.
>>
>> It was dumb luck that my guess actually made his symptoms go away.
>>
>> That's all I know.
>
> We did have a similar issue with the PCTV 800i.  Basically, the GPIO
> definition was improperly defined for the xc5000 reset callback.  As a
> result, it was strobing the reset on both the xc5000 *and* the
> s5h1411, which would then cause the s5h1411's hardware state to not
> match the driver state.
>
> After multiple round trips with the hardware engineer at PCTV, I
> finally concluded that there actually wasn't a way to strobe the reset
> without screwing up the demodulator, which prompted me to disable the
> xc5000 reset callback (see cx88-cards:2944).
>
> My guess is that the reset GPIO definition for that board is wrong (a
> problem exposed by this change), or that it's resetting the s5h1411 as
> well.
>
> Devin
>


I replaced the single tuner with the other FusionHD7 Dual Express I had 
so there was two of the same cards. Within a few hours Both tuners where 
down on the original card and even restarting drivers wouldn't bring it 
back. So I moved the new card to it's slot and put the single back in in 
case the old card was defective. I removed the no power off switch and 
went out for awhile. When I came back vdr had crashed which often 
happens when it tried to tune and there is no signal as in when a tuner 
goes down. For some reason vdr/xine/xorg/vdpau combo is very unstable 
when signal is poor or missing. I wish we could dump xine as it seems to 
be the cause. I never had a problem with vdr crashing when it rained 
knocking out signal when the nexus card was providing video.

  parent reply	other threads:[~2010-05-11  1:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 17:29 cx5000 default auto sleep mode Timothy D. Lenz
2010-04-14 17:40 ` Devin Heitmueller
2010-04-15  3:44   ` Andy Walls
2010-04-15  4:39     ` Devin Heitmueller
2010-04-21 22:26       ` Timothy D. Lenz
2010-05-11  1:45       ` Timothy D. Lenz [this message]
2010-09-27 18:37         ` Timothy D. Lenz
2010-06-20 21:04       ` Timothy D. Lenz
2010-04-18 19:19     ` Timothy D. Lenz
2010-04-20  0:14   ` Timothy D. Lenz
2010-04-20 17:17   ` Timothy D. Lenz
2010-04-21  2:10   ` Timothy D. Lenz

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=4BE8B6B9.1070605@vorgon.com \
    --to=tlenz@vorgon.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.