All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Antti Palosaari <crope@iki.fi>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	hverkuil@xs4all.nl
Subject: Re: [PATCH 4/4] radio-si470x: Lower firmware version requirements
Date: Mon, 09 Jul 2012 12:03:59 +0200	[thread overview]
Message-ID: <4FFAAC8F.5080100@redhat.com> (raw)
In-Reply-To: <4FFAA1B9.6020306@iki.fi>

Hi,

On 07/09/2012 11:17 AM, Antti Palosaari wrote:
> On 07/07/2012 09:53 PM, Hans de Goede wrote:
>> Hi,
>>
>> On 07/07/2012 11:00 AM, Antti Palosaari wrote:
>>> Hello Hans,
>>>
>>> On 07/07/2012 10:58 AM, Hans de Goede wrote:
>>>> So is your device working properly now? The reason I'm asking it
>>>> because it is still causing a firmware version warning, and if
>>>> it works fine I would like to lower the firmware version warning
>>>> point, so that the warning goes away.
>>>
>>> I don't know what is definition of properly in that case.
>>>
>>> Problem is that when I use radio application from xawtv3 with that new
>>> loopback I hear very often cracks and following errors are printed to
>>> the radio screen:
>>> ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
>>> or
>>> ALSA lib pcm.c:7339:(snd_pcm_recover) overrun occurred
>>>
>>> Looks like those does not appear, at least it does not crack so often
>>> nor errors seen, when I use Rhythmbox to tune and "arecord -D hw:2,0
>>> -r96000 -c2 -f S16_LE | aplay -" to listen.
>>  >
>>> I can guess those are not firmware related so warning texts could be
>>> removed.
>>
>> Actually they may very well be firmware related. At least with my
>> firmware there
>> is a bug where actively asking the device for its register contents, it
>> lets
>> its audio stream drop.
>>
>> My patches fix this by waiting for the device to volunteer it register
>> contents
>> through its usb interrupt in endpoint, which it does at xx times / sec.
>>
>> So the first question would be, does this dropping of sound happen
>> approx 1 / sec
>> when using radio?
>>
>> If so this is caused by radio upating the signal strength it displays 1
>> / sec. If
>> you look at radio.c line 981 you will see a
>> radio_getsignal_n_stereo(fd); call
>> there in the main loop which gets called 1/sec. Try commenting this out.
>>
>> If commenting this out fixes your sound issues with radio, then the next
>> question is are you using my 4 recent si470x patches, if not please
>> give them a try. If you are already using them then I'm afraid that your
>> older
>> firmware may be broken even more then my also not so new firmware.
>
> I suspect these signal strength update pops are different thing. Those are almost so minor you cannot even hear.
>
> I recorded small sample:
> http://palosaari.fi/linux/v4l-dvb/xawtv3_radio.m4v
>
> And I am almost 100% sure those cracks are coming ALSA underrun/overrun as error text is seen just same time when crack happens.

The signal updates are what is causing the ALSA under-runs (*), the over-runs are the result of "catching up" after a under-run.

*) Or at least an important cause of them

> Commenting out line did not help.

Are you sure about this? Did you do a make after commenting, are you sure you were using the new build to test?

> But I think I was also hearing those small pops too and likely new four patches fixes those  - but it is hard to say because it cracks audio all time.

One other thing you can try is increasing the buffer size, using:
radio -L 1000

For example will increase it from the 500 millisecs default to 1 second

Regards,

Hans

  reply	other threads:[~2012-07-09 10:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 13:43 [PATCH 1/4] radio-si470x: Don't unnecesarily read registers on G_TUNER Hans de Goede
2012-06-14 13:43 ` [PATCH 2/4] radio-si470x: Always use interrupt to wait for tune/seek completion Hans de Goede
2012-06-14 13:43 ` [PATCH 3/4] radio-si470x: Lower hardware freq seek signal treshold Hans de Goede
2012-06-14 13:43 ` [PATCH 4/4] radio-si470x: Lower firmware version requirements Hans de Goede
2012-07-04 15:23   ` Antti Palosaari
2012-07-05  8:33     ` Hans de Goede
2012-07-05 13:35       ` Antti Palosaari
2012-07-05 13:41         ` Hans de Goede
2012-07-05 14:13           ` Antti Palosaari
2012-07-05 15:08             ` Hans de Goede
2012-07-05 15:09               ` Antti Palosaari
2012-07-07  7:58               ` Hans de Goede
2012-07-07  9:00                 ` Antti Palosaari
2012-07-07 18:53                   ` Hans de Goede
2012-07-09  9:17                     ` Antti Palosaari
2012-07-09 10:03                       ` Hans de Goede [this message]
2012-07-09 11:58                         ` Antti Palosaari
2012-07-09 13:02                           ` Hans de Goede
2012-07-09 13:34                             ` Antti Palosaari

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=4FFAAC8F.5080100@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=crope@iki.fi \
    --cc=hverkuil@xs4all.nl \
    --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.