From: soraberri <421246@posta.unizar.es>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] btsco and alsa driver interaction
Date: Tue, 08 Mar 2005 20:11:31 +0100 [thread overview]
Message-ID: <d0ktcr$n2i$1@sea.gmane.org> (raw)
I have studied btsco.c code (the userspace code part), but I'm scared of
the kernel part. It's my first match with a kernel driver and it has won
the game... so, I would like to ask you just to figure out how the big
black box is behaving.
My impression is that in btsco daemon, once we get the descriptor for
the SOCK_STREAM socket we just need to hook it to the hwdep device, and
it seems that it is done this way -more or less-
sd=sco_connect( &local,
&bdaddr,
&sco_handle,
&sco_mtu));
bt_sco_set_fd(handle, sd);
where _handle_ represents the device. So I imagine that all what is
happening with the SCO channel is "carried" into the device. Is it right?
I also imagine that when we poll data from the hwdep interface, we are
not polling SCO data type (which I assume it is being drived
automatically); instead, we are polling for volume-control data type
which is enigmatically (for me) generated at the core of the driver. Is
it right?
The question is, 'when does the following condition evaluate TRUE ?
if (!snd_hwdep_poll_descriptors_revents(handle, &pfds[nfds - 1], 1,
revents) && revents & POLLIN) {
a) when we have used the write function some point before, like this:
snd_hwdep_write(handle, volumes, sizeof(volumes));
b) only when the driver is initialized at the begining
c) or, periodically at some interval defined in the driver code...
well, sorry if these answers are a bit obscure, they are just to give
you an idea of how poor is what I can imagine. I think what I wish to
know is 'when and why will the hwdep interface produce the events we are
listening for'?
Thanks a lot in advance
Luis Peiro
-------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-03-08 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 19:11 soraberri [this message]
2005-03-09 2:04 ` [Bluez-devel] btsco and alsa driver interaction Brad Midgley
2005-03-09 9:17 ` [Bluez-devel] " soraberri
2005-03-10 8:26 ` suche.org
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='d0ktcr$n2i$1@sea.gmane.org' \
--to=421246@posta.unizar.es \
--cc=bluez-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.