public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: lamikr <lamikr@cc.jyu.fi>
To: James Selvam <james.iisc@gmail.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH 0/3] aic23 sound driver fixes
Date: Wed, 31 May 2006 03:54:11 +0300	[thread overview]
Message-ID: <447CE933.7020207@cc.jyu.fi> (raw)
In-Reply-To: <fd1e34b0605260412h3d5931bcvfb629e62b61cc30b@mail.gmail.com>


>
>
>     Can you verify some issues that have remained open.
>     Is it working for you without these lines in the audio_process_dma()
>     function. (in omap_alsa.c)
>
>             spin_lock_irqsave(&s->dma_lock, flags);
>             omap_stop_alsa_sound_dma(s);
>             spin_unlock_irqrestore(&s->dma_lock, flags);
>
>
> I had to add these lines to get it to work. It does not work without
> these lines. I had added these lines while testing the patches you had
> sent.
>
>     At least you added those lines once for there for testing. (I need to
>     use those with my omap1510 based device) 
>
>
> I think it is not a h6300 specific requirement (as present in the
> code) but a more generic OMAP 1510 requirement (atleast Innovator OMAP
> 1510 definitely requires it).

Thanks for the info, I will send patch immediately. Or does others have
any better idea to handle this in omap1510?

Mika

      reply	other threads:[~2006-05-31  0:54 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
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 [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=447CE933.7020207@cc.jyu.fi \
    --to=lamikr@cc.jyu.fi \
    --cc=james.iisc@gmail.com \
    --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