Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Azizul Hakim <azizulfahim2002@gmail.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Audio Driver Works In Ubuntu but Crash in Debian After 2nd Run
Date: Wed, 17 Jun 2015 10:05:34 +0100	[thread overview]
Message-ID: <1434531934.2471.9.camel@loki> (raw)
In-Reply-To: <55812940.5050906@ladisch.de>

+ Peter for Beaglebone

On Wed, 2015-06-17 at 10:01 +0200, Clemens Ladisch wrote:
> Azizul Hakim wrote:
> > Driver didn't start the DMA: Not sure how to track on this point. Any suggestion?
> > Interrupt do not arrive correctly: Is this the hardware issue or ALSA issue?
> 
> These would imply that some your driver, or some code used by your driver,
> did not configure the DMA/interrupt correctly.

On beaglebone it may also be that the McBSP port clocking is not
configured correctly.

Liam

  reply	other threads:[~2015-06-17  9:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14  3:18 Audio Driver Works In Ubuntu but Crash in Debian After 2nd Run Azizul Hakim
2015-06-15 14:26 ` Azizul Hakim
2015-06-16  7:50 ` Clemens Ladisch
2015-06-16 19:30   ` Azizul Hakim
2015-06-17  8:01     ` Clemens Ladisch
2015-06-17  9:05       ` Liam Girdwood [this message]
2015-06-17 14:53         ` Azizul Hakim
2015-06-19  4:32           ` Azizul Hakim
2015-06-19  5:56             ` Takashi Sakamoto
2015-06-19  6:21               ` Takashi Sakamoto
2015-06-20  2:52                 ` Takashi Sakamoto
2015-06-19  8:01             ` Clemens Ladisch
2015-06-21 14:34             ` Raymond Yau
2015-06-22  6:55           ` Peter Ujfalusi
2015-06-22 15:00             ` Azizul Hakim
2015-06-26 14:20               ` Antonio Ospite

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=1434531934.2471.9.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=azizulfahim2002@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=peter.ujfalusi@ti.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox