What the patches do
Both changes are in the Bluetooth development tree and target the btintel_pcie driver. That driver handles Intel's PCIe-attached Bluetooth controllers, the kind built into recent laptop and desktop platforms.
- The CNVi ID patch. It defines BTINTEL_CNVI_SCP2_C0 (0xA11) for the Scorpius Peak2 C0 stepping used on Titan Lake platforms, and handles it in btintel_pcie_read_hwexp() alongside existing Scorpius Peak2 variants. It was authored by Intel's Catherine L. on September 18, 2026. The kernel tree records maintainer Luiz Augusto von Dentz committing it on October 14.
- The PCI ID patch. It adds PCI ID 0x9329 for Titan Lake (Scorpius Peak2 C0). The author is the same, with a patch date of October 13 and an October 14 commit. It touches only
btintel_pcie.c.
Together, the first patch teaches the driver's hardware-exception handling about the new stepping. The second lets the driver bind to the device when it shows up on the PCI bus.
A correction on the CNVi value
Wccftech's write-up gives the CNVi identifier as 0xA11B. The kernel patch text says otherwise. As quoted above, the constant is defined as 0xA11, and Wccftech's own screenshot description lists 'BTINTEL_CNVI_SCP2_C0' as '0xA11'. The trailing "B" appears to be a typo. Anyone grepping kernel sources should search for 0xA11.
The spelling of "Scorpius" also varies. The CNVi patch uses "Scorpius", and the PCI ID patch's prose does too. The code comment in the PCI patch reads "Scorpious", a spelling that also shows up in earlier Intel Bluetooth patches. It's a harmless inconsistency, but it matters if you're searching mailing lists.
What the lspci output shows
The PCI patch includes sample output from lspci -v -k -d 8086:9329. It lists the device at 02:00.0 as a Bluetooth controller, "Intel Corporation Device 9329", with subsystem device 0012. The memory region is 16K, MSI-X is enabled with a count of five, and the kernel driver in use is btintel_pcie.
That is a developer's pre-silicon or early-hardware sanity check showing the driver binding as intended. It doesn't prove a retail system exists. Note too that the device has no marketing name yet, so lspci shows only a raw ID.
Where this sits in Intel's naming lineage
Earlier patches in the same driver show the pattern. A February 2026 series from Intel's Kiran K added Scorpius Peak2 support, with a CNVi define of 0xA10 commented as Scorpius Peak2 for Nova Lake, and 0xA00 for Scorpius Peak on Panther Lake. So the 0xA11 value for the C0 stepping sits right next to the Nova Lake-era Scorpius Peak2 entry. That is circumstantial and is my own reading, not something Intel states. It suggests the Titan Lake part is a later stepping of the same Bluetooth family rather than a wholly new design.
The October 14 Bluetooth-next pull request tag lists both additions in one line, "Add PCI ID and CNVi ID for Titan Lake", among other driver changes that day. This is based on the packet's inspection of that tag, and it shows the work was grouped for the next kernel merge cycle.
What this does not tell us
Wccftech itself notes that the patches contain nothing about Titan Lake's architecture, core and clock details, or process node. I'd go further and keep these points separate:
- The patches don't state that Titan Lake follows Razor Lake. That comes from earlier reports and leaked roadmaps cited by Wccftech.
- The "Unified Core" and mobile-focus claims are likewise from that outside reporting. They are unconfirmed and not supported by the kernel changes.
- There is no launch date, SKU list, or performance data here.
Why Windows and PC readers might care
Linux driver patches are often the earliest public sign of Intel hardware, because Intel pushes support upstream well ahead of launch. Bluetooth and Wi-Fi identifiers are an especially cheap tell: they are tiny and low-risk to merge. Windows enthusiasts have long watched Linux kernel commits for exactly this reason.
The practical takeaways:
- For platform watchers: Titan Lake exists as a named target in Intel's software pipeline, at least as far as its connectivity silicon goes.
- For IT planners: nothing to act on. No hardware is available, and no Windows driver or deployment guidance has been tied to these IDs.
- For Linux users: nothing to install. Support lands through normal kernel releases, and only matters once hardware ships.
Bottom line
Two tiny commits, one real signal: Intel's upstream Bluetooth driver now recognizes a Scorpius Peak2 C0 device explicitly labelled for Titan Lake. Treat the CNVi value as 0xA11, not 0xA11B, and treat everything else about Titan Lake as rumor until Intel says otherwise.
References
- Intel’s Post-Razor Lake Titan Lake Platform Shows Up In Two Linux Bluetooth Patches, With PCI ID 0x9329 Labelled ‘Scorpius Peak2 C0, Titan Lake’ - Wccftech Wccftech · 2026-11-18T13:21:31+00:00
- (PW_SID:1168712) (v1,1/2) Bluetooth: btintel_pcie: Add CNVi ID for Titan Lake (Scorpius Peak2 C0) by BluezTestBot · Pull Request #793 · bluez/bluetooth-next · GitHub github.com
- 7de1fcfb783b0633684c0eff0c18d6f4e12e8954 - pub/scm/linux/kernel/git/bluetooth/bluetooth-next - Git at Google kernel.googlesource.com