From: Catherine L <catherine.l@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: chethan.tumkur.narayan@intel.com, kiran.k@intel.com,
Catherine L <catherine.l@intel.com>
Subject: [PATCH v1 1/2] Bluetooth: btintel_pcie: Add CNVi ID for Titan Lake (Scorpius Peak2 C0)
Date: Fri, 18 Sep 2026 19:19:19 +0530 [thread overview]
Message-ID: <20260918134919.39137-1-catherine.l@intel.com> (raw)
Define BTINTEL_CNVI_SCP2_C0 (0xA11) for the Scorpius Peak2 C0 stepping
used on Titan Lake platforms and handle it in btintel_pcie_read_hwexp()
alongside existing Scorpius Peak2 variants.
Signed-off-by: Catherine L <catherine.l@intel.com>
---
drivers/bluetooth/btintel.h | 1 +
drivers/bluetooth/btintel_pcie.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/bluetooth/btintel.h b/drivers/bluetooth/btintel.h
index ef232820c31b..e51fb78ee469 100644
--- a/drivers/bluetooth/btintel.h
+++ b/drivers/bluetooth/btintel.h
@@ -61,6 +61,7 @@ struct intel_tlv {
#define BTINTEL_CNVI_BLAZARU 0x930 /* BlazarU - Meteor Lake */
#define BTINTEL_CNVI_SCP 0xA00 /* Scorpius Peak - Panther Lake */
#define BTINTEL_CNVI_SCP2 0xA10 /* Scorpius Peak2 - Nova Lake */
+#define BTINTEL_CNVI_SCP2_C0 0xA11 /* Scorpius Peak2 C0 - Titan Lake */
#define BTINTEL_CNVI_SCP2F 0xA20 /* Scorpius Peak2F - Nova Lake */
/* CNVR */
diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
index 30923eaabed7..9dbadef31324 100644
--- a/drivers/bluetooth/btintel_pcie.c
+++ b/drivers/bluetooth/btintel_pcie.c
@@ -1635,6 +1635,7 @@ static void btintel_pcie_read_hwexp(struct btintel_pcie_data *data)
break;
case BTINTEL_CNVI_SCP:
case BTINTEL_CNVI_SCP2:
+ case BTINTEL_CNVI_SCP2_C0:
case BTINTEL_CNVI_SCP2F:
break;
default:
--
2.43.0
next reply other threads:[~2026-09-18 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 13:49 Catherine L [this message]
2026-09-18 14:36 ` [v1,1/2] Bluetooth: btintel_pcie: Add CNVi ID for Titan Lake (Scorpius Peak2 C0) bluez.test.bot
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=20260918134919.39137-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox