From: David Liontooth <lionteeth@cogweb.net>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: hermann pitton <hermann-pitton@arcor.de>, linux-media@vger.kernel.org
Subject: Re: Audio drop on saa7134
Date: Mon, 21 Sep 2009 00:40:00 -0700 [thread overview]
Message-ID: <4AB72DD0.70205@cogweb.net> (raw)
In-Reply-To: <20090920060218.51971a45@pedra.chehab.org>
Mauro Carvalho Chehab wrote:
> Em Sun, 20 Sep 2009 01:24:12 -0700
> David Liontooth <lionteeth@cogweb.net> escreveu:
>
>
>> Sep 18 07:00:01 prato kernel: saa7133[4]/audio: dsp write reg 0x464 = 0x000000
>> Sep 18 07:00:01 prato kernel: saa7133[4]/audio: dsp write reg 0x46c = 0xbbbbbb
>>
>
> This means mute. With this, audio will stop.
>
>
>> Sep 18 07:00:01 prato kernel: saa7133[4]/audio: dsp write reg 0x464 = 0x000000
>> Sep 18 07:00:01 prato kernel: saa7133[4]/audio: dsp write reg 0x46c = 0xbbbb10
>>
>
> This means unmute.
>
> It seems that the auto-mute code is doing some bad things for you. What happens
> if you disable automute? This is a control that you can access via v4l2ctl or
> on your userspace application.
>
Ah, great -- I added "v4lctl -c /dev/video$DEV setattr automute off" to
the script and verified it works.
Is there a way to turn off the automute on module insertion?
I don't see a lot of difference -- during the initialization, audio is
still turned off several times, and then left on:
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: tvaudio thread scan
start [8]
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: scanning: M
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x454 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x454 =
0x0000c0
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x470 =
0x101010
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: tvaudio thread scan
start [9]
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: scanning: M
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x454 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x454 =
0x0000c0
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x470 =
0x101010
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbb10
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:25:19 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbb10
Sep 21 00:25:22 prato kernel: saa7133[4]/audio: tvaudio thread status:
0x100003 [M (in progress)]
Sep 21 00:25:22 prato kernel: saa7133[4]/audio: detailed status:
############# init done
And then audio is turned off again at the end of the recording:
Sep 21 00:35:15 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:35:15 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
Sep 21 00:35:15 prato kernel: saa7133[4]/audio: dsp write reg 0x464 =
0x000000
Sep 21 00:35:15 prato kernel: saa7133[4]/audio: dsp write reg 0x46c =
0xbbbbbb
I'll run with audiomute off for a while and see if it makes a difference
for the audio drops -- it seems a plausible cause.
> Are you using the last version of the driver? I'm not seeing some debug log messages
> that should be there...
>
I'm still running 2.6.19.1 and 2.6.20.11 on these production machines --
if it works, don't fix it. If there's a clear reason to upgrade, of
course I'll do that.
It would be a huge relief to discover the audio drops is a driver issue
that can be fixed with a simple setting.
Cheers,
Dave
next prev parent reply other threads:[~2009-09-21 7:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 2:41 Reliable work-horse capture device? David Liontooth
2009-09-15 3:08 ` Mauro Carvalho Chehab
2009-09-15 4:02 ` David Liontooth
2009-09-15 4:21 ` hermann pitton
2009-09-15 5:16 ` Audio drop on saa7134 David Liontooth
2009-09-15 5:36 ` hermann pitton
2009-09-15 6:07 ` David Liontooth
2009-09-20 8:24 ` David Liontooth
2009-09-20 9:02 ` Mauro Carvalho Chehab
2009-09-21 1:30 ` hermann pitton
2009-09-21 7:53 ` David Liontooth
2009-09-23 0:42 ` hermann pitton
2009-09-21 7:40 ` David Liontooth [this message]
2009-09-15 4:34 ` Reliable work-horse capture device? Mauro Carvalho Chehab
2009-09-15 5:03 ` David Liontooth
2009-09-15 10:39 ` Andy Walls
2009-09-15 14:48 ` David Liontooth
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=4AB72DD0.70205@cogweb.net \
--to=lionteeth@cogweb.net \
--cc=hermann-pitton@arcor.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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