All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Koenig <list@phasorlab.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] Support for ESI Miditerminal 4140
Date: Tue, 25 Apr 2006 17:33:55 +0200	[thread overview]
Message-ID: <87mze9mzz0.fsf@zebra.localdomain> (raw)
In-Reply-To: <s5hslo1zu6e.wl%tiwai@suse.de> (Takashi Iwai's message of "Tue, 25 Apr 2006 15:00:41 +0200")

Takashi Iwai <tiwai@suse.de> writes:
> The mutex belongs to the rawmidi device, so open/close is mutual as
> long as the same rawmidi device is used no matter which substream is
> used.  It doesn't care open/close of another rawmidi device, though.

Ah, thanks! This is the informationen I needed.

>> Hmm, then why should I hold an additional mutex?
>
> Well, I just thought of something as a replacement of mts->lock, but
> regarding open/close, yes, you can get rid of an extra mutex.
>
> You might still need a spinlock somewhere, but definitely not together
> with mdelay().

Yes, I decoupled now delay stuff from the spinlock sections and placed
the spinlocks just near the HW access.

New patch for next turn will follow.

Matthias


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2006-04-25 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 17:23 [PATCH] Support for ESI Miditerminal 4140 Matthias Koenig
2006-04-24 18:13 ` Takashi Iwai
2006-04-25  9:49   ` Matthias Koenig
2006-04-25 10:05     ` Takashi Iwai
2006-04-25 12:17       ` Matthias Koenig
2006-04-25 13:00         ` Takashi Iwai
2006-04-25 15:33           ` Matthias Koenig [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=87mze9mzz0.fsf@zebra.localdomain \
    --to=list@phasorlab.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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.