All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: alsa-devel@lists.sourceforge.net
Subject: Plugin loading and unloading
Date: Sat, 23 Apr 2005 16:36:00 +0200	[thread overview]
Message-ID: <1114266960.10706.30.camel@pegasus> (raw)

Hi guys,

I am working again on the A2DP Bluetooth plugin and the caching support
in the latest ALSA library is nice and allows me to keep the underlaying
link connected while stupid programs like XMMS closes the PCM when they
switch the tracks.

The PCM opening part and reusing of the underlaying AVDTP connection is
easy, but I am a little bit concerned about the plugin unloading time.
So is it possible to add init() and exit() functions that are called
when the plugin is loaded and unloaded. Like we have for kernel modules?

Do the ALSA library has a timer mechanism that we can use inside a
plugin. Since it is a bad idea to hold the Bluetooth connection open for
all the time, I like to add a idle timeout. This allows me to put the
connection into sniff mode to save power or terminate it.

Also the listing of plugins is still missing. I am fine with a general
or plugin specific flag to make its PCM visible.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-04-23 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-23 14:36 Marcel Holtmann [this message]
2005-04-30 11:35 ` Plugin loading and unloading Marcel Holtmann
2005-05-09  8:10 ` Jaroslav Kysela
2005-05-09  8:16   ` Marcel Holtmann
2005-05-09  8:36     ` Jaroslav Kysela
2005-05-09  9:07       ` Marcel Holtmann
2005-05-10 11:21         ` Device name lists Jaroslav Kysela
2005-05-10 15:19           ` Marcel Holtmann
2005-05-10 15:32             ` Clemens Ladisch
2005-05-10 15:57               ` Jaroslav Kysela

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=1114266960.10706.30.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.