From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 193671] New: btattach -B /dev/ttyS1 -P qca -> Frame reassembly failed (-84)
Date: Mon, 30 Jan 2017 16:15:08 +0000 [thread overview]
Message-ID: <bug-193671-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=193671
Bug ID: 193671
Summary: btattach -B /dev/ttyS1 -P qca -> Frame reassembly
failed (-84)
Product: Drivers
Version: 2.5
Kernel Version: <4.9.*,4.10-rc6
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: nrndda@gmail.com
Regression: No
Created attachment 253591
--> https://bugzilla.kernel.org/attachment.cgi?id=253591&action=edit
ACPI BT part
Dell Venue 11 Pro has Dell Wireless 1538, which is QCA6234 SIP module. WiFi
works, but Bluetooth doesn't. It is recognized by kernel:
80860F0A:00: ttyS1 at MMIO 0x9094d000 (irq = 183, base_baud = 2764800) is a
16550A
But then, doing `btattach -B /dev/ttyS1 -P qca` gives this:
ROME setup
Set UART speed to 3000000
Frame reassembly failed (-84)
hci1 command 0xfc00 tx timeout
Failed to read version of ROME (-110)
Failed to get version 0xffffff92
ACPI says that it uses 115200 speed, but bt QCA protocol tries 3000000. Windows
drivers mention 115200 as initial speed as well.
Also after btattach number of interrupts rises and is claimed by serial:
183: 2 1 0 0 IO-APIC 39-fasteoi
serial
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2017-01-30 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 16:15 bugzilla-daemon [this message]
2017-01-30 16:16 ` [Bug 193671] btattach -B /dev/ttyS1 -P qca -> Frame reassembly failed (-84) bugzilla-daemon
2017-01-30 16:17 ` bugzilla-daemon
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=bug-193671-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/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.