From: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>
To: Loic Poulain <loic.poulain@intel.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org
Cc: Frederic Danis <frederic.danis@intel.com>
Subject: Re: Bluetooth not working anymore due to too agressive PM in hci_bcm ? (was: [PATCH v5 5/5] Bluetooth: hci_bcm: Add suspend/resume runtime PM functions)
Date: Thu, 06 Oct 2016 09:03:08 +0200 [thread overview]
Message-ID: <1475737388.5772.1.camel@gmail.com> (raw)
In-Reply-To: <1475702165.5992.4.camel@gmail.com>
Hi Loic,
> > I remember Frederic had some gpio/irq polarity issues:>
> > 5cebdfea32b89911d4540440c1c2854a1a3d591e
> > Bluetooth: hci_bcm: Fix IRQ polarity for T100
> > Maybe the ACPI table is not correct on some devices.
>
>
> I had seen that patch indeed. I'm attaching the ACPI table I had shared on
> the list a long time ago for the ThinkPad Tablet 8. Is there anything that
> looks suspicious in there and that you could link to a similar gpio/irq
> polarity issue maybe?
>
> If you think there is a good chance that this could be the issue as well,
> I
> will try to build a similar patch for this ThinkPad product and share my
> results.
Just to let you know, after finding the right DMI values to simply adapt the
above patch for my ThinkPad tablet, I can confirm that a quick local kernel
modification indeed fixes the issue.
I will need a bit more time to propose a proper patch, adding this other
impacted tablet instead of replacing the above Asus one, and supporting
potentially even more products facing the same polarity issue.
Is hard-coding such exceptions / polarity issues manually the only way to go
or could there be a way to detect this programmatically instead?
Regards,
Jérôme
prev parent reply other threads:[~2016-10-06 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 22:22 Bluetooth not working anymore due to too agressive PM in hci_bcm ? (was: [PATCH v5 5/5] Bluetooth: hci_bcm: Add suspend/resume runtime PM functions) Jérôme de Bretagne
2016-10-04 7:46 ` Loic Poulain
2016-10-04 8:38 ` Marcel Holtmann
2016-10-05 21:18 ` Jérôme de Bretagne
2016-10-05 21:16 ` Jérôme de Bretagne
2016-10-06 7:03 ` Jérôme de Bretagne [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=1475737388.5772.1.camel@gmail.com \
--to=jerome.debretagne@gmail.com \
--cc=frederic.danis@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=loic.poulain@intel.com \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).