Hi Marcel,
On Thu, Feb 09, 2012 at 02:51:11PM +0100, Marcel Holtmann wrote:
> > > > > > > if (!test_bit(HCI_RAW, &hdev->flags) &&
> > > > > > > - test_bit(HCI_QUIRK_NO_RESET,
> > > > &hdev->quirks)) {
> > > > > > > + !test_bit(HCI_QUIRK_NO_RESET,
> > > > &hdev->quirks)) {
> > > > > > Nack. The NO_RESET quirk is supposed to prevent reset during the
> > > > device
> > > > > > init sequence. The purpose of the test in hci_dev_do_close() is to
> > > > let
> > > > > > the reset be done there instead.
> > > > >
> > > > > we might wanna rename this into HCI_QUIRK_RESET_ON_CLOSE. Otherwise
> > > > > people keep in getting confused.
> > > > >
> > > >
> > > > Moreover without my patch my USB dongle gets stuck after reset.
> > >
> > > please send hcidump traces for this. And you mean hciconfig hci0 reset?
> >
> > In the trace there is only one line:
> >
> > < HCI Command: Reset (0x03|0x0003) plen 0
> >
> > Then chip stuck (I am testing this inside virtual machine).
> >
> > I have A-Link BCM USB dongle.
>
> the patch in general is correct, but it seems that it has some side
> effects on some dongles. Can you try doing hciconfig hci0 reset versus a
> hciconfig hci0 down + hciconfig hci0 up and if it makes any difference.
I was testing for some time and I think now with Johan's patch reverted it
only a little bit better. I was testing with hciconfig hci0 down +
hciconfig hci0 up and with hciconfig hci0 reset and at some point dongle
gets stuck in my virtualbox either way. This is very unstable and probably
related to timing.
Has anybody else experienced the same problem?
Best regards
Andrei Emeltchenko
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
