All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gabriel M. Beddingfield" <gabrbedd@gmail.com>
To: Anders Alex <alibobar@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: twl4030 and Puredata/jack
Date: Sat, 09 Mar 2013 12:21:20 -0800	[thread overview]
Message-ID: <513B99C0.8020805@gmail.com> (raw)
In-Reply-To: <CAAuz6aqqixPxBZQQ5GJinPDfseSVKcnBCvMnLt-6Uad4fP9uPw@mail.gmail.com>

On 03/08/2013 07:31 AM, Anders Alex wrote:
> I will paste a couple of use-cases and their corresponding dmesg output:
>
> When I run ~$ pd -alsa I get:
>
> snd_pcm_hw_params (input): Invalid argument
> snd_pcm_hw_params (output): Invalid argument
>
> and:
> [201429.385345] omap_mcbsp_dai_hw_params: not enough bandwidth for desired
> rate and channels
> [201429.385375] asoc: interface omap-mcbsp-dai.1 hw params failed

Strange.  In kernel 3.2, omap-mcbsp-dai.1 (McBSP1) is used for the 
codec.  But in the mainline it's omap-mcbsp-dai.2.

So the question is... how is the board wired?  And does your kernel 
match the board?

> With 'jackd -d alsa -S'  (need s16_le):
>
> loading driver ..
> creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|16bit
> control device hw:0
> configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
> ALSA: final selected sample format for capture: 16bit little-endian
> ALSA: use 2 periods for capture
> ALSA: cannot set hardware parameters for capture
> ALSA: cannot configure capture channel

Looking at the source, it looks like hw:0,0 has no capture port.  Try 
adding the -P parameter to jackd.  Playback only.

Also, post the output of:

    $ cat /proc/asound/devices

-gabriel

  reply	other threads:[~2013-03-09 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 15:31 twl4030 and Puredata/jack Anders Alex
2013-03-09 20:21 ` Gabriel M. Beddingfield [this message]
2013-03-11  1:42   ` Anders Alex
2013-03-11 10:42     ` Peter Ujfalusi
2013-03-11 16:57       ` Grazvydas Ignotas
2013-03-11 13:45 ` Peter Ujfalusi
2013-03-11 17:31   ` Peter Ujfalusi
2013-03-11 18:21     ` Anders Alex

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=513B99C0.8020805@gmail.com \
    --to=gabrbedd@gmail.com \
    --cc=alibobar@gmail.com \
    --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.