Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Saurav SAHU <saurav.sahu@st.com>
Cc: alsa-user@lists.sourceforge.net, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] ALSA utility aplay/arecord error
Date: Thu, 13 Mar 2008 11:50:48 +0100	[thread overview]
Message-ID: <s5hve3q99tj.wl%tiwai@suse.de> (raw)
In-Reply-To: <009601c88263$16950fe0$7c70500a@amk.st.com>

At Mon, 10 Mar 2008 11:59:04 +0800,
Saurav SAHU wrote:
> 
> Hi all
> 
> The platform on which I am trying to perform ALSA playback and record with USB sound device is based on a MIPS CPU running Linux kernel 2.6.14. The kernel uses non-coherent DMA in the configuration:
>   CONFIG_DMA_NONCOHERENT=y
>   CONFIG_DMA_NEED_PCI_MAP_STATE=y
>   CONFIG_CPU_BIG_ENDIAN=y
>   CONFIG_SYS_SUPPORTS_BIG_ENDIAN=y
>   CONFIG_BOOT_ELF32=y
>   CONFIG_MIPS_L1_CACHE_SHIFT=5
> I have attached the kernel .config file for further information. So far, I have not succeeded in hearing sound with 'aplay', or capturing sound with 'arecord'.
> 
> If there have been any similar issues reported on ALSA usage with MIPS CPU based on non-coherent DMA in the past, please let me know. Also, if there have been any patches developed for successful resolution of this issue on similar platform/configuration, it would be very useful for me.

Yes, there is a known long-standing problem wrt cache coherency.
Try to disable the mmap support in the driver as a test.


Takashi

> 
> Thanks & Regards
> Saurav
> 
>   ----- Original Message ----- 
>   From: Saurav Sahu 
>   To: alsa-user@lists.sourceforge.net 
>   Sent: Friday, March 07, 2008 4:33 PM
>   Subject: Re: ALSA utility aplay/arecord error
> 
> 
>   I have been able to resolve the previously reported errors by setting the environment variable for ALSA configuration file on the target filesystem of the embedded platform.
> 
>   However, I do not hear any audio from USB sound device with speaker-test or aplay:
> 
>   Upon using arecord for recording, I get an error:
> 
>   Is this problem related to a low-level driver issue which may not be working well on target platform? Could there be a DMA related issue as the samples don't seem to be transferred to the USB audio device.
> 
> 
>     ----- Original Message ----- 
>     From: Saurav Sahu 
>     To: alsa-user@lists.sourceforge.net 
>     Sent: Thursday, March 06, 2008 4:28 PM
>     Subject: ALSA utility aplay/arecord error
> 
> 
>     Hello
> 
>     I am working towards using ALSA for playback and capture on an embedded platform running Linux. The kernel uses ALSA driver version 1.0.10rc1. I had manually built and installed ALSA library (v1.0.10) and ALSA utilities (v1.0.10) for the target platform filesystem. I have a USB audio device (C-Media) connected to the USB port of the board and it seems to be successfully successfully detected by the driver.
> 
>     However, when I run ALSA utilities like aplay, arecord or speaker-test, I observe errors opening the hardware device which may be related to the configuration on the filesystem.
> 
>     Are these errors from ALSA utility/library due to the detection of hardware, ALSA configuration files or something else related to my target device filesystem?
> 
>     Thanks in advance for any help. Do let me know if you need any more details.
> 
>     Best Regards
>     Saurav

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-03-13 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10  3:59 ALSA utility aplay/arecord error Saurav SAHU
2008-03-13 10:50 ` Takashi Iwai [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=s5hve3q99tj.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=saurav.sahu@st.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