From: Dmitry Tunin <hanipouspilot@gmail.com>
To: "Raphaël Jakse" <raphael.jakse@gmail.com>,
"Marcel Holtmann" <marcel@holtmann.org>,
"Gustavo Padovan" <gustavo@padovan.org>,
"Johan Hedberg" <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: PROBLEM: AR9462: ath3k and btusb: support for device 04ca:300d makes it disconnect/reconnect indefinitely
Date: Mon, 20 Jul 2015 15:04:41 +0300 [thread overview]
Message-ID: <55ACE3D9.8090908@gmail.com> (raw)
In-Reply-To: <55AC1C43.6030301@gmail.com>
> [X.] Other notes, patches, fixes, workarounds:
>
> A workaround to this bug is to blacklist ath3k and btusb, and have two versions of them:
>
> 1) The patched versions, which contains the following lines:
>
> in btusb.c:
> { USB_DEVICE(0x04CA, 0x300d) },
>
> in ath3k.c:
> { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
> 2) The unpatched versions, same modules without these lines.
>
> The workaround is to insmod the patched versions (which load the
> firmware), rmmod them after a second, and insmod the unpatched versions.
> After that Bluetooth is working until next computer suspend or halt.
> The firmware is not kept loaded after suspend or halt, but it is kept
> loaded after a reboot. Using the unpatched versions without the firmware being loaded makes Bluetooth look activated but unusable.
>
> I also noticed that iProduct = 0 for the 04ca:300d device.
>
> This is my first bug report to the kernel, so please tell me if I did anything wrong.
>
> Cheers,
>
> Raphaël.
>
This looks like a bug in ath3k module. It loads firmware, but after that hangs.
That is why when you load btusb after that, BT works.
iProduct is 0 for all new AR3012 devices. It is not a criterion now to distinguish AR3011 and AR3012.
prev parent reply other threads:[~2015-07-20 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 21:53 PROBLEM: AR9462: ath3k and btusb: support for device 04ca:300d makes it disconnect/reconnect indefinitely Raphaël Jakse
2015-07-20 12:04 ` Dmitry Tunin [this message]
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=55ACE3D9.8090908@gmail.com \
--to=hanipouspilot@gmail.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=raphael.jakse@gmail.com \
/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.