From: Marcel Holtmann <marcel@holtmann.org>
To: Lars Grunewaldt <lgw@dark-reality.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] question about hci_usb endpoint selection...
Date: Sat, 16 Oct 2004 14:06:54 +0200 [thread overview]
Message-ID: <1097928414.4911.27.camel@pegasus> (raw)
In-Reply-To: <416EF4B0.6070802@dark-reality.de>
Hi Lars,
> OK, I added hci_usb_notify(..) and it works as it should (get's the
> notify when voice mode is changed).
you also need some extra changes from my Bitkeeper repository, because I
fixed some locking parts around the notify framework. The number of ACL
and SCO links are now also counted separately. You need that for
selecting the correct alternate setting.
> Now for the "real stuff"... :)
>
> I think to handle the voice mode change correctly, I have to duplicate
> the code from about line 874..922 that locates the "proper" alternate
> setting; before this can happen, the notify function must close
No, because the correct alternate setting is described in the Bluetooth
HCI USB transport specification.
> ((husb *)hdev->driver_data)->isoc_iface with
> usb_driver_release_interface(...)
Don't try to release and claim it again. You are not in the probe()
function.
> is there anything else to do? Must some buffers be dropped or free'd or
> something? is it possible to simply re-set
> isoc_iface, isoc_in_ep and isoc_out_ep?
No simple reset. Change the alternate setting, but you maybe have to
suspend the ISOC URBs first and then resume them. Check the USB API
definition of it first.
> Or is it in fact not neccesary to disconnect isoc_iface and only change
> the values of isoc_in_ep and isoc_out_ep?
Maybe you should look at the /proc/bus/usb/devices first, because the
endpoint identifiers on the second interface are always the same. You
must tell the USB core to switch the alternate setting.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-10-16 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 12:46 [Bluez-devel] question about hci_usb endpoint selection Lars Grunewaldt
2004-10-14 11:20 ` Marcel Holtmann
2004-10-14 21:50 ` Lars Grunewaldt
2004-10-16 12:06 ` Marcel Holtmann [this message]
2004-10-16 16:19 ` Lars Grunewaldt
2004-10-17 11:41 ` Marcel Holtmann
2004-10-17 14:15 ` Lars Grunewaldt
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=1097928414.4911.27.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=lgw@dark-reality.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox