From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Philip Balister <philip@balister.org>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: ALSA with linux-omap
Date: Fri, 16 Jan 2009 09:37:53 +0200 [thread overview]
Message-ID: <20090116093753.314559ab.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <496FE1C9.509@balister.org>
On Thu, 15 Jan 2009 18:24:25 -0700
"ext Philip Balister" <philip@balister.org> wrote:
> cat /dev/random > /dev/dsp make a brief soft sound, then stops. Ctrl-c
> and you can hear a pop a few seconds later.
>
This sounds like digital audio link between cpu and codec is working but
DMA stalls after transmitting one ALSA period or buffer.
What's your HW? And probably you are using ASoC on OMAP. I.e.
CONFIG_SND_SOC & CONFIG_SND_OMAP_SOC?
> Does this make any sense to anyone? The non pm kernels have been working
> great.
>
I'm also curious to know since unfortunately I haven't investigated
yet how well ASoC OMAP drivers co-operate with the dynamic PM.
Jarkko
prev parent reply other threads:[~2009-01-16 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 1:24 ALSA with linux-omap Philip Balister
2009-01-16 7:37 ` Jarkko Nikula [this message]
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=20090116093753.314559ab.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=philip@balister.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.