From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Azizul Hakim <azizulfahim2002@gmail.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: 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: Mon, 22 Jun 2015 09:55:38 +0300 [thread overview]
Message-ID: <5587B16A.90100@ti.com> (raw)
In-Reply-To: <CA+k7WwbSt-sxQePXx=A=2LJgNS2OPTrZQFhHcD2g02HM0P7NYg@mail.gmail.com>
On 06/17/2015 05:53 PM, Azizul Hakim wrote:
> Okay, its good to learn something new on every day. So how do I configure
> McBSP port clocking? I'm very new on these things and was unable to find any
> useful link on this point. :(
I don't see anything in the driver [1] which would indicate that the issue is
in any ways specific to BeagleBone (apart from the beagleaudio strings in the
driver). You are not using the McASP, nor the edma-pcm/davinci-pcm.
What you seams to have is a custom sound card driver for USB. Is there a
reason why you could not use the already available USB sound card for this?
Are you running exactly the same kernel under ubuntu and debian?
--
Péter
[1] https://github.com/azizulhakim/beagleusb/blob/master/beagle-audio.c
> On Wed, Jun 17, 2015 at 5:05 AM, Liam Girdwood
> <liam.r.girdwood@linux.intel.com <mailto:liam.r.girdwood@linux.intel.com>> wrote:
>
> + 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
>
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-06-22 6:55 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
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 [this message]
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=5587B16A.90100@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=azizulfahim2002@gmail.com \
--cc=clemens@ladisch.de \
--cc=liam.r.girdwood@linux.intel.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 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.