* [PATCH v1] Bluetooth: btintel: Add support for BlazarIW core
@ 2025-07-23 13:44 Kiran K
2025-07-23 14:14 ` [v1] " bluez.test.bot
2025-07-23 19:53 ` [PATCH v1] " Luiz Augusto von Dentz
0 siblings, 2 replies; 5+ messages in thread
From: Kiran K @ 2025-07-23 13:44 UTC (permalink / raw)
To: linux-bluetooth; +Cc: ravishankar.srivatsa, Kiran K, Vijay Satija
Add support for the BlazarIW Bluetooth core used in the Wildcat Lake
platform.
dmesg:
Bluetooth: Core ver 2.22
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Bluetooth: hci0: Device revision is 0
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is disabled
Bluetooth: hci0: API lock is disabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995
Bluetooth: hci0: Found device firmware: intel/ibt-1190-00a1-iml.sfi
Bluetooth: hci0: Boot Address: 0x30098800
Bluetooth: hci0: Firmware Version: 184-28.25
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 67426 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 2248 usecs
Bluetooth: hci0: Waiting for device transition to d0
Bluetooth: hci0: Device moved to D0 in 0 usecs
Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0f
Bluetooth: hci0: Found device firmware: intel/ibt-1190-00a1-pci.sfi
Bluetooth: hci0: Boot Address: 0x10000800
Bluetooth: hci0: Firmware Version: 184-28.25
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 510990 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 39057 usecs
Bluetooth: hci0: Waiting for device transition to d0
Bluetooth: hci0: Device moved to D0 in 88 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-1190-00a1-pci.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware timestamp 2025.28 buildtype 1 build 96440
Bluetooth: hci0: Firmware SHA1: 0x34b85c16
Bluetooth: hci0: Fseq status: Success (0x00)
Bluetooth: hci0: Fseq executed: 00.98.00.05
Bluetooth: hci0: Fseq BT Top: 00.98.00.05
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: MGMT ver 1.23
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Signed-off-by: Vijay Satija <vijay.satija@intel.com>
Signed-off-by: Kiran K <kiran.k@intel.com>
---
drivers/bluetooth/btintel.c | 3 +++
drivers/bluetooth/btintel_pcie.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
index be69d21c9aa7..9d29ab811f80 100644
--- a/drivers/bluetooth/btintel.c
+++ b/drivers/bluetooth/btintel.c
@@ -484,6 +484,7 @@ int btintel_version_info_tlv(struct hci_dev *hdev,
case 0x1d: /* BlazarU (BzrU) */
case 0x1e: /* BlazarI (Bzr) */
case 0x1f: /* Scorpious Peak */
+ case 0x22: /* BlazarIW (BzrIW) */
break;
default:
bt_dev_err(hdev, "Unsupported Intel hardware variant (0x%x)",
@@ -3253,6 +3254,7 @@ void btintel_set_msft_opcode(struct hci_dev *hdev, u8 hw_variant)
case 0x1d:
case 0x1e:
case 0x1f:
+ case 0x22:
hci_set_msft_opcode(hdev, 0xFC1E);
break;
default:
@@ -3593,6 +3595,7 @@ static int btintel_setup_combined(struct hci_dev *hdev)
case 0x1d:
case 0x1e:
case 0x1f:
+ case 0x22:
/* Display version information of TLV type */
btintel_version_info_tlv(hdev, &ver_tlv);
diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
index 6e7bbbd35279..d08f59ae7720 100644
--- a/drivers/bluetooth/btintel_pcie.c
+++ b/drivers/bluetooth/btintel_pcie.c
@@ -2149,6 +2149,7 @@ static int btintel_pcie_setup_internal(struct hci_dev *hdev)
switch (INTEL_HW_VARIANT(ver_tlv.cnvi_bt)) {
case 0x1e: /* BzrI */
case 0x1f: /* ScP */
+ case 0x22: /* BzrIW */
/* Display version information of TLV type */
btintel_version_info_tlv(hdev, &ver_tlv);
--
2.43.0
^ permalink raw reply related [flat|nested] 5+ messages in thread* RE: [v1] Bluetooth: btintel: Add support for BlazarIW core
2025-07-23 13:44 [PATCH v1] Bluetooth: btintel: Add support for BlazarIW core Kiran K
@ 2025-07-23 14:14 ` bluez.test.bot
2025-07-23 19:53 ` [PATCH v1] " Luiz Augusto von Dentz
1 sibling, 0 replies; 5+ messages in thread
From: bluez.test.bot @ 2025-07-23 14:14 UTC (permalink / raw)
To: linux-bluetooth, kiran.k
[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=985135
---Test result---
Test Summary:
CheckPatch PENDING 0.31 seconds
GitLint PENDING 0.30 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 24.18 seconds
CheckAllWarning PASS 29.81 seconds
CheckSparse PASS 29.90 seconds
BuildKernel32 PASS 24.30 seconds
TestRunnerSetup PASS 473.54 seconds
TestRunner_l2cap-tester PASS 25.30 seconds
TestRunner_iso-tester PASS 42.63 seconds
TestRunner_bnep-tester PASS 6.19 seconds
TestRunner_mgmt-tester FAIL 135.30 seconds
TestRunner_rfcomm-tester PASS 9.46 seconds
TestRunner_sco-tester PASS 14.88 seconds
TestRunner_ioctl-tester PASS 10.33 seconds
TestRunner_mesh-tester FAIL 11.63 seconds
TestRunner_smp-tester PASS 8.84 seconds
TestRunner_userchan-tester PASS 6.45 seconds
IncrementalBuild PENDING 0.64 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
LL Privacy - Start Discovery 1 (Disable RL) Failed 0.186 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.072 seconds
Mesh - Send cancel - 2 Timed out 1.996 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v1] Bluetooth: btintel: Add support for BlazarIW core
2025-07-23 13:44 [PATCH v1] Bluetooth: btintel: Add support for BlazarIW core Kiran K
2025-07-23 14:14 ` [v1] " bluez.test.bot
@ 2025-07-23 19:53 ` Luiz Augusto von Dentz
2025-07-24 11:58 ` K, Kiran
1 sibling, 1 reply; 5+ messages in thread
From: Luiz Augusto von Dentz @ 2025-07-23 19:53 UTC (permalink / raw)
To: Kiran K; +Cc: linux-bluetooth, ravishankar.srivatsa, Vijay Satija
Hi Kiran,
On Wed, Jul 23, 2025 at 9:34 AM Kiran K <kiran.k@intel.com> wrote:
>
> Add support for the BlazarIW Bluetooth core used in the Wildcat Lake
> platform.
>
> dmesg:
> Bluetooth: Core ver 2.22
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: SCO socket layer initialized
> Bluetooth: hci0: Device revision is 0
> Bluetooth: hci0: Secure boot is enabled
> Bluetooth: hci0: OTP lock is disabled
> Bluetooth: hci0: API lock is disabled
> Bluetooth: hci0: Debug lock is disabled
> Bluetooth: hci0: Minimum firmware build 1 week 10 2014
> Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995
> Bluetooth: hci0: Found device firmware: intel/ibt-1190-00a1-iml.sfi
> Bluetooth: hci0: Boot Address: 0x30098800
> Bluetooth: hci0: Firmware Version: 184-28.25
> Bluetooth: hci0: Waiting for firmware download to complete
> Bluetooth: hci0: Firmware loaded in 67426 usecs
> Bluetooth: hci0: Waiting for device to boot
> Bluetooth: hci0: Device booted in 2248 usecs
> Bluetooth: hci0: Waiting for device transition to d0
> Bluetooth: hci0: Device moved to D0 in 0 usecs
> Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0f
> Bluetooth: hci0: Found device firmware: intel/ibt-1190-00a1-pci.sfi
> Bluetooth: hci0: Boot Address: 0x10000800
> Bluetooth: hci0: Firmware Version: 184-28.25
> Bluetooth: hci0: Waiting for firmware download to complete
> Bluetooth: hci0: Firmware loaded in 510990 usecs
> Bluetooth: hci0: Waiting for device to boot
> Bluetooth: hci0: Device booted in 39057 usecs
> Bluetooth: hci0: Waiting for device transition to d0
> Bluetooth: hci0: Device moved to D0 in 88 usecs
> Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-1190-00a1-pci.ddc
> Bluetooth: hci0: Applying Intel DDC parameters completed
> Bluetooth: hci0: Firmware timestamp 2025.28 buildtype 1 build 96440
> Bluetooth: hci0: Firmware SHA1: 0x34b85c16
> Bluetooth: hci0: Fseq status: Success (0x00)
> Bluetooth: hci0: Fseq executed: 00.98.00.05
> Bluetooth: hci0: Fseq BT Top: 00.98.00.05
> Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> Bluetooth: BNEP filters: protocol multicast
> Bluetooth: BNEP socket layer initialized
> Bluetooth: MGMT ver 1.23
> Bluetooth: RFCOMM TTY layer initialized
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM ver 1.11
lspci is probably better than dmesg when adding new models since what
matters here, or there is no change in the lspci? If it doesn't them
it probably better to add the response of Read Version TLV, we do have
decoding of it:
https://github.com/bluez/bluez/blob/3c0693c5d22606f786da4389103740424a04213b/monitor/intel.c#L297
Perhaps we should add a decoding for the version code name rather than
just print version number, anyway dmesg is just not useful in general
and we actually should reduce the amount of information we print there
using bt_dev_info.
> Signed-off-by: Vijay Satija <vijay.satija@intel.com>
> Signed-off-by: Kiran K <kiran.k@intel.com>
> ---
> drivers/bluetooth/btintel.c | 3 +++
> drivers/bluetooth/btintel_pcie.c | 1 +
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
> index be69d21c9aa7..9d29ab811f80 100644
> --- a/drivers/bluetooth/btintel.c
> +++ b/drivers/bluetooth/btintel.c
> @@ -484,6 +484,7 @@ int btintel_version_info_tlv(struct hci_dev *hdev,
> case 0x1d: /* BlazarU (BzrU) */
> case 0x1e: /* BlazarI (Bzr) */
> case 0x1f: /* Scorpious Peak */
> + case 0x22: /* BlazarIW (BzrIW) */
> break;
> default:
> bt_dev_err(hdev, "Unsupported Intel hardware variant (0x%x)",
> @@ -3253,6 +3254,7 @@ void btintel_set_msft_opcode(struct hci_dev *hdev, u8 hw_variant)
> case 0x1d:
> case 0x1e:
> case 0x1f:
> + case 0x22:
> hci_set_msft_opcode(hdev, 0xFC1E);
> break;
> default:
> @@ -3593,6 +3595,7 @@ static int btintel_setup_combined(struct hci_dev *hdev)
> case 0x1d:
> case 0x1e:
> case 0x1f:
> + case 0x22:
> /* Display version information of TLV type */
> btintel_version_info_tlv(hdev, &ver_tlv);
>
> diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
> index 6e7bbbd35279..d08f59ae7720 100644
> --- a/drivers/bluetooth/btintel_pcie.c
> +++ b/drivers/bluetooth/btintel_pcie.c
> @@ -2149,6 +2149,7 @@ static int btintel_pcie_setup_internal(struct hci_dev *hdev)
> switch (INTEL_HW_VARIANT(ver_tlv.cnvi_bt)) {
> case 0x1e: /* BzrI */
> case 0x1f: /* ScP */
> + case 0x22: /* BzrIW */
> /* Display version information of TLV type */
> btintel_version_info_tlv(hdev, &ver_tlv);
>
> --
> 2.43.0
>
>
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 5+ messages in thread* RE: [PATCH v1] Bluetooth: btintel: Add support for BlazarIW core
2025-07-23 19:53 ` [PATCH v1] " Luiz Augusto von Dentz
@ 2025-07-24 11:58 ` K, Kiran
0 siblings, 0 replies; 5+ messages in thread
From: K, Kiran @ 2025-07-24 11:58 UTC (permalink / raw)
To: Luiz Augusto von Dentz
Cc: linux-bluetooth@vger.kernel.org, Srivatsa, Ravishankar,
Vijay Satija
Hi Luiz,
>-----Original Message-----
>From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
>Sent: Thursday, July 24, 2025 1:24 AM
>To: K, Kiran <kiran.k@intel.com>
>Cc: linux-bluetooth@vger.kernel.org; Srivatsa, Ravishankar
><ravishankar.srivatsa@intel.com>; Vijay Satija <vijay.satija@intel.com>
>Subject: Re: [PATCH v1] Bluetooth: btintel: Add support for BlazarIW core
>
>Hi Kiran,
>
>On Wed, Jul 23, 2025 at 9:34 AM Kiran K <kiran.k@intel.com> wrote:
>>
>> Add support for the BlazarIW Bluetooth core used in the Wildcat Lake
>> platform.
>>
>> dmesg:
>> Bluetooth: Core ver 2.22
>> Bluetooth: HCI device and connection manager initialized
>> Bluetooth: HCI socket layer initialized
>> Bluetooth: L2CAP socket layer initialized
>> Bluetooth: SCO socket layer initialized
>> Bluetooth: hci0: Device revision is 0
>> Bluetooth: hci0: Secure boot is enabled
>> Bluetooth: hci0: OTP lock is disabled
>> Bluetooth: hci0: API lock is disabled
>> Bluetooth: hci0: Debug lock is disabled
>> Bluetooth: hci0: Minimum firmware build 1 week 10 2014
>> Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995
>> Bluetooth: hci0: Found device firmware: intel/ibt-1190-00a1-iml.sfi
>> Bluetooth: hci0: Boot Address: 0x30098800
>> Bluetooth: hci0: Firmware Version: 184-28.25
>> Bluetooth: hci0: Waiting for firmware download to complete
>> Bluetooth: hci0: Firmware loaded in 67426 usecs
>> Bluetooth: hci0: Waiting for device to boot
>> Bluetooth: hci0: Device booted in 2248 usecs
>> Bluetooth: hci0: Waiting for device transition to d0
>> Bluetooth: hci0: Device moved to D0 in 0 usecs
>> Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0f
>> Bluetooth: hci0: Found device firmware: intel/ibt-1190-00a1-pci.sfi
>> Bluetooth: hci0: Boot Address: 0x10000800
>> Bluetooth: hci0: Firmware Version: 184-28.25
>> Bluetooth: hci0: Waiting for firmware download to complete
>> Bluetooth: hci0: Firmware loaded in 510990 usecs
>> Bluetooth: hci0: Waiting for device to boot
>> Bluetooth: hci0: Device booted in 39057 usecs
>> Bluetooth: hci0: Waiting for device transition to d0
>> Bluetooth: hci0: Device moved to D0 in 88 usecs
>> Bluetooth: hci0: Found Intel DDC parameters:
>> intel/ibt-1190-00a1-pci.ddc
>> Bluetooth: hci0: Applying Intel DDC parameters completed
>> Bluetooth: hci0: Firmware timestamp 2025.28 buildtype 1 build 96440
>> Bluetooth: hci0: Firmware SHA1: 0x34b85c16
>> Bluetooth: hci0: Fseq status: Success (0x00)
>> Bluetooth: hci0: Fseq executed: 00.98.00.05
>> Bluetooth: hci0: Fseq BT Top: 00.98.00.05
>> Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>> Bluetooth: BNEP filters: protocol multicast
>> Bluetooth: BNEP socket layer initialized
>> Bluetooth: MGMT ver 1.23
>> Bluetooth: RFCOMM TTY layer initialized
>> Bluetooth: RFCOMM socket layer initialized
>> Bluetooth: RFCOMM ver 1.11
>
>lspci is probably better than dmesg when adding new models since what
>matters here, or there is no change in the lspci? If it doesn't them it probably
Hardware variant is intel specific and it doesn’t show up in lscpi coutput.
>better to add the response of Read Version TLV, we do have decoding of it:
>
>https://github.com/bluez/bluez/blob/3c0693c5d22606f786da4389103740424a
>04213b/monitor/intel.c#L297
>
>Perhaps we should add a decoding for the version code name rather than just
>print version number, anyway dmesg is just not useful in general and we
>actually should reduce the amount of information we print there using
>bt_dev_info.
>
I will add the support in monitor to decode cnvi name and include the hci traces in commit message.
>
>> Signed-off-by: Vijay Satija <vijay.satija@intel.com>
>> Signed-off-by: Kiran K <kiran.k@intel.com>
>> ---
>> drivers/bluetooth/btintel.c | 3 +++
>> drivers/bluetooth/btintel_pcie.c | 1 +
>> 2 files changed, 4 insertions(+)
>>
>> diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
>> index be69d21c9aa7..9d29ab811f80 100644
>> --- a/drivers/bluetooth/btintel.c
>> +++ b/drivers/bluetooth/btintel.c
>> @@ -484,6 +484,7 @@ int btintel_version_info_tlv(struct hci_dev *hdev,
>> case 0x1d: /* BlazarU (BzrU) */
>> case 0x1e: /* BlazarI (Bzr) */
>> case 0x1f: /* Scorpious Peak */
>> + case 0x22: /* BlazarIW (BzrIW) */
>> break;
>> default:
>> bt_dev_err(hdev, "Unsupported Intel hardware variant
>> (0x%x)", @@ -3253,6 +3254,7 @@ void btintel_set_msft_opcode(struct
>hci_dev *hdev, u8 hw_variant)
>> case 0x1d:
>> case 0x1e:
>> case 0x1f:
>> + case 0x22:
>> hci_set_msft_opcode(hdev, 0xFC1E);
>> break;
>> default:
>> @@ -3593,6 +3595,7 @@ static int btintel_setup_combined(struct hci_dev
>*hdev)
>> case 0x1d:
>> case 0x1e:
>> case 0x1f:
>> + case 0x22:
>> /* Display version information of TLV type */
>> btintel_version_info_tlv(hdev, &ver_tlv);
>>
>> diff --git a/drivers/bluetooth/btintel_pcie.c
>> b/drivers/bluetooth/btintel_pcie.c
>> index 6e7bbbd35279..d08f59ae7720 100644
>> --- a/drivers/bluetooth/btintel_pcie.c
>> +++ b/drivers/bluetooth/btintel_pcie.c
>> @@ -2149,6 +2149,7 @@ static int btintel_pcie_setup_internal(struct hci_dev
>*hdev)
>> switch (INTEL_HW_VARIANT(ver_tlv.cnvi_bt)) {
>> case 0x1e: /* BzrI */
>> case 0x1f: /* ScP */
>> + case 0x22: /* BzrIW */
>> /* Display version information of TLV type */
>> btintel_version_info_tlv(hdev, &ver_tlv);
>>
>> --
>> 2.43.0
>>
>>
>
>
>--
>Luiz Augusto von Dentz
Thanks,
Kiran
^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH v1] Bluetooth: btintel: Add support for BlazarIW core
@ 2025-07-23 6:26 Kiran K
2025-07-23 6:43 ` [v1] " bluez.test.bot
0 siblings, 1 reply; 5+ messages in thread
From: Kiran K @ 2025-07-23 6:26 UTC (permalink / raw)
To: linux-bluetooth; +Cc: ravishankar.srivatsa, Kiran K, Vijay Satija
Need to add support for BlazarIW Bluetooth core used in Wildcat Lake
platform.
Signed-off-by: Vijay Satija <vijay.satija@intel.com>
Signed-off-by: Kiran K <kiran.k@intel.com>
---
drivers/bluetooth/btintel.c | 3 +++
drivers/bluetooth/btintel_pcie.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
index be69d21c9aa7..ea1521c6b2d3 100644
--- a/drivers/bluetooth/btintel.c
+++ b/drivers/bluetooth/btintel.c
@@ -484,6 +484,7 @@ int btintel_version_info_tlv(struct hci_dev *hdev,
case 0x1d: /* BlazarU (BzrU) */
case 0x1e: /* BlazarI (Bzr) */
case 0x1f: /* Scorpious Peak */
+ case 0x22: /* BlazarIW (BzrIW */
break;
default:
bt_dev_err(hdev, "Unsupported Intel hardware variant (0x%x)",
@@ -3253,6 +3254,7 @@ void btintel_set_msft_opcode(struct hci_dev *hdev, u8 hw_variant)
case 0x1d:
case 0x1e:
case 0x1f:
+ case 0x22:
hci_set_msft_opcode(hdev, 0xFC1E);
break;
default:
@@ -3593,6 +3595,7 @@ static int btintel_setup_combined(struct hci_dev *hdev)
case 0x1d:
case 0x1e:
case 0x1f:
+ case 0x22:
/* Display version information of TLV type */
btintel_version_info_tlv(hdev, &ver_tlv);
diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
index 6e7bbbd35279..d08f59ae7720 100644
--- a/drivers/bluetooth/btintel_pcie.c
+++ b/drivers/bluetooth/btintel_pcie.c
@@ -2149,6 +2149,7 @@ static int btintel_pcie_setup_internal(struct hci_dev *hdev)
switch (INTEL_HW_VARIANT(ver_tlv.cnvi_bt)) {
case 0x1e: /* BzrI */
case 0x1f: /* ScP */
+ case 0x22: /* BzrIW */
/* Display version information of TLV type */
btintel_version_info_tlv(hdev, &ver_tlv);
--
2.43.0
^ permalink raw reply related [flat|nested] 5+ messages in thread* RE: [v1] Bluetooth: btintel: Add support for BlazarIW core
2025-07-23 6:26 Kiran K
@ 2025-07-23 6:43 ` bluez.test.bot
0 siblings, 0 replies; 5+ messages in thread
From: bluez.test.bot @ 2025-07-23 6:43 UTC (permalink / raw)
To: linux-bluetooth, kiran.k
[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=984974
---Test result---
Test Summary:
CheckPatch PENDING 0.29 seconds
GitLint PENDING 0.21 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 24.06 seconds
CheckAllWarning PASS 26.65 seconds
CheckSparse PASS 30.00 seconds
BuildKernel32 PASS 24.11 seconds
TestRunnerSetup PASS 471.66 seconds
TestRunner_l2cap-tester PASS 25.25 seconds
TestRunner_iso-tester PASS 40.21 seconds
TestRunner_bnep-tester PASS 6.16 seconds
TestRunner_mgmt-tester FAIL 133.14 seconds
TestRunner_rfcomm-tester PASS 9.54 seconds
TestRunner_sco-tester PASS 14.99 seconds
TestRunner_ioctl-tester PASS 10.14 seconds
TestRunner_mesh-tester FAIL 11.69 seconds
TestRunner_smp-tester PASS 8.65 seconds
TestRunner_userchan-tester PASS 6.42 seconds
IncrementalBuild PENDING 0.95 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
LL Privacy - Set Device Flag 1 (Device Privacy) Failed 0.156 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.160 seconds
Mesh - Send cancel - 2 Timed out 1.989 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2025-07-24 11:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-23 13:44 [PATCH v1] Bluetooth: btintel: Add support for BlazarIW core Kiran K
2025-07-23 14:14 ` [v1] " bluez.test.bot
2025-07-23 19:53 ` [PATCH v1] " Luiz Augusto von Dentz
2025-07-24 11:58 ` K, Kiran
-- strict thread matches above, loose matches on Subject: below --
2025-07-23 6:26 Kiran K
2025-07-23 6:43 ` [v1] " bluez.test.bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox