Mauro Carvalho Chehab wrote:
Em Sun, 20 Sep 2009 01:24:12 -0700
David Liontooth <lionteeth@xxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
