All of lore.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: Thu, 25 May 2006 14:28:17 +0300	[thread overview]
Message-ID: <447594D1.60401@cc.jyu.fi> (raw)
In-Reply-To: <fd1e34b0605222135x650aaac9t31437eac3b9fdb7a@mail.gmail.com>

James

Thanks for the info, I have been quite busy but in Finland we have today
holiday so I have now time again to
prepare a new set of patches. 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);

At least you added those lines once for there for testing. (I need to
use those with my omap1510 based device)

Mika

James Selvam wrote:

> Hi Mika/All,
>
> Im happy to inform you that the patches you sent have been tested and
> they are found to be working fine on my Innovator 1510. There should
> be no problem with it going into the git.
>
> I was bogged down by a hardware snag on my Innovator kit which delayed
> the verification. But I see its fine now. :-) .
>
> Thanx for the help.
>
> Regards,
> James.
>
>
> On 5/3/06, *lamikr* <lamikr@cc.jyu.fi <mailto:lamikr@cc.jyu.fi>> wrote:
>
>     Following patch set should fix the broken method references to
>     from Alsa
>     and OSS drivers to tlv320aic23 i2c drivers that has been reported.
>     In addition the 3:rd patch contains the platform driver code that the
>     innovator requires if it wants to use alsa driver.
>
>     I do not own myself the innovator or aic23 drivers so it would be nice
>     if someone else could test these.
>
>     Mika
>     _______________________________________________
>     Linux-omap-open-source mailing list
>     Linux-omap-open-source@linux.omap.com
>     <mailto:Linux-omap-open-source@linux.omap.com>
>     http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>     <http://linux.omap.com/mailman/listinfo/linux-omap-open-source>
>
>

  reply	other threads:[~2006-05-25 11:28 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 [this message]
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=447594D1.60401@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 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.