From: Loic Poulain <loic.poulain@intel.com>
To: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>
Cc: Ilya Faenson <ilya.faenson@broadcom.com>,
linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: Broadcom BCM4324(1) rev B5 chipset - Bluetooth support in Linux Kernel 4.x ?
Date: Mon, 07 Mar 2016 16:06:20 +0100 [thread overview]
Message-ID: <56DD98EC.1060504@intel.com> (raw)
In-Reply-To: <CA+kEDGF7MaWNW_8jRintsGgnfCa=rp251dtxyrvpQHp7RusYiw@mail.gmail.com>
Hi Jerome
> What about the other ACPI ID (BCM2E3C) that I've found in the ACPI
> table of that ThinkPad 8 tablet? Is it included in its table to cover
> another HW variant of that product, using a different Broadcom
> chipset? Any value for you if I create a similar patch (without being
> able to test it)? I guess the answer will be "No" from your message
> above but just let me know.
Yes, ACPI table is often filled with different optional components so
that it can be compatible with several platform variants without impact
on the ACPI data. Then, components are enabled/disabled depending board ID.
This BCM2E3C is disabled on your platform, but seems compatible with
hci_bcm UART driver (2GPIOs + 1IRQ). Should be only a revision of BCM2Ex.
Broadcom input is welcome here.
Regards,
Loic
--
Intel Open Source Technology Center
http://oss.intel.com/
prev parent reply other threads:[~2016-03-07 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+kEDGEHfsODon6aOdLU86E9c0Lfs-4bo=ycEZz3MdEa1qLrKw@mail.gmail.com>
2016-02-22 9:17 ` Broadcom BCM4324(1) rev B5 chipset - Bluetooth support in Linux Kernel 4.x ? Arend Van Spriel
2016-02-28 17:56 ` Jérôme de Bretagne
2016-02-28 18:23 ` Jérôme de Bretagne
2016-02-28 19:54 ` Loic Poulain
[not found] ` <CA+kEDGHbzH9VPRUaz5-JPsU5kHTDk8UwGGmt94rGVXiG1KY-Ow@mail.gmail.com>
2016-02-28 22:58 ` Loic Poulain
2016-03-06 13:22 ` Jérôme de Bretagne
2016-03-07 9:42 ` Loic Poulain
2016-03-07 10:48 ` Jérôme de Bretagne
2016-03-07 15:06 ` Loic Poulain [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=56DD98EC.1060504@intel.com \
--to=loic.poulain@intel.com \
--cc=ilya.faenson@broadcom.com \
--cc=jerome.debretagne@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--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).