From: Krzysztof Adamski <k@japko.eu>
To: alsa-devel@alsa-project.org
Subject: Plug plugin not working on Raspberry Pi.
Date: Fri, 13 Jul 2012 09:38:14 +0200 [thread overview]
Message-ID: <4FFFD066.30000@japko.eu> (raw)
Hi,
for a couple of days I'm trying to figure out problems with ALSA on
Raspberry Pi. It turned out that for some reason, plug plugin is not
working as expected. Id does work correctly when I'm using PCM
configuration that can be handled directly by HW but any other
configuration (like unsuported format, more channes etc) fails with
"Invalid argument" on snd_pcm_hw_params.
It's not my code that fails because of this by it's both mplayer and
VLC. Both snd_pcm_hw_params_set_format and snd_pcm_hw_params_test_format
(and other similar functions) does not return error. Only when
snd_pcm_hw_params is run, there is one.
I'm using Debian Wheezy, with ALSA 1.0.25 with all default ALSA
configuration. ALSA drivers for RPi are not in mainline kernel but they
can be viewed here:
https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm (it's
bcm2835). Card capabilities seems to be described correctly:
static struct snd_pcm_hardware snd_bcm2835_playback_hw = {
.info = (SNDRV_PCM_INFO_INTERLEAVED | SNDRV_PCM_INFO_BLOCK_TRANSFER),
.formats = SNDRV_PCM_FMTBIT_U8 | SNDRV_PCM_FMTBIT_S16_LE,
.rates = SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_48000,
.rate_min = 8000,
.rate_max = 48000,
.channels_min = 1,
.channels_max = 2,
.buffer_bytes_max = (4 * 8 - 1) * 1024, /* Needs to be less than
audioplay buffer size */
.period_bytes_min = 1 * 1024,
.period_bytes_max = (4 * 8 - 1) * 1024,
.periods_min = 1,
.periods_max = 4 * 8 - 1,
};
So, I would like someone to help me investigate if it's a userspace or
driver BUG and how to fix this. I will be happy to provide any
information that is needed for debug, test patches, recompile with some
debugin enabled etc.
reply other threads:[~2012-07-13 7:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FFFD066.30000@japko.eu \
--to=k@japko.eu \
--cc=alsa-devel@alsa-project.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.