From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@kernel.org
Subject: [Bug 198953] hci_bcm: Streamline runtime PM code change for 4.16 kernel breaks bluetooth on ASUS T100TA
Date: Thu, 15 Mar 2018 07:58:53 +0000 [thread overview]
Message-ID: <bug-198953-62941-3qVYkMAAGt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198953-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198953
Hans de Goede (jwrdegoede@fedoraproject.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwrdegoede@fedoraproject.or
| |g
--- Comment #5 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
Hi All,
So as discussed on the bluetooth list I've hit the same problem of the bcm
bluetooth device getting stuck in suspend. My solution is a simple revert of
the offending commit, as instead of being just a simple cleanup it has
unintended and unwanted side-effects. Anyways lets discuss that further on the
list.
My main reason for replying here is because of the adding of extra dmi matches
for active-low interrupts. I've come up with an alternative approach which
actually removes DMI matches, since I believe that we simply need to always
treat the IRQ as active-low if it is declared with an "Interrupt" ACPI resource
(the other way is with a "GpioInt" resource).
I'll attach my patch for this, if you can test this on the machines needing an
extra DMI match that would be great. I would also appreciate it if you can run:
acpidump -o acpidump.vendorname-modelname
And attach the generated acpidump.vendorname-modelname file here.
Regards,
Hans
--
You are receiving this mail because:
You are the assignee for the bug.
next parent reply other threads:[~2018-03-15 7:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-198953-62941@https.bugzilla.kernel.org/>
2018-03-15 7:58 ` bugzilla-daemon [this message]
2018-03-15 8:03 ` [Bug 198953] hci_bcm: Streamline runtime PM code change for 4.16 kernel breaks bluetooth on ASUS T100TA bugzilla-daemon
2018-03-15 8:07 ` bugzilla-daemon
2018-03-15 8:08 ` bugzilla-daemon
2018-03-15 8:09 ` bugzilla-daemon
2018-03-15 17:06 ` bugzilla-daemon
2018-03-15 17:08 ` bugzilla-daemon
2018-03-15 17:09 ` bugzilla-daemon
2018-03-15 17:10 ` bugzilla-daemon
2018-03-15 17:21 ` bugzilla-daemon
2018-03-15 17:23 ` bugzilla-daemon
2018-03-15 18:25 ` bugzilla-daemon
2018-03-15 18:26 ` bugzilla-daemon
2018-03-15 18:31 ` bugzilla-daemon
2018-03-15 19:47 ` bugzilla-daemon
2018-03-15 20:01 ` bugzilla-daemon
2018-03-16 10:36 ` bugzilla-daemon
2018-03-18 3:49 ` bugzilla-daemon
2018-03-18 3:51 ` bugzilla-daemon
2018-03-18 16:54 ` bugzilla-daemon
2018-03-18 18:43 ` bugzilla-daemon
2018-03-20 7:45 ` bugzilla-daemon
2018-03-22 16:31 ` bugzilla-daemon
2018-03-27 15:07 ` 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-198953-62941-3qVYkMAAGt@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@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.