On Sat, Sep 08, 2012 at 01:32:58PM +0200, Miroslav Sabljic wrote:
On 09/07/2012 07:07 PM, Sarah Sharp wrote:
Big improvment with the latest patches from
for-usb-linus-plus-set-addr branch. My bluetooth device now works as
expected, I can suspend and device isn't disconnected after a
resume.
On 09/07/2012 07:07 PM, Sarah Sharp wrote:
Big improvment with the latest patches from
for-usb-linus-plus-set-addr branch. My bluetooth device now works as
expected, I can suspend and device isn't disconnected after a
resume. Although those timeout and not accepting address errors are
still
On Fri, Sep 07, 2012 at 01:22:43AM +0200, Miroslav Sabljic wrote:
On 09/06/2012 08:12 PM, Sarah Sharp wrote:
So, try compiling a kernel from the for-usb-linus-plus-set-addr branch
in the same git repo, and see if that helps. If it doesn't, please turn
on CONFIG_USB_XHCI_HCD_DEBUGGING and send
On 09/06/2012 12:02 AM, Sarah Sharp wrote:
I'm actually wondering if you're hitting a bug that is fixed by a patch
in my queue to send to Greg. Apparently, some BIOSes expect specific
USB ports on the mobile Panther Point chipset to remain under the EHCI
controller, even though they can be
On Mon, Aug 27, 2012 at 02:09:53PM +0200, Miroslav Sabljic wrote:
On 08/22/2012 05:39 PM, Miroslav Sabljic wrote:
If the device is working properly on boot up and fails after
suspend/resume, you can try the patch attached to see if it helps on
the failure after system resume.
On Wed, Aug 22, 2012 at 7:30 PM, Miroslav Sabljic
miroslav.sabl...@avl.com wrote:
On 08/21/2012 01:33 PM, Andiry Xu wrote:
Not sure. it's hard to debug via software side because software seems
does not do anything wrong. If you disable USB3 support in BIOS the
ports are handled by EHCI
Adding Linux-USB back..
On Tue, Aug 21, 2012 at 7:31 PM, Andiry Xu and...@gmail.com wrote:
On Mon, Aug 20, 2012 at 8:17 PM, Miroslav Sabljic
miroslav.sabl...@avl.com wrote:
On 08/19/2012 03:29 PM, Andiry Xu wrote:
Thanks. The dmesg indicates the device does not respond the address
device
On 08/18/2012 12:33 PM, Andiry Xu wrote:
From the dmesg, it looks like your xhci host controller is in a mess.
It either does not respond to the address device command, or just
return an invalid response. And worse, the memory is leaked.
I think the host controller is not initialized properly
On Sat, Aug 18, 2012 at 8:16 PM, Miroslav Sabljic
miroslav.sabl...@avl.com wrote:
On 08/18/2012 12:33 PM, Andiry Xu wrote:
From the dmesg, it looks like your xhci host controller is in a mess.
It either does not respond to the address device command, or just
return an invalid response. And
