From: Marcel Holtmann <marcel@holtmann.org>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Hardware interface constant for Bluetooth
Date: Mon, 08 Nov 2004 13:03:48 +0100 [thread overview]
Message-ID: <1099915428.6896.107.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.58.0411081152120.2162@pnote.perex-int.cz>
Hi Jaroslav,
> > I like to drive the Bluetooth audio support a little bit and it would be
> > great if you can add a hardware interface constant for us. I don't know
> > what is the correct procedure to do it, but from my first analysis it
> > seems that it is enough to add a patch like the one below to the kernel
> > code and the library code. Everything else can be developed outside the
> > ALSA core.
> >
> > + SNDRV_HWDEP_IFACE_BLUETOOTH, /* Bluetooth audio */
>
> Do you need really this change? This identifier is only used for hardware
> independent API (hwdep) - mostly for firmware / DSP code handling and
> other things which don't fall into abstract APIs.
this is a little bit tricky. Besides the native support for transporting
PCM data over a Bluetooth SCO channel, the headset/handsfree profile
uses a RFCOMM channel (serial port emulation) for additional settings.
On this channel they use AT commands and actually I don't wanna put a AT
parser into the kernel. It is in somekind possible, but I still think
that it does not belong there, because it is profile specific and a
Bluetooth profile is an application and applications should run in user
space. On the other hand you still need to create that SCO channel from
user space with somekind of ioctl, because the kernel can't know when
this channel must be established. It depends on some AT commands that
are send over the RFCOMM channel.
So my plan is to write a kernel module that is reponsible for the SCO
audio traffic. This registers as a soundcard with the ALSA subsystem and
it also registers a Bluetooth HWDEP. There is no initial PCM device
registered with this soundcard. These are only added when a SCO channel
is opened from the peer side or requested through an ioctl on the HWDEP
interface. Besides this the HWDEP would also control the mixer settings,
because these are exchanged over the RFCOMM channel.
Do you think this makes sense?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-08 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 1:24 Hardware interface constant for Bluetooth Marcel Holtmann
2004-11-08 10:54 ` Jaroslav Kysela
2004-11-08 12:03 ` Marcel Holtmann [this message]
2004-11-08 12:18 ` Jaroslav Kysela
2004-11-08 12:28 ` Marcel Holtmann
2004-11-09 12:16 ` Marcel Holtmann
2004-11-09 13:10 ` 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=1099915428.6896.107.camel@pegasus \
--to=marcel@holtmann.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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.