From: "James Selvam" <james.iisc@gmail.com>
To: lamikr@cc.jyu.fi
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH 0/3] aic23 sound driver fixes
Date: Mon, 8 May 2006 11:29:01 +0530 [thread overview]
Message-ID: <fd1e34b0605072259o7a4bb4bei6b0d0556047751c0@mail.gmail.com> (raw)
In-Reply-To: <445B7A03.6040908@cc.jyu.fi>
Hi Mika/All,
I have all the relavant nodes created in /dev/snd directory. This includes
controlCx, hwCxDy, midiCxDy, pcmCxDyc, pcmCxDyc, seq & timer.
I have also put the following three lines:
spin_lock_irqsave(&s->dma_lock, flags);
omap_stop_alsa_sound_dma(s);
spin_unlock_irqrestore(&s->dma_lock, flags);
Any ideas about how to get this working? Is there something else missing?
Thanks,
James.
On 5/5/06, lamikr <lamikr@cc.jyu.fi> wrote:
>
> James Selvam wrote:
>
> > Hi Mika/All,
> >
> > The patch set the MCLK error all right. It infact took the right CLK
> > freq of 12 MHz:
> >
> > Advanced Linux Sound Architecture Driver Version 1.0.11rc2 (Wed Jan 04
> > 08:57:20
> > 2006 UTC).
> > MCLK = 12000000 [12000000], usecount = 1
> > audio support initialized
> > ALSA device list:
> > #0: OMAP Innovator AIC23
> >
> > But aplay -l still fails. It fails to recognise and list the hardware
> > present:
>
> Hmm, do you have udev installed and do you get nodes created to /dev/snd
> directory?
>
> >
> > **** List of PLAYBACK Hardware Devices ****
> > ALSA lib control.c:818:(snd_ctl_open_noupdate) Invalid CTL hw:0
> > aplay: device_list:232: control open (0): No such file or directory
> >
> > I then tried to do a simple "cat raw_file > /dev/dsp" (OSS emulation
> > enabled). It just gave me some noise. Another player "bplay"
> > cross-compiled for ARM gave similar results.
>
> So, you were able to hear something? I had some DMA problems with my
> OMAP1510 based h6300 and therefore the omap-alsa.c has
> #ifdef CONFIG_MACH_OMAP_H6300 in one place. You could try to enable that
> also in your board?
> For Daniel the AIC23 alsa code however worked with the OSK board without
> need for the modifications.
>
> Mika
>
next prev parent reply other threads:[~2006-05-08 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 20:38 [PATCH 0/3] aic23 sound driver fixes lamikr
2006-05-03 11:20 ` James Selvam
2006-05-03 19:33 ` lamikr
2006-05-04 10:18 ` James Selvam
2006-05-05 16:14 ` lamikr
2006-05-08 5:59 ` James Selvam [this message]
2006-05-23 4:35 ` James Selvam
2006-05-25 11:28 ` lamikr
2006-05-26 11:12 ` James Selvam
2006-05-31 0:54 ` lamikr
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=fd1e34b0605072259o7a4bb4bei6b0d0556047751c0@mail.gmail.com \
--to=james.iisc@gmail.com \
--cc=lamikr@cc.jyu.fi \
--cc=linux-omap-open-source@linux.omap.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