From: Catherine L <catherine.l@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: kiran.k@intel.com, chethan.tumkur.narayan@intel.com,
Catherine L <catherine.l@intel.com>
Subject: [RESEND v1] Bluetooth: btintel_pcie: Add PCI ID for Titan Lake
Date: Tue, 13 Oct 2026 15:06:50 +0530 [thread overview]
Message-ID: <20261013093650.423572-1-catherine.l@intel.com> (raw)
Add PCI ID 0x9329 for Titan Lake (Scorpius Peak2 C0).
sudo lspci -v -k -d 8086:9329
02:00.0 Bluetooth: Intel Corporation Device 9329
Subsystem: Intel Corporation Device 0012
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at fe000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=5 Masked-
Kernel driver in use: btintel_pcie
Kernel modules: btintel_pcie
Signed-off-by: Catherine L <catherine.l@intel.com>
---
drivers/bluetooth/btintel_pcie.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
index 3a555aa50c87..91b1ee9d6010 100644
--- a/drivers/bluetooth/btintel_pcie.c
+++ b/drivers/bluetooth/btintel_pcie.c
@@ -59,6 +59,8 @@ static const struct pci_device_id btintel_pcie_table[] = {
/* Draco */
{ BTINTEL_PCI_DEVICE(0x2731, PCI_ANY_ID) },
{ BTINTEL_PCI_DEVICE(0x2732, PCI_ANY_ID) },
+ /* Scorpious Peak2 C0, Titan Lake */
+ { BTINTEL_PCI_DEVICE(0x9329, PCI_ANY_ID) },
{ 0 }
};
MODULE_DEVICE_TABLE(pci, btintel_pcie_table);
--
2.43.0
next reply other threads:[~2026-10-13 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:36 Catherine L [this message]
2026-10-13 11:55 ` [RESEND,v1] Bluetooth: btintel_pcie: Add PCI ID for Titan Lake bluez.test.bot
2026-10-13 15:10 ` [RESEND v1] " patchwork-bot+bluetooth
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=20261013093650.423572-1-catherine.l@intel.com \
--to=catherine.l@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--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.