Add support for Qualcomm QCA639x chips family
Subsystems (6)
v3 cover Add support for Qualcomm QCA639x chips family
Qualcomm QCA639x is a family of WiFi + Bluetooth chips, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks use common power management unit wich should be turned on before either of devices can be probed. Add common 'qcom-qca6390' driver providing regulator to be used by both BT and PCIe parts.
Changes since v2:
- Rebase on top of linux-next to get wcn6750 changes.
- Switch from misc device providing power domains into regulator code.
- Use vddpe-3v3-supply as expected by pcie-qcom driver.
- Use enable_gpio functionality in hci_qca driver.
Changes since v1:
- Stopped using wildcard in the dts binding, stick to qcom,qca6390.
- Stopped using pcie0_phy for qca639x power domain.
- Describe root PCIe bridge in the dts and bind power domain to the bridge.
- Add pci quirk to power up power domains connected to this bridge.
----------------------------------------------------------------
Dmitry Baryshkov (7):
dt-bindings: regulator: qcom,qca6390: add binding for QCA6390 device
regulator: qca6390: add support for QCA639x powerup sequence
Bluetooth: hci_qca: provide default device data
Bluetooth: hci_qca: merge qca_power into qca_serdev
Bluetooth: hci_qca: merge wcn & non-wcn code paths
Bluetooth: hci_qca: add power sequencer support to qca6390
arm64: dts: qcom: qrb5165-rb5: add QCA6391 WiFi+BT SoC
.../bindings/regulator/qcom,qca6390.yaml | 70 +++++++ arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 56 +++++ drivers/bluetooth/hci_qca.c | 225 ++++++++++----------- drivers/regulator/Kconfig | 13 ++ drivers/regulator/Makefile | 1 + drivers/regulator/qcom-qca639x.c | 157 ++++++++++++++ 6 files changed, 401 insertions(+), 121 deletions(-) create mode 100644 Documentation/devicetree/bindings/regulator/qcom,qca6390.yaml create mode 100644 drivers/regulator/qcom-qca639x.c
PATCH v3 1/7 dt-bindings: regulator: qcom,qca6390: add binding for QCA6390 device
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add binding to describe power sequencing required to power up this device.
--- .../bindings/regulator/qcom,qca6390.yaml | 70 +++++++++++++++++++ 1 file changed, 70 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/qcom,qca6390.yaml
Documentation/devicetree/bindings/regulator/qcom,qca6390.yaml new file +70 -0
@@ -0,0 +1,70 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: "http://devicetree.org/schemas/regulator/qcom,qca6390.yaml#" +$schema: "http://devicetree.org/meta-schemas/core.yaml#" + +title: Qualcomm QCA6390 WiFi + Bluetoot SoC bindings + +maintainers: + - Andy Gross <[email protected]> + - Bjorn Andersson <[email protected]> + +description: | + This binding describes thes Qualcomm QCA6390 or QCA6391 power supplies and + enablement pins. + +properties: + compatible: + const: qcom,qca6390 + + vddaon-supply: + description: + 0.95V always-on LDO power input + + vddpmu-supply: + description: + 0.95V LDO power input to PMU + + vddrfa1-supply: + description: + 0.95V LDO power input to RFA + + vddrfa2-supply: + description: + 1.25V LDO power input to RFA + + vddrfa3-supply: + description: + 2V LDO power input to RFA + + vddpcie1-supply: + description: + 1.25V LDO power input to PCIe part + + vddpcie2-supply: + description: + 2V LDO power input to PCIe part + + vddio-supply: + description: + 1.8V VIO input + +additionalProperties: false + +examples: + - | + #include <dt-bindings/gpio/gpio.h> + qca6390: qca6390 { + compatible = "qcom,qca6390"; + + vddaon-supply = <&vreg_s6a_0p95>; + vddpmu-supply = <&vreg_s2f_0p95>; + vddrfa1-supply = <&vreg_s2f_0p95>; + vddrfa2-supply = <&vreg_s8c_1p3>; + vddrfa3-supply = <&vreg_s5a_1p9>; + vddpcie1-supply = <&vreg_s8c_1p3>; + vddpcie2-supply = <&vreg_s5a_1p9>; + vddio-supply = <&vreg_s4a_1p8>; + }; +...
Signature · 1 line
2.30.2
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=504629
---Test result---
Test Summary:
CheckPatch FAIL 1.51 seconds GitLint PASS 0.87 seconds BuildKernel PASS 618.69 seconds TestRunner: Setup PASS 403.43 seconds TestRunner: l2cap-tester PASS 2.93 seconds TestRunner: bnep-tester PASS 2.06 seconds TestRunner: mgmt-tester PASS 29.40 seconds TestRunner: rfcomm-tester PASS 2.31 seconds TestRunner: sco-tester PASS 2.22 seconds TestRunner: smp-tester PASS 2.30 seconds TestRunner: userchan-tester PASS 2.09 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.51 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
dt-bindings: regulator: qcom,qca6390: add binding for QCA6390 device
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #15:
new file mode 100644
total: 0 errors, 1 warnings, 70 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] dt-bindings: regulator: qcom,qca6390: add binding for QCA6390" has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
regulator: qca6390: add support for QCA639x powerup sequence
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #50:
new file mode 100644
total: 0 errors, 1 warnings, 183 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] regulator: qca6390: add support for QCA639x powerup sequence" has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - PASS - 0.87 seconds
Run gitlint with rule in .gitlint
##############################
Test: BuildKernel - PASS - 618.69 seconds
Build Kernel with minimal configuration supports Bluetooth
##############################
Test: TestRunner: Setup - PASS - 403.43 seconds
Setup environment for running Test Runner
##############################
Test: TestRunner: l2cap-tester - PASS - 2.93 seconds Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: bnep-tester - PASS - 2.06 seconds Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: mgmt-tester - PASS - 29.40 seconds Run test-runner with mgmt-tester
Total: 446, Passed: 433 (97.1%), Failed: 0, Not Run: 13
##############################
Test: TestRunner: rfcomm-tester - PASS - 2.31 seconds Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: sco-tester - PASS - 2.22 seconds Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: smp-tester - PASS - 2.30 seconds Run test-runner with smp-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: userchan-tester - PASS - 2.09 seconds Run test-runner with userchan-tester
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0
---
Regards,
Linux Bluetooth
c[?7l[2JSeaBIOS (version 1.13.0-1ubuntu1.1) Booting from ROM..c[?7l[2Jearly console in extract_kernelinput_data: 0x0000000001e782e0input_len: 0x000000000036171d
output: 0x0000000001000000output_len: 0x00000000011a722ckernel_total_size: 0x0000000001030000needed_size: 0x0000000001200000trampoline_32bit: 0x000000000009d000
Physical KASLR using RDTSC...
Virtual KASLR using RDTSC...
Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel.
Linux version 5.12.0-g72a0f235d09c (root@3eb00f0dfff0) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #2 Mon Jun 21 23:10:12 UTC 2021
Command line: console=ttyS0,115200n8 earlyprintk=serial rootfstype=9p rootflags=trans=virtio,version=9p2000.L acpi=off pci=noacpi noapic quiet ro init=/github/workspace/bluez/tools/test-runner bluetooth.enable_ecred=1TESTHOME=/github/workspace TESTDBUS=0 TESTMONITOR=0 TESTDEVS=0 TESTAUTO=0 TESTARGS='/github/workspace/bluez/tools/l2cap-tester' x86/fpu: x87 FPU will use FXSAVE
BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000000bffdfff] usable
BIOS-e820: [mem 0x000000000bffe000-0x000000000bffffff] reserved
BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
printk: bootconsole [earlyser0] enabled
Memory KASLR using RDTSC...
Poking KASLR using RDTSC...
Mounting sysfs to /sys
Mounting proc to /proc
Mounting devtmpfs to /dev
Creating /dev/pts
Mounting devpts to /dev/pts
Creating /dev/shm
Mounting tmpfs to /dev/shm
Mounting tmpfs to /run
Mounting tmpfs to /tmp
Mounting debugfs to /sys/kernel/debug
Linking /dev/fd to /proc/self/fd
Linking /dev/stdin to /proc/self/fd/0
Linking /dev/stdout to /proc/self/fd/1
Linking /dev/stderr to /proc/self/fd/2
Creating new session group leader
Setting controlling terminal
Creating /var/lib/bluetooth
Failed to create filesystem: No such file or directory
Creating /etc/bluetooth
Failed to create filesystem: No such file or directory
Creating /etc/dbus-1
Failed to create filesystem: No such file or directory
Creating /usr/share/dbus-1
Running command /github/workspace/bluez/tools/l2cap-tester
New process 41 created
Changing into directory /github/workspace
Basic L2CAP Socket - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Basic L2CAP Socket - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
Basic L2CAP Socket - Success - setup complete
Basic L2CAP Socket - Success - run
Basic L2CAP Socket - Success - test passed
Basic L2CAP Socket - Success - teardown
Index Removed callback
Index: 0x0000
Basic L2CAP Socket - Success - teardown complete
Basic L2CAP Socket - Success - done
Non-connected getpeername - Failure - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Non-connected getpeername - Failure - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
Non-connected getpeername - Failure - setup complete Non-connected getpeername - Failure - run Non-connected getpeername - Failure - test passed Non-connected getpeername - Failure - teardown
Index Removed callback
Index: 0x0000
Non-connected getpeername - Failure - teardown complete Non-connected getpeername - Failure - done
L2CAP BR/EDR Client - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP BR/EDR Client - Success - setup complete
L2CAP BR/EDR Client - Success - run
Connect in progress
Successfully connected
L2CAP BR/EDR Client - Success - test passed
L2CAP BR/EDR Client - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client - Success - teardown complete
L2CAP BR/EDR Client - Success - done
L2CAP BR/EDR Client SSP - Success 1 - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client SSP - Success 1 - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
Client enable SSP status 0x00
L2CAP BR/EDR Client SSP - Success 1 - setup complete L2CAP BR/EDR Client SSP - Success 1 - run
Connect in progress
Successfully connected
L2CAP BR/EDR Client SSP - Success 1 - test passed L2CAP BR/EDR Client SSP - Success 1 - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client SSP - Success 1 - teardown complete L2CAP BR/EDR Client SSP - Success 1 - done
L2CAP BR/EDR Client SSP - Success 2 - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client SSP - Success 2 - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
Client enable SSP status 0x00
L2CAP BR/EDR Client SSP - Success 2 - setup complete L2CAP BR/EDR Client SSP - Success 2 - run
Connect in progress
Successfully connected
L2CAP BR/EDR Client SSP - Success 2 - test passed L2CAP BR/EDR Client SSP - Success 2 - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client SSP - Success 2 - teardown complete L2CAP BR/EDR Client SSP - Success 2 - done
L2CAP BR/EDR Client PIN Code - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client PIN Code - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP BR/EDR Client PIN Code - Success - setup complete L2CAP BR/EDR Client PIN Code - Success - run
Connect in progress
Successfully connected
L2CAP BR/EDR Client PIN Code - Success - test passed L2CAP BR/EDR Client PIN Code - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client PIN Code - Success - teardown complete L2CAP BR/EDR Client PIN Code - Success - done
L2CAP BR/EDR Client - Read Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client - Read Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP BR/EDR Client - Read Success - setup complete L2CAP BR/EDR Client - Read Success - run
Connect in progress
Successfully connected
L2CAP BR/EDR Client - Read Success - test passed L2CAP BR/EDR Client - Read Success - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client - Read Success - teardown complete L2CAP BR/EDR Client - Read Success - done
L2CAP BR/EDR Client - Write Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client - Write Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP BR/EDR Client - Write Success - setup complete L2CAP BR/EDR Client - Write Success - run
Connect in progress
Successfully connected
L2CAP BR/EDR Client - Write Success - test passed L2CAP BR/EDR Client - Write Success - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client - Write Success - teardown complete L2CAP BR/EDR Client - Write Success - done
L2CAP BR/EDR Client - Invalid PSM 1 - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client - Invalid PSM 1 - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP BR/EDR Client - Invalid PSM 1 - setup complete L2CAP BR/EDR Client - Invalid PSM 1 - run
Connect in progress
Connect failed: Connection refused (111)
L2CAP BR/EDR Client - Invalid PSM 1 - test passed L2CAP BR/EDR Client - Invalid PSM 1 - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client - Invalid PSM 1 - teardown complete L2CAP BR/EDR Client - Invalid PSM 1 - done
L2CAP BR/EDR Client - Invalid PSM 2 - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client - Invalid PSM 2 - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP BR/EDR Client - Invalid PSM 2 - setup complete L2CAP BR/EDR Client - Invalid PSM 2 - run
Connect in progress
Connect failed: Connection refused (111)
L2CAP BR/EDR Client - Invalid PSM 2 - test passed L2CAP BR/EDR Client - Invalid PSM 2 - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client - Invalid PSM 2 - teardown complete L2CAP BR/EDR Client - Invalid PSM 2 - done
L2CAP BR/EDR Client - Invalid PSM 3 - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client - Invalid PSM 3 - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
Client enable SSP status 0x00
L2CAP BR/EDR Client - Invalid PSM 3 - setup complete L2CAP BR/EDR Client - Invalid PSM 3 - run
Connect in progress
Connect failed: Connection refused (111)
L2CAP BR/EDR Client - Invalid PSM 3 - test passed L2CAP BR/EDR Client - Invalid PSM 3 - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client - Invalid PSM 3 - teardown complete L2CAP BR/EDR Client - Invalid PSM 3 - done
L2CAP BR/EDR Client - Socket Shut WR Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Client - Socket Shut WR Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP BR/EDR Client - Socket Shut WR Success - setup complete L2CAP BR/EDR Client - Socket Shut WR Success - run
Connect in progress
Successfully connected
L2CAP BR/EDR Client - Socket Shut WR Success - test passed L2CAP BR/EDR Client - Socket Shut WR Success - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Client - Socket Shut WR Success - teardown complete L2CAP BR/EDR Client - Socket Shut WR Success - done
L2CAP BR/EDR Server - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Server - Success - setup
Powering on controller
Controller powered on
L2CAP BR/EDR Server - Success - setup complete
L2CAP BR/EDR Server - Success - run
Listening for connections
New client connection with handle 0x002a
Sending L2CAP Request from client
Client received response code 0x03
L2CAP BR/EDR Server - Success - test passed
Successfully connected
L2CAP BR/EDR Server - Success - test passed
L2CAP BR/EDR Server - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Server - Success - teardown complete
L2CAP BR/EDR Server - Success - done
L2CAP BR/EDR Server - Read Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Server - Read Success - setup
Powering on controller
Controller powered on
L2CAP BR/EDR Server - Read Success - setup complete L2CAP BR/EDR Server - Read Success - run
Listening for connections
New client connection with handle 0x002a Sending L2CAP Request from client
Client received response code 0x03
L2CAP BR/EDR Server - Read Success - test passed L2CAP BR/EDR Server - Read Success - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Server - Read Success - teardown complete L2CAP BR/EDR Server - Read Success - done
L2CAP BR/EDR Server - Write Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Server - Write Success - setup
Powering on controller
Controller powered on
L2CAP BR/EDR Server - Write Success - setup complete L2CAP BR/EDR Server - Write Success - run
Listening for connections
New client connection with handle 0x002a Sending L2CAP Request from client
Client received response code 0x03
L2CAP BR/EDR Server - Write Success - test passed L2CAP BR/EDR Server - Write Success - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Server - Write Success - teardown complete L2CAP BR/EDR Server - Write Success - done
L2CAP BR/EDR Server - Security Block - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Server - Security Block - setup
Powering on controller
Controller powered on
Server enable SSP status 0x00
L2CAP BR/EDR Server - Security Block - setup complete L2CAP BR/EDR Server - Security Block - run
Listening for connections
New client connection with handle 0x002a Sending L2CAP Request from client
Client received response code 0x03
L2CAP BR/EDR Server - Security Block - test passed L2CAP BR/EDR Server - Security Block - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Server - Security Block - teardown complete L2CAP BR/EDR Server - Security Block - done
L2CAP BR/EDR Server - Invalid PSM - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Server - Invalid PSM - setup
Powering on controller
Controller powered on
L2CAP BR/EDR Server - Invalid PSM - setup complete L2CAP BR/EDR Server - Invalid PSM - run
New client connection with handle 0x002a Sending L2CAP Request from client
Client received response code 0x03
L2CAP BR/EDR Server - Invalid PSM - test passed L2CAP BR/EDR Server - Invalid PSM - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Server - Invalid PSM - teardown complete L2CAP BR/EDR Server - Invalid PSM - done
L2CAP BR/EDR Server - Invalid PDU - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Server - Invalid PDU - setup
Powering on controller
Controller powered on
L2CAP BR/EDR Server - Invalid PDU - setup complete L2CAP BR/EDR Server - Invalid PDU - run
New client connection with handle 0x002a Sending L2CAP Request from client
Bluetooth: Wrong link type (-71)
Client received response code 0x01
L2CAP BR/EDR Server - Invalid PDU - test passed L2CAP BR/EDR Server - Invalid PDU - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Server - Invalid PDU - teardown complete L2CAP BR/EDR Server - Invalid PDU - done
L2CAP BR/EDR Server - Invalid Disconnect CID - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Server - Invalid Disconnect CID - setup
Powering on controller
Controller powered on
L2CAP BR/EDR Server - Invalid Disconnect CID - setup complete L2CAP BR/EDR Server - Invalid Disconnect CID - run
New client connection with handle 0x002a
Sending L2CAP Request from client
Client received response code 0x01
L2CAP BR/EDR Server - Invalid Disconnect CID - test passed L2CAP BR/EDR Server - Invalid Disconnect CID - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Server - Invalid Disconnect CID - teardown complete L2CAP BR/EDR Server - Invalid Disconnect CID - done
L2CAP BR/EDR Server - Invalid Config CID - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP BR/EDR Server - Invalid Config CID - setup
Powering on controller
Controller powered on
L2CAP BR/EDR Server - Invalid Config CID - setup complete L2CAP BR/EDR Server - Invalid Config CID - run
New client connection with handle 0x002a Sending L2CAP Request from client
Client received response code 0x01
L2CAP BR/EDR Server - Invalid Config CID - test passed L2CAP BR/EDR Server - Invalid Config CID - teardown
Index Removed callback
Index: 0x0000
L2CAP BR/EDR Server - Invalid Config CID - teardown complete L2CAP BR/EDR Server - Invalid Config CID - done
L2CAP LE Client - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP LE Client - Success - setup complete
L2CAP LE Client - Success - run
Connect in progress
Successfully connected
L2CAP LE Client - Success - test passed
L2CAP LE Client - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client - Success - teardown complete
L2CAP LE Client - Success - done
L2CAP LE Client, Direct Advertising - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client, Direct Advertising - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP LE Client, Direct Advertising - Success - setup complete L2CAP LE Client, Direct Advertising - Success - run
Connect in progress
Received advertising parameters HCI command
L2CAP LE Client, Direct Advertising - Success - test passed L2CAP LE Client, Direct Advertising - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client, Direct Advertising - Success - teardown complete L2CAP LE Client, Direct Advertising - Success - done
L2CAP LE Client SMP - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client SMP - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP LE Client SMP - Success - setup complete
L2CAP LE Client SMP - Success - run
Connect in progress
Successfully connected
L2CAP LE Client SMP - Success - test passed
Bluetooth: hci0: link tx timeout
L2CAP LE Client SMP - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client SMP - Success - teardown complete
L2CAP LE Client SMP - Success - done
L2CAP LE Client - Command Reject - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client - Command Reject - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP LE Client - Command Reject - setup complete
L2CAP LE Client - Command Reject - run
Connect in progress
New connection with handle 0x002a
Connect failed: Connection refused (111)
L2CAP LE Client - Command Reject - test passed
L2CAP LE Client - Command Reject - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client - Command Reject - teardown complete L2CAP LE Client - Command Reject - done
L2CAP LE Client - Connection Reject - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: L2CAP LE Client - Connection Reject - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP LE Client - Connection Reject - setup complete L2CAP LE Client - Connection Reject - run
Can't connect socket: No route to host (113)
L2CAP LE Client - Connection Reject - test passed L2CAP LE Client - Connection Reject - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client - Connection Reject - teardown complete L2CAP LE Client - Connection Reject - done
L2CAP LE Client - Close socket 1 - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client - Close socket 1 - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP LE Client - Close socket 1 - setup complete
L2CAP LE Client - Close socket 1 - run
Connect in progress, sk = 13
Will close socket during scan phase...
Checking whether scan was properly stopped...
L2CAP LE Client - Close socket 1 - test passed
L2CAP LE Client - Close socket 1 - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client - Close socket 1 - teardown complete L2CAP LE Client - Close socket 1 - done
L2CAP LE Client - Close socket 2 - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client - Close socket 2 - setup
Powering on controller
Controller powered on
L2CAP LE Client - Close socket 2 - setup complete
L2CAP LE Client - Close socket 2 - run
Connect in progress, sk = 13
Client set connectable status 0x00
Client set connectable status 0x00
L2CAP LE Client - Close socket 2 - test passed
L2CAP LE Client - Close socket 2 - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client - Close socket 2 - teardown complete L2CAP LE Client - Close socket 2 - done
L2CAP LE Client - Open two sockets - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client - Open two sockets - setup
Powering on controller
Controller powered on
L2CAP LE Client - Open two sockets - setup complete L2CAP LE Client - Open two sockets - run
Connect in progress, sk = 13
HCI Command 0x2011 length 7
HCI Command 0x200b length 7
HCI Command 0x200c length 2
Connect in progress, sk = 14
HCI Command 0x200c length 2
Client set connectable status 0x00
HCI Command 0x200d length 25
HCI Command 0x2016 length 2
Successfully connected
Successfully connected
L2CAP LE Client - Open two sockets - test passed
(l2cap-tester:41): GLib-WARNING **: 23:10:20.985: Invalid file descriptor. L2CAP LE Client - Open two sockets - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client - Open two sockets - teardown complete L2CAP LE Client - Open two sockets - done
L2CAP LE Client - Open two sockets close one - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client - Open two sockets close one - setup
Powering on controller
Controller powered on
L2CAP LE Client - Open two sockets close one - setup complete L2CAP LE Client - Open two sockets close one - run
Connect in progress, sk = 13
HCI Command 0x2011 length 7
HCI Command 0x200b length 7
HCI Command 0x200c length 2
Connect in progress, sk = 14
Closing first socket! 13
HCI Command 0x200c length 2
Client set connectable status 0x00
HCI Command 0x200d length 25
HCI Command 0x2016 length 2
Successfully connected
L2CAP LE Client - Open two sockets close one - test passed
(l2cap-tester:41): GLib-WARNING **: 23:10:21.021: Invalid file descriptor. L2CAP LE Client - Open two sockets close one - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client - Open two sockets close one - teardown complete L2CAP LE Client - Open two sockets close one - done
L2CAP LE Client - Invalid PSM - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Client - Invalid PSM - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP LE Client - Invalid PSM - setup complete
L2CAP LE Client - Invalid PSM - run
Connect in progress
Connect failed: Connection refused (111)
L2CAP LE Client - Invalid PSM - test passed
L2CAP LE Client - Invalid PSM - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Client - Invalid PSM - teardown complete
L2CAP LE Client - Invalid PSM - done
L2CAP LE Server - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Server - Success - setup
Powering on controller
Controller powered on
L2CAP LE Server - Success - setup complete
L2CAP LE Server - Success - run
Listening for connections
New client connection with handle 0x002a
Sending L2CAP Request from client
Successfully connected
L2CAP LE Server - Success - test passed
Client received response code 0x15
L2CAP LE Server - Success - test passed
L2CAP LE Server - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Server - Success - teardown complete
L2CAP LE Server - Success - done
L2CAP LE Server - Nval SCID - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE Server - Nval SCID - setup
Powering on controller
Controller powered on
L2CAP LE Server - Nval SCID - setup complete
L2CAP LE Server - Nval SCID - run
Listening for connections
New client connection with handle 0x002a
Sending L2CAP Request from client
Client received response code 0x15
L2CAP LE Server - Nval SCID - test passed
L2CAP LE Server - Nval SCID - teardown
Index Removed callback
Index: 0x0000
L2CAP LE Server - Nval SCID - teardown complete
L2CAP LE Server - Nval SCID - done
L2CAP Ext-Flowctl Client - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP Ext-Flowctl Client - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP Ext-Flowctl Client - Success - setup complete L2CAP Ext-Flowctl Client - Success - run
Connect in progress
Successfully connected
L2CAP Ext-Flowctl Client - Success - test passed L2CAP Ext-Flowctl Client - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP Ext-Flowctl Client - Success - teardown complete L2CAP Ext-Flowctl Client - Success - done
L2CAP Ext-Flowctl Client, Direct Advertising - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP Ext-Flowctl Client, Direct Advertising - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP Ext-Flowctl Client, Direct Advertising - Success - setup complete L2CAP Ext-Flowctl Client, Direct Advertising - Success - run
Connect in progress
Received advertising parameters HCI command
L2CAP Ext-Flowctl Client, Direct Advertising - Success - test passed L2CAP Ext-Flowctl Client, Direct Advertising - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP Ext-Flowctl Client, Direct Advertising - Success - teardown complete L2CAP Ext-Flowctl Client, Direct Advertising - Success - done
L2CAP Ext-Flowctl Client SMP - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP Ext-Flowctl Client SMP - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP Ext-Flowctl Client SMP - Success - setup complete L2CAP Ext-Flowctl Client SMP - Success - run
Connect in progress
Successfully connected
L2CAP Ext-Flowctl Client SMP - Success - test passed
Bluetooth: hci0: link tx timeout
L2CAP Ext-Flowctl Client SMP - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP Ext-Flowctl Client SMP - Success - teardown complete L2CAP Ext-Flowctl Client SMP - Success - done
L2CAP Ext-Flowctl Client - Command Reject - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP Ext-Flowctl Client - Command Reject - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP Ext-Flowctl Client - Command Reject - setup complete L2CAP Ext-Flowctl Client - Command Reject - run
Connect in progress
New connection with handle 0x002a
Connect failed: Connection refused (111)
L2CAP Ext-Flowctl Client - Command Reject - test passed L2CAP Ext-Flowctl Client - Command Reject - teardown
Index Removed callback
Index: 0x0000
L2CAP Ext-Flowctl Client - Command Reject - teardown complete L2CAP Ext-Flowctl Client - Command Reject - done
L2CAP Ext-Flowctl Client - Open two sockets - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP Ext-Flowctl Client - Open two sockets - setup
Powering on controller
Controller powered on
L2CAP Ext-Flowctl Client - Open two sockets - setup complete L2CAP Ext-Flowctl Client - Open two sockets - run
Connect in progress, sk = 13 (deferred)
HCI Command 0x2011 length 7
HCI Command 0x200b length 7
HCI Command 0x200c length 2
Connect in progress, sk = 14
HCI Command 0x200c length 2
Client set connectable status 0x00
HCI Command 0x200d length 25
HCI Command 0x2016 length 2
Successfully connected
Successfully connected
Bluetooth: hci0: link tx timeout
L2CAP Ext-Flowctl Client - Open two sockets - test passed
(l2cap-tester:41): GLib-WARNING **: 23:10:21.169: Invalid file descriptor. L2CAP Ext-Flowctl Client - Open two sockets - teardown
Index Removed callback
Index: 0x0000
L2CAP Ext-Flowctl Client - Open two sockets - teardown complete L2CAP Ext-Flowctl Client - Open two sockets - done
L2CAP Ext-Flowctl Client - Open two sockets close one - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP Ext-Flowctl Client - Open two sockets close one - setup
Powering on controller
Controller powered on
L2CAP Ext-Flowctl Client - Open two sockets close one - setup complete L2CAP Ext-Flowctl Client - Open two sockets close one - run
Connect in progress, sk = 13 (deferred)
HCI Command 0x2011 length 7
HCI Command 0x200b length 7
HCI Command 0x200c length 2
Connect in progress, sk = 14
Closing first socket! 13
HCI Command 0x200c length 2
Client set connectable status 0x00
HCI Command 0x200d length 25
HCI Command 0x2016 length 2
Successfully connected
L2CAP Ext-Flowctl Client - Open two sockets close one - test passed
(l2cap-tester:41): GLib-WARNING **: 23:10:21.194: Invalid file descriptor. L2CAP Ext-Flowctl Client - Open two sockets close one - teardown
Index Removed callback
Index: 0x0000
L2CAP Ext-Flowctl Client - Open two sockets close one - teardown complete L2CAP Ext-Flowctl Client - Open two sockets close one - done
L2CAP LE ATT Client - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE ATT Client - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
L2CAP LE ATT Client - Success - setup complete
L2CAP LE ATT Client - Success - run
Connect in progress
Successfully connected
L2CAP LE ATT Client - Success - test passed
L2CAP LE ATT Client - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP LE ATT Client - Success - teardown complete
L2CAP LE ATT Client - Success - done
L2CAP LE ATT Server - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: L2CAP LE ATT Server - Success - setup
Powering on controller
Controller powered on
L2CAP LE ATT Server - Success - setup complete
L2CAP LE ATT Server - Success - run
Listening for connections
New client connection with handle 0x002a
Successfully connected
L2CAP LE ATT Server - Success - test passed
L2CAP LE ATT Server - Success - teardown
Index Removed callback
Index: 0x0000
L2CAP LE ATT Server - Success - teardown complete
L2CAP LE ATT Server - Success - done
Test Summary
------------
Basic L2CAP Socket - Success Passed 0.062 seconds Non-connected getpeername - Failure Passed 0.017 seconds L2CAP BR/EDR Client - Success Passed 0.036 seconds L2CAP BR/EDR Client SSP - Success 1 Passed 0.024 seconds L2CAP BR/EDR Client SSP - Success 2 Passed 0.021 seconds L2CAP BR/EDR Client PIN Code - Success Passed 0.017 seconds L2CAP BR/EDR Client - Read Success Passed 0.014 seconds L2CAP BR/EDR Client - Write Success Passed 0.014 seconds L2CAP BR/EDR Client - Invalid PSM 1 Passed 0.021 seconds L2CAP BR/EDR Client - Invalid PSM 2 Passed 0.013 seconds L2CAP BR/EDR Client - Invalid PSM 3 Passed 0.013 seconds L2CAP BR/EDR Client - Socket Shut WR Success Passed 0.018 seconds L2CAP BR/EDR Server - Success Passed 0.018 seconds L2CAP BR/EDR Server - Read Success Passed 0.019 seconds L2CAP BR/EDR Server - Write Success Passed 0.019 seconds L2CAP BR/EDR Server - Security Block Passed 0.022 seconds L2CAP BR/EDR Server - Invalid PSM Passed 0.013 seconds L2CAP BR/EDR Server - Invalid PDU Passed 0.019 seconds L2CAP BR/EDR Server - Invalid Disconnect CID Passed 0.016 seconds L2CAP BR/EDR Server - Invalid Config CID Passed 0.016 seconds L2CAP LE Client - Success Passed 0.032 seconds L2CAP LE Client, Direct Advertising - Success Passed 0.015 seconds L2CAP LE Client SMP - Success Passed 0.031 seconds L2CAP LE Client - Command Reject Passed 0.017 seconds L2CAP LE Client - Connection Reject Passed 0.017 seconds L2CAP LE Client - Close socket 1 Passed 0.018 seconds L2CAP LE Client - Close socket 2 Passed 0.017 seconds L2CAP LE Client - Open two sockets Passed 0.051 seconds L2CAP LE Client - Open two sockets close one Passed 0.023 seconds L2CAP LE Client - Invalid PSM Passed 0.016 seconds L2CAP LE Server - Success Passed 0.020 seconds L2CAP LE Server - Nval SCID Passed 0.016 seconds L2CAP Ext-Flowctl Client - Success Passed 0.016 seconds L2CAP Ext-Flowctl Client, Direct Advertising - Success Passed 0.015 seconds L2CAP Ext-Flowctl Client SMP - Success Passed 0.017 seconds L2CAP Ext-Flowctl Client - Command Reject Passed 0.017 seconds L2CAP Ext-Flowctl Client - Open two sockets Passed 0.025 seconds L2CAP Ext-Flowctl Client - Open two sockets close one Passed 0.024 seconds L2CAP LE ATT Client - Success Passed 0.018 seconds L2CAP LE ATT Server - Success Passed 0.017 seconds
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0 Overall execution time: 0.872 seconds
Process 41 exited with status 0
reboot: Restarting system
c[?7l[2JSeaBIOS (version 1.13.0-1ubuntu1.1) Booting from ROM..c[?7l[2Jearly console in extract_kernelinput_data: 0x0000000001e782e0input_len: 0x000000000036171d
output: 0x0000000001000000output_len: 0x00000000011a722ckernel_total_size: 0x0000000001030000needed_size: 0x0000000001200000trampoline_32bit: 0x000000000009d000
Physical KASLR using RDTSC...
Virtual KASLR using RDTSC...
Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel.
Linux version 5.12.0-g72a0f235d09c (root@3eb00f0dfff0) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #2 Mon Jun 21 23:10:12 UTC 2021
Command line: console=ttyS0,115200n8 earlyprintk=serial rootfstype=9p rootflags=trans=virtio,version=9p2000.L acpi=off pci=noacpi noapic quiet ro init=/github/workspace/bluez/tools/test-runner bluetooth.enable_ecred=1TESTHOME=/github/workspace TESTDBUS=0 TESTMONITOR=0 TESTDEVS=0 TESTAUTO=0 TESTARGS='/github/workspace/bluez/tools/bnep-tester' x86/fpu: x87 FPU will use FXSAVE
BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000000bffdfff] usable
BIOS-e820: [mem 0x000000000bffe000-0x000000000bffffff] reserved
BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
printk: bootconsole [earlyser0] enabled
Memory KASLR using RDTSC...
Poking KASLR using RDTSC...
Mounting sysfs to /sys
Mounting proc to /proc
Mounting devtmpfs to /dev
Creating /dev/pts
Mounting devpts to /dev/pts
Creating /dev/shm
Mounting tmpfs to /dev/shm
Mounting tmpfs to /run
Mounting tmpfs to /tmp
Mounting debugfs to /sys/kernel/debug
Linking /dev/fd to /proc/self/fd
Linking /dev/stdin to /proc/self/fd/0
Linking /dev/stdout to /proc/self/fd/1
Linking /dev/stderr to /proc/self/fd/2
Creating new session group leader
Setting controlling terminal
Creating /var/lib/bluetooth
Failed to create filesystem: No such file or directory
Creating /etc/bluetooth
Failed to create filesystem: No such file or directory
Creating /etc/dbus-1
Failed to create filesystem: No such file or directory
Creating /usr/share/dbus-1
Running command /github/workspace/bluez/tools/bnep-tester
New process 41 created
Changing into directory /github/workspace
Basic BNEP Socket - Success - init
Read Index List callback
Status: 0x00
New hciemu instance created
Index Added callback
Index: 0x0000
Read Info callback
Status: 0x00
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Basic BNEP Socket - Success - setup
Powering on controller
Controller powered on
Client set connectable status 0x00
Basic BNEP Socket - Success - setup complete
Basic BNEP Socket - Success - run
Basic BNEP Socket - Success - test passed
Basic BNEP Socket - Success - teardown
Index Removed callback
Index: 0x0000
Basic BNEP Socket - Success - teardown complete
Basic BNEP Socket - Success - done
Test Summary
------------
Basic BNEP Socket - Success Passed 0.056 seconds
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0 Overall execution time: 0.063 seconds Process 41 exited with status 0
reboot: Restarting system
c[?7l[2JSeaBIOS (version 1.13.0-1ubuntu1.1) Booting from ROM..c[?7l[2Jearly console in extract_kernelinput_data: 0x0000000001e782e0input_len: 0x000000000036171d
output: 0x0000000001000000output_len: 0x00000000011a722ckernel_total_size: 0x0000000001030000needed_size: 0x0000000001200000trampoline_32bit: 0x000000000009d000
Physical KASLR using RDTSC...
Virtual KASLR using RDTSC...
Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel.
Linux version 5.12.0-g72a0f235d09c (root@3eb00f0dfff0) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #2 Mon Jun 21 23:10:12 UTC 2021
Command line: console=ttyS0,115200n8 earlyprintk=serial rootfstype=9p rootflags=trans=virtio,version=9p2000.L acpi=off pci=noacpi noapic quiet ro init=/github/workspace/bluez/tools/test-runner bluetooth.enable_ecred=1TESTHOME=/github/workspace TESTDBUS=0 TESTMONITOR=0 TESTDEVS=0 TESTAUTO=0 TESTARGS='/github/workspace/bluez/tools/mgmt-tester' x86/fpu: x87 FPU will use FXSAVE
BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000000bffdfff] usable
BIOS-e820: [mem 0x000000000bffe000-0x000000000bffffff] reserved
BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
printk: bootconsole [earlyser0] enabled
Memory KASLR using RDTSC...
Poking KASLR using RDTSC...
Mounting sysfs to /sys
Mounting proc to /proc
Mounting devtmpfs to /dev
Creating /dev/pts
Mounting devpts to /dev/pts
Creating /dev/shm
Mounting tmpfs to /dev/shm
Mounting tmpfs to /run
Mounting tmpfs to /tmp
Mounting debugfs to /sys/kernel/debug
Linking /dev/fd to /proc/self/fd
Linking /dev/stdin to /proc/self/fd/0
Linking /dev/stdout to /proc/self/fd/1
Linking /dev/stderr to /proc/self/fd/2
Creating new session group leader
Setting controlling terminal
Creating /var/lib/bluetooth
Failed to create filesystem: No such file or directory
Creating /etc/bluetooth
Failed to create filesystem: No such file or directory
Creating /etc/dbus-1
Failed to create filesystem: No such file or directory
Creating /usr/share/dbus-1
Running command /github/workspace/bluez/tools/mgmt-tester
New process 41 created
Changing into directory /github/workspace
Controller setup - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Controller setup - setup
Controller setup - setup complete
Controller setup - run
Controller setup - test passed
Controller setup - teardown
Index Removed callback
Index: 0x0000
Controller setup - teardown complete
Controller setup - done
Controller setup (BR/EDR-only) - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Controller setup (BR/EDR-only) - setup
Controller setup (BR/EDR-only) - setup complete
Controller setup (BR/EDR-only) - run
Controller setup (BR/EDR-only) - test passed
Controller setup (BR/EDR-only) - teardown
Index Removed callback
Index: 0x0000
Controller setup (BR/EDR-only) - teardown complete Controller setup (BR/EDR-only) - done
Controller setup (LE) - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Controller setup (LE) - setup
Controller setup (LE) - setup complete
Controller setup (LE) - run
Controller setup (LE) - test passed
Controller setup (LE) - teardown
Index Removed callback
Index: 0x0000
Controller setup (LE) - teardown complete
Controller setup (LE) - done
Invalid command - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Invalid command - setup
Invalid command - setup complete
Invalid command - run
Sending <unknown opcode> (0xffff)
Test condition added, total 1
<unknown opcode> (0xffff): Unknown Command (0x01) Test condition complete, 0 left
Invalid command - test passed
Invalid command - teardown
Index Removed callback
Index: 0x0000
Invalid command - teardown complete
Invalid command - done
Read version - Success - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read version - Success - setup
Read version - Success - setup complete
Read version - Success - run
Sending Read Version (0x0001)
Test condition added, total 1
Read Version (0x0001): Success (0x00)
Test condition complete, 0 left
Read version - Success - test passed
Read version - Success - teardown
Index Removed callback
Index: 0x0000
Read version - Success - teardown complete
Read version - Success - done
Read version - Invalid parameters - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read version - Invalid parameters - setup Read version - Invalid parameters - setup complete Read version - Invalid parameters - run
Sending Read Version (0x0001)
Test condition added, total 1
Read Version (0x0001): Invalid Parameters (0x0d) Test condition complete, 0 left
Read version - Invalid parameters - test passed Read version - Invalid parameters - teardown
Index Removed callback
Index: 0x0000
Read version - Invalid parameters - teardown complete Read version - Invalid parameters - done
Read version - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read version - Invalid index - setup
Read version - Invalid index - setup complete
Read version - Invalid index - run
Sending Read Version (0x0001)
Test condition added, total 1
Read Version (0x0001): Invalid Index (0x11)
Test condition complete, 0 left
Read version - Invalid index - test passed
Read version - Invalid index - teardown
Index Removed callback
Index: 0x0000
Read version - Invalid index - teardown complete
Read version - Invalid index - done
Read commands - Invalid parameters - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read commands - Invalid parameters - setup Read commands - Invalid parameters - setup complete Read commands - Invalid parameters - run
Sending Read Commands (0x0002)
Test condition added, total 1
Read Commands (0x0002): Invalid Parameters (0x0d) Test condition complete, 0 left
Read commands - Invalid parameters - test passed Read commands - Invalid parameters - teardown
Index Removed callback
Index: 0x0000
Read commands - Invalid parameters - teardown complete Read commands - Invalid parameters - done
Read commands - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read commands - Invalid index - setup
Read commands - Invalid index - setup complete
Read commands - Invalid index - run
Sending Read Commands (0x0002)
Test condition added, total 1
Read Commands (0x0002): Invalid Index (0x11)
Test condition complete, 0 left
Read commands - Invalid index - test passed
Read commands - Invalid index - teardown
Index Removed callback
Index: 0x0000
Read commands - Invalid index - teardown complete
Read commands - Invalid index - done
Read index list - Invalid parameters - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read index list - Invalid parameters - setup Read index list - Invalid parameters - setup complete Read index list - Invalid parameters - run
Sending Read Index List (0x0003)
Test condition added, total 1
Read Index List (0x0003): Invalid Parameters (0x0d) Test condition complete, 0 left
Read index list - Invalid parameters - test passed Read index list - Invalid parameters - teardown
Index Removed callback
Index: 0x0000
Read index list - Invalid parameters - teardown complete Read index list - Invalid parameters - done
Read index list - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read index list - Invalid index - setup
Read index list - Invalid index - setup complete
Read index list - Invalid index - run
Sending Read Index List (0x0003)
Test condition added, total 1
Read Index List (0x0003): Invalid Index (0x11)
Test condition complete, 0 left
Read index list - Invalid index - test passed
Read index list - Invalid index - teardown
Index Removed callback
Index: 0x0000
Read index list - Invalid index - teardown complete Read index list - Invalid index - done
Read info - Invalid parameters - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read info - Invalid parameters - setup
Read info - Invalid parameters - setup complete Read info - Invalid parameters - run
Sending Read Controller Info (0x0004)
Test condition added, total 1
Read Controller Info (0x0004): Invalid Parameters (0x0d) Test condition complete, 0 left
Read info - Invalid parameters - test passed
Read info - Invalid parameters - teardown
Index Removed callback
Index: 0x0000
Read info - Invalid parameters - teardown complete Read info - Invalid parameters - done
Read info - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read info - Invalid index - setup
Read info - Invalid index - setup complete Read info - Invalid index - run
Sending Read Controller Info (0x0004)
Test condition added, total 1
Read Controller Info (0x0004): Invalid Index (0x11) Test condition complete, 0 left
Read info - Invalid index - test passed
Read info - Invalid index - teardown
Index Removed callback
Index: 0x0000
Read info - Invalid index - teardown complete
Read info - Invalid index - done
Read unconfigured index list - Invalid parameters - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read unconfigured index list - Invalid parameters - setup Read unconfigured index list - Invalid parameters - setup complete Read unconfigured index list - Invalid parameters - run
Sending Read Unconfigured Index List (0x0036)
Test condition added, total 1
Read Unconfigured Index List (0x0036): Invalid Parameters (0x0d) Test condition complete, 0 left
Read unconfigured index list - Invalid parameters - test passed Read unconfigured index list - Invalid parameters - teardown
Index Removed callback
Index: 0x0000
Read unconfigured index list - Invalid parameters - teardown complete Read unconfigured index list - Invalid parameters - done
Read unconfigured index list - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read unconfigured index list - Invalid index - setup Read unconfigured index list - Invalid index - setup complete Read unconfigured index list - Invalid index - run
Sending Read Unconfigured Index List (0x0036) Test condition added, total 1
Read Unconfigured Index List (0x0036): Invalid Index (0x11) Test condition complete, 0 left
Read unconfigured index list - Invalid index - test passed Read unconfigured index list - Invalid index - teardown
Index Removed callback
Index: 0x0000
Read unconfigured index list - Invalid index - teardown complete Read unconfigured index list - Invalid index - done
Read configuration info - Invalid parameters - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read configuration info - Invalid parameters - setup
Read configuration info - Invalid parameters - setup complete
Read configuration info - Invalid parameters - run
Sending Read Controller Configuration Information (0x0037)
Test condition added, total 1
Read Controller Configuration Information (0x0037): Invalid Parameters (0x0d) Test condition complete, 0 left
Read configuration info - Invalid parameters - test passed
Read configuration info - Invalid parameters - teardown
Index Removed callback
Index: 0x0000
Read configuration info - Invalid parameters - teardown complete Read configuration info - Invalid parameters - done
Read configuration info - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read configuration info - Invalid index - setup
Read configuration info - Invalid index - setup complete
Read configuration info - Invalid index - run
Sending Read Controller Configuration Information (0x0037) Test condition added, total 1
Read Controller Configuration Information (0x0037): Invalid Index (0x11) Test condition complete, 0 left
Read configuration info - Invalid index - test passed
Read configuration info - Invalid index - teardown
Index Removed callback
Index: 0x0000
Read configuration info - Invalid index - teardown complete Read configuration info - Invalid index - done
Read extended index list - Invalid parameters - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read extended index list - Invalid parameters - setup
Read extended index list - Invalid parameters - setup complete Read extended index list - Invalid parameters - run
Sending Read Extended Controller Index List (0x003c)
Test condition added, total 1
Read Extended Controller Index List (0x003c): Invalid Parameters (0x0d) Test condition complete, 0 left
Read extended index list - Invalid parameters - test passed Read extended index list - Invalid parameters - teardown
Index Removed callback
Index: 0x0000
Read extended index list - Invalid parameters - teardown complete Read extended index list - Invalid parameters - done
Read extended index list - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Read extended index list - Invalid index - setup
Read extended index list - Invalid index - setup complete Read extended index list - Invalid index - run
Sending Read Extended Controller Index List (0x003c) Test condition added, total 1
Read Extended Controller Index List (0x003c): Invalid Index (0x11) Test condition complete, 0 left
Read extended index list - Invalid index - test passed Read extended index list - Invalid index - teardown
Index Removed callback
Index: 0x0000
Read extended index list - Invalid index - teardown complete Read extended index list - Invalid index - done
Set powered on - Success - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered on - Success - setup
Set powered on - Success - setup complete
Set powered on - Success - run
Registering new settings notification
Test condition added, total 1
Sending Set Powered (0x0005)
Test condition added, total 2
Set Powered (0x0005): Success (0x00)
Test condition complete, 1 left
New settings 0x00000081 received
Unregistering new settings notification
Test condition complete, 0 left
Set powered on - Success - test passed
Set powered on - Success - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set powered on - Success - teardown complete
Set powered on - Success - done
Set powered on - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered on - Invalid parameters 1 - setup Set powered on - Invalid parameters 1 - setup complete Set powered on - Invalid parameters 1 - run
Sending Set Powered (0x0005)
Test condition added, total 1
Set Powered (0x0005): Invalid Parameters (0x0d) Test condition complete, 0 left
Set powered on - Invalid parameters 1 - test passed Set powered on - Invalid parameters 1 - teardown
Index Removed callback
Index: 0x0000
Set powered on - Invalid parameters 1 - teardown complete Set powered on - Invalid parameters 1 - done
Set powered on - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered on - Invalid parameters 2 - setup Set powered on - Invalid parameters 2 - setup complete Set powered on - Invalid parameters 2 - run
Sending Set Powered (0x0005)
Test condition added, total 1
Set Powered (0x0005): Invalid Parameters (0x0d) Test condition complete, 0 left
Set powered on - Invalid parameters 2 - test passed Set powered on - Invalid parameters 2 - teardown
Index Removed callback
Index: 0x0000
Set powered on - Invalid parameters 2 - teardown complete Set powered on - Invalid parameters 2 - done
Set powered on - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered on - Invalid parameters 3 - setup Set powered on - Invalid parameters 3 - setup complete Set powered on - Invalid parameters 3 - run
Sending Set Powered (0x0005)
Test condition added, total 1
Set Powered (0x0005): Invalid Parameters (0x0d) Test condition complete, 0 left
Set powered on - Invalid parameters 3 - test passed Set powered on - Invalid parameters 3 - teardown
Index Removed callback
Index: 0x0000
Set powered on - Invalid parameters 3 - teardown complete Set powered on - Invalid parameters 3 - done
Set powered on - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered on - Invalid index - setup
Set powered on - Invalid index - setup complete
Set powered on - Invalid index - run
Sending Set Powered (0x0005)
Test condition added, total 1
Set Powered (0x0005): Invalid Index (0x11)
Test condition complete, 0 left
Set powered on - Invalid index - test passed
Set powered on - Invalid index - teardown
Index Removed callback
Index: 0x0000
Set powered on - Invalid index - teardown complete Set powered on - Invalid index - done
Set powered on - Privacy and Advertising - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set powered on - Privacy and Advertising - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set powered on - Privacy and Advertising - setup complete Set powered on - Privacy and Advertising - run
Sending Set Advertising (0x0029)
Test condition added, total 1
Set Advertising (0x0029): Success (0x00)
Test condition complete, 0 left
Set powered on - Privacy and Advertising - test passed Set powered on - Privacy and Advertising - teardown
Index Removed callback
Index: 0x0000
Set powered on - Privacy and Advertising - teardown complete Set powered on - Privacy and Advertising - done
Set powered off - Success - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered off - Success - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set powered off - Success - setup complete
Set powered off - Success - run
Registering new settings notification
Test condition added, total 1
Sending Set Powered (0x0005)
Test condition added, total 2
Set Powered (0x0005): Success (0x00)
Test condition complete, 1 left
New settings 0x00000080 received
Unregistering new settings notification
Test condition complete, 0 left
Set powered off - Success - test passed
Set powered off - Success - teardown
Index Removed callback
Index: 0x0000
Set powered off - Success - teardown complete
Set powered off - Success - done
Set powered off - Class of Device - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered off - Class of Device - setup
Setting device class and powering on Controller powered on
Test setup condition added, total 1 Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set powered off - Class of Device - setup complete Set powered off - Class of Device - run
Registering new settings notification Test condition added, total 1 Registering Class of Device Changed notification Test condition added, total 2
Sending Set Powered (0x0005)
Test condition added, total 3
Set Powered (0x0005): Success (0x00) Test condition complete, 2 left
New Class of Device Changed event received Test condition complete, 1 left
New settings 0x00000080 received Unregistering new settings notification Test condition complete, 0 left
Set powered off - Class of Device - test passed Set powered off - Class of Device - teardown
Index Removed callback
Index: 0x0000
Set powered off - Class of Device - teardown complete Set powered off - Class of Device - done
Set powered off - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered off - Invalid parameters 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set powered off - Invalid parameters 1 - setup complete Set powered off - Invalid parameters 1 - run
Sending Set Powered (0x0005)
Test condition added, total 1
Set Powered (0x0005): Invalid Parameters (0x0d) Test condition complete, 0 left
Set powered off - Invalid parameters 1 - test passed Set powered off - Invalid parameters 1 - teardown
Index Removed callback
Index: 0x0000
Set powered off - Invalid parameters 1 - teardown complete Set powered off - Invalid parameters 1 - done
Set powered off - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered off - Invalid parameters 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set powered off - Invalid parameters 2 - setup complete Set powered off - Invalid parameters 2 - run
Sending Set Powered (0x0005)
Test condition added, total 1
Set Powered (0x0005): Invalid Parameters (0x0d) Test condition complete, 0 left
Set powered off - Invalid parameters 2 - test passed Set powered off - Invalid parameters 2 - teardown
Index Removed callback
Index: 0x0000
Set powered off - Invalid parameters 2 - teardown complete Set powered off - Invalid parameters 2 - done
Set powered off - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set powered off - Invalid parameters 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set powered off - Invalid parameters 3 - setup complete Set powered off - Invalid parameters 3 - run
Sending Set Powered (0x0005)
Test condition added, total 1
Set Powered (0x0005): Invalid Parameters (0x0d) Test condition complete, 0 left
Set powered off - Invalid parameters 3 - test passed Set powered off - Invalid parameters 3 - teardown
Index Removed callback
Index: 0x0000
Set powered off - Invalid parameters 3 - teardown complete Set powered off - Invalid parameters 3 - done
Set connectable on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable on - Success 1 - setup
Set connectable on - Success 1 - setup complete
Set connectable on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Connectable (0x0007)
Test condition added, total 2
Set Connectable (0x0007): Success (0x00)
Test condition complete, 1 left
New settings 0x00000082 received
Unregistering new settings notification
Test condition complete, 0 left
Set connectable on - Success 1 - test passed
Set connectable on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set connectable on - Success 1 - teardown complete Set connectable on - Success 1 - done
Set connectable on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable on - Success 2 - setup complete
Set connectable on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Connectable (0x0007)
Test condition added, total 3
HCI Command 0x0c1a length 1
Test condition complete, 2 left
Set Connectable (0x0007): Success (0x00)
Test condition complete, 1 left
New settings 0x00000083 received
Unregistering new settings notification
Test condition complete, 0 left
Set connectable on - Success 2 - test passed
Set connectable on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable on - Success 2 - teardown complete Set connectable on - Success 2 - done
Set connectable on - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable on - Invalid parameters 1 - setup Set connectable on - Invalid parameters 1 - setup complete Set connectable on - Invalid parameters 1 - run
Sending Set Connectable (0x0007)
Test condition added, total 1
Set Connectable (0x0007): Invalid Parameters (0x0d) Test condition complete, 0 left
Set connectable on - Invalid parameters 1 - test passed Set connectable on - Invalid parameters 1 - teardown
Index Removed callback
Index: 0x0000
Set connectable on - Invalid parameters 1 - teardown complete Set connectable on - Invalid parameters 1 - done
Set connectable on - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable on - Invalid parameters 2 - setup Set connectable on - Invalid parameters 2 - setup complete Set connectable on - Invalid parameters 2 - run
Sending Set Connectable (0x0007)
Test condition added, total 1
Set Connectable (0x0007): Invalid Parameters (0x0d) Test condition complete, 0 left
Set connectable on - Invalid parameters 2 - test passed Set connectable on - Invalid parameters 2 - teardown
Index Removed callback
Index: 0x0000
Set connectable on - Invalid parameters 2 - teardown complete Set connectable on - Invalid parameters 2 - done
Set connectable on - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable on - Invalid parameters 3 - setup Set connectable on - Invalid parameters 3 - setup complete Set connectable on - Invalid parameters 3 - run
Sending Set Connectable (0x0007)
Test condition added, total 1
Set Connectable (0x0007): Invalid Parameters (0x0d) Test condition complete, 0 left
Set connectable on - Invalid parameters 3 - test passed Set connectable on - Invalid parameters 3 - teardown
Index Removed callback
Index: 0x0000
Set connectable on - Invalid parameters 3 - teardown complete Set connectable on - Invalid parameters 3 - done
Set connectable on - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable on - Invalid index - setup Set connectable on - Invalid index - setup complete Set connectable on - Invalid index - run
Sending Set Connectable (0x0007)
Test condition added, total 1
Set Connectable (0x0007): Invalid Index (0x11) Test condition complete, 0 left
Set connectable on - Invalid index - test passed Set connectable on - Invalid index - teardown
Index Removed callback
Index: 0x0000
Set connectable on - Invalid index - teardown complete Set connectable on - Invalid index - done
Set connectable on (LE) - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set connectable on (LE) - Success 1 - setup Set connectable on (LE) - Success 1 - setup complete Set connectable on (LE) - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Connectable (0x0007)
Test condition added, total 2
Set Connectable (0x0007): Success (0x00) Test condition complete, 1 left
New settings 0x00000202 received Unregistering new settings notification Test condition complete, 0 left
Set connectable on (LE) - Success 1 - test passed Set connectable on (LE) - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set connectable on (LE) - Success 1 - teardown complete Set connectable on (LE) - Success 1 - done
Set connectable on (LE) - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set connectable on (LE) - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set connectable on (LE) - Success 2 - setup complete Set connectable on (LE) - Success 2 - run
Registering new settings notification
Test condition added, total 1
Sending Set Connectable (0x0007)
Test condition added, total 2
Set Connectable (0x0007): Success (0x00) Test condition complete, 1 left
New settings 0x00000203 received Unregistering new settings notification Test condition complete, 0 left
Set connectable on (LE) - Success 2 - test passed Set connectable on (LE) - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable on (LE) - Success 2 - teardown complete Set connectable on (LE) - Success 2 - done
Set connectable on (LE) - Success 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set connectable on (LE) - Success 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set connectable on (LE) - Success 3 - setup complete Set connectable on (LE) - Success 3 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Connectable (0x0007)
Test condition added, total 3
HCI Command 0x200a length 1
HCI Command 0x2006 length 15
Test condition complete, 2 left
HCI Command 0x200a length 1
Set Connectable (0x0007): Success (0x00) Test condition complete, 1 left
New settings 0x00000603 received Unregistering new settings notification Test condition complete, 0 left
Set connectable on (LE) - Success 3 - test passed Set connectable on (LE) - Success 3 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable on (LE) - Success 3 - teardown complete Set connectable on (LE) - Success 3 - done
Set connectable off - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable off - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable off - Success 1 - setup complete
Set connectable off - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Connectable (0x0007)
Test condition added, total 2
Set Connectable (0x0007): Success (0x00)
Test condition complete, 1 left
New settings 0x00000080 received
Unregistering new settings notification
Test condition complete, 0 left
Set connectable off - Success 1 - test passed
Set connectable off - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set connectable off - Success 1 - teardown complete Set connectable off - Success 1 - done
Set connectable off - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable off - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable off - Success 2 - setup complete
Set connectable off - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Connectable (0x0007)
Test condition added, total 3
HCI Command 0x0c1a length 1
Test condition complete, 2 left
Set Connectable (0x0007): Success (0x00)
Test condition complete, 1 left
New settings 0x00000081 received
Unregistering new settings notification
Test condition complete, 0 left
Set connectable off - Success 2 - test passed
Set connectable off - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable off - Success 2 - teardown complete Set connectable off - Success 2 - done
Set connectable off - Success 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable off - Success 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable off - Success 3 - setup complete
Set connectable off - Success 3 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Connectable (0x0007)
Test condition added, total 3
HCI Command 0x0c1a length 1
Test condition complete, 2 left
Set Connectable (0x0007): Success (0x00)
Test condition complete, 1 left
New settings 0x00000081 received
Unregistering new settings notification
Test condition complete, 0 left
Set connectable off - Success 3 - test passed
Set connectable off - Success 3 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable off - Success 3 - teardown complete Set connectable off - Success 3 - done
Set connectable off - Success 4 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set connectable off - Success 4 - setup
Initial settings completed
Powering on controller (with added device)
Controller powered on
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable off - Success 4 - setup complete
Set connectable off - Success 4 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Connectable (0x0007)
Test condition added, total 3
HCI Command 0x0c1a length 1
Test condition complete, 2 left
Set Connectable (0x0007): Success (0x00)
Test condition complete, 1 left
New settings 0x00000081 received
Unregistering new settings notification
Test condition complete, 0 left
Set connectable off - Success 4 - test passed
Set connectable off - Success 4 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable off - Success 4 - teardown complete Set connectable off - Success 4 - done
Set connectable off (LE) - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set connectable off (LE) - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable off (LE) - Success 1 - setup complete Set connectable off (LE) - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Connectable (0x0007)
Test condition added, total 2
Set Connectable (0x0007): Success (0x00) Test condition complete, 1 left
New settings 0x00000200 received Unregistering new settings notification Test condition complete, 0 left
Set connectable off (LE) - Success 1 - test passed Set connectable off (LE) - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set connectable off (LE) - Success 1 - teardown complete Set connectable off (LE) - Success 1 - done
Set connectable off (LE) - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set connectable off (LE) - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable off (LE) - Success 2 - setup complete Set connectable off (LE) - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Connectable (0x0007)
Test condition added, total 3
HCI Command 0x200a length 1
HCI Command 0x2005 length 6
HCI Command 0x2006 length 15
Test condition complete, 2 left
HCI Command 0x200a length 1
Set Connectable (0x0007): Success (0x00) Test condition complete, 1 left
New settings 0x00000601 received Unregistering new settings notification Test condition complete, 0 left
Set connectable off (LE) - Success 2 - test passed Set connectable off (LE) - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable off (LE) - Success 2 - teardown complete Set connectable off (LE) - Success 2 - done
Set connectable off (LE) - Success 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set connectable off (LE) - Success 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable off (LE) - Success 3 - setup complete Set connectable off (LE) - Success 3 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Connectable (0x0007)
Test condition added, total 3
HCI Command 0x2008 length 32
HCI Command 0x200a length 1
HCI Command 0x2005 length 6
HCI Command 0x2006 length 15
Test condition complete, 2 left
HCI Command 0x200a length 1
Set Connectable (0x0007): Success (0x00) Test condition complete, 1 left
New settings 0x00000601 received Unregistering new settings notification Test condition complete, 0 left
Set connectable off (LE) - Success 3 - test passed Set connectable off (LE) - Success 3 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable off (LE) - Success 3 - teardown complete Set connectable off (LE) - Success 3 - done
Set connectable off (LE) - Success 4 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set connectable off (LE) - Success 4 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set connectable off (LE) - Success 4 - setup complete Set connectable off (LE) - Success 4 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Connectable (0x0007)
Test condition added, total 3
HCI Command 0x2008 length 32
HCI Command 0x200a length 1
HCI Command 0x2005 length 6
HCI Command 0x2006 length 15
Test condition complete, 2 left
HCI Command 0x200a length 1
Set Connectable (0x0007): Success (0x00) Test condition complete, 1 left
New settings 0x00000601 received Unregistering new settings notification Test condition complete, 0 left
Set connectable off (LE) - Success 4 - test passed Set connectable off (LE) - Success 4 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set connectable off (LE) - Success 4 - teardown complete Set connectable off (LE) - Success 4 - done
Set fast connectable on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set fast connectable on - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set fast connectable on - Success 1 - setup complete Set fast connectable on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Fast Connectable (0x0008)
Test condition added, total 2
Set Fast Connectable (0x0008): Success (0x00) Test condition complete, 1 left
New settings 0x00000087 received Unregistering new settings notification Test condition complete, 0 left
Set fast connectable on - Success 1 - test passed Set fast connectable on - Success 1 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set fast connectable on - Success 1 - teardown complete Set fast connectable on - Success 1 - done
Set fast connectable on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set fast connectable on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set fast connectable on - Success 2 - setup complete Set fast connectable on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Sending Set Fast Connectable (0x0008)
Test condition added, total 2
Set Fast Connectable (0x0008): Success (0x00) Test condition complete, 1 left
New settings 0x00000085 received Unregistering new settings notification Test condition complete, 0 left
Set fast connectable on - Success 2 - test passed Set fast connectable on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set fast connectable on - Success 2 - teardown complete Set fast connectable on - Success 2 - done
Set fast connectable on - Success 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set fast connectable on - Success 3 - setup Set fast connectable on - Success 3 - setup complete Set fast connectable on - Success 3 - run
Registering new settings notification
Test condition added, total 1
Sending Set Fast Connectable (0x0008)
Test condition added, total 2
Set Fast Connectable (0x0008): Success (0x00) Test condition complete, 1 left
New settings 0x00000084 received Unregistering new settings notification Test condition complete, 0 left
Set fast connectable on - Success 3 - test passed Set fast connectable on - Success 3 - teardown
Index Removed callback
Index: 0x0000
Set fast connectable on - Success 3 - teardown complete Set fast connectable on - Success 3 - done
Set fast connectable on - Invalid Params 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set fast connectable on - Invalid Params 1 - setup Set fast connectable on - Invalid Params 1 - setup complete Set fast connectable on - Invalid Params 1 - run
Sending Set Fast Connectable (0x0008)
Test condition added, total 1
Set Fast Connectable (0x0008): Invalid Parameters (0x0d) Test condition complete, 0 left
Set fast connectable on - Invalid Params 1 - test passed Set fast connectable on - Invalid Params 1 - teardown
Index Removed callback
Index: 0x0000
Set fast connectable on - Invalid Params 1 - teardown complete Set fast connectable on - Invalid Params 1 - done
Set fast connectable on - Not Supported 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set fast connectable on - Not Supported 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set fast connectable on - Not Supported 1 - setup complete Set fast connectable on - Not Supported 1 - run
Sending Set Fast Connectable (0x0008)
Test condition added, total 1
Set Fast Connectable (0x0008): Not Supported (0x0c) Test condition complete, 0 left
Set fast connectable on - Not Supported 1 - test passed Set fast connectable on - Not Supported 1 - teardown
Index Removed callback
Index: 0x0000
Set fast connectable on - Not Supported 1 - teardown complete Set fast connectable on - Not Supported 1 - done
Set bondable on - Success - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set bondable on - Success - setup
Set bondable on - Success - setup complete
Set bondable on - Success - run
Registering new settings notification
Test condition added, total 1
Sending Set Bondable (0x0009)
Test condition added, total 2
Set Bondable (0x0009): Success (0x00)
Test condition complete, 1 left
New settings 0x00000090 received
Unregistering new settings notification
Test condition complete, 0 left
Set bondable on - Success - test passed
Set bondable on - Success - teardown
Index Removed callback
Index: 0x0000
Set bondable on - Success - teardown complete
Set bondable on - Success - done
Set bondable on - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set bondable on - Invalid parameters 1 - setup Set bondable on - Invalid parameters 1 - setup complete Set bondable on - Invalid parameters 1 - run
Sending Set Bondable (0x0009)
Test condition added, total 1
Set Bondable (0x0009): Invalid Parameters (0x0d) Test condition complete, 0 left
Set bondable on - Invalid parameters 1 - test passed Set bondable on - Invalid parameters 1 - teardown
Index Removed callback
Index: 0x0000
Set bondable on - Invalid parameters 1 - teardown complete Set bondable on - Invalid parameters 1 - done
Set bondable on - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set bondable on - Invalid parameters 2 - setup Set bondable on - Invalid parameters 2 - setup complete Set bondable on - Invalid parameters 2 - run
Sending Set Bondable (0x0009)
Test condition added, total 1
Set Bondable (0x0009): Invalid Parameters (0x0d) Test condition complete, 0 left
Set bondable on - Invalid parameters 2 - test passed Set bondable on - Invalid parameters 2 - teardown
Index Removed callback
Index: 0x0000
Set bondable on - Invalid parameters 2 - teardown complete Set bondable on - Invalid parameters 2 - done
Set bondable on - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set bondable on - Invalid parameters 3 - setup Set bondable on - Invalid parameters 3 - setup complete Set bondable on - Invalid parameters 3 - run
Sending Set Bondable (0x0009)
Test condition added, total 1
Set Bondable (0x0009): Invalid Parameters (0x0d) Test condition complete, 0 left
Set bondable on - Invalid parameters 3 - test passed Set bondable on - Invalid parameters 3 - teardown
Index Removed callback
Index: 0x0000
Set bondable on - Invalid parameters 3 - teardown complete Set bondable on - Invalid parameters 3 - done
Set bondable on - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set bondable on - Invalid index - setup
Set bondable on - Invalid index - setup complete
Set bondable on - Invalid index - run
Sending Set Bondable (0x0009)
Test condition added, total 1
Set Bondable (0x0009): Invalid Index (0x11)
Test condition complete, 0 left
Set bondable on - Invalid index - test passed
Set bondable on - Invalid index - teardown
Index Removed callback
Index: 0x0000
Set bondable on - Invalid index - teardown complete Set bondable on - Invalid index - done
Set discoverable on - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Invalid parameters 1 - setup Set discoverable on - Invalid parameters 1 - setup complete Set discoverable on - Invalid parameters 1 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Invalid Parameters (0x0d) Test condition complete, 0 left
Set discoverable on - Invalid parameters 1 - test passed Set discoverable on - Invalid parameters 1 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Invalid parameters 1 - teardown complete Set discoverable on - Invalid parameters 1 - done
Set discoverable on - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Invalid parameters 2 - setup Set discoverable on - Invalid parameters 2 - setup complete Set discoverable on - Invalid parameters 2 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Invalid Parameters (0x0d) Test condition complete, 0 left
Set discoverable on - Invalid parameters 2 - test passed Set discoverable on - Invalid parameters 2 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Invalid parameters 2 - teardown complete Set discoverable on - Invalid parameters 2 - done
Set discoverable on - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Invalid parameters 3 - setup Set discoverable on - Invalid parameters 3 - setup complete Set discoverable on - Invalid parameters 3 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Invalid Parameters (0x0d) Test condition complete, 0 left
Set discoverable on - Invalid parameters 3 - test passed Set discoverable on - Invalid parameters 3 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Invalid parameters 3 - teardown complete Set discoverable on - Invalid parameters 3 - done
Set discoverable on - Invalid parameters 4 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Invalid parameters 4 - setup Set discoverable on - Invalid parameters 4 - setup complete Set discoverable on - Invalid parameters 4 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Invalid Parameters (0x0d) Test condition complete, 0 left
Set discoverable on - Invalid parameters 4 - test passed Set discoverable on - Invalid parameters 4 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Invalid parameters 4 - teardown complete Set discoverable on - Invalid parameters 4 - done
Set discoverable on - Not powered 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Not powered 1 - setup Set discoverable on - Not powered 1 - setup complete Set discoverable on - Not powered 1 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Not Powered (0x0f) Test condition complete, 0 left
Set discoverable on - Not powered 1 - test passed Set discoverable on - Not powered 1 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Not powered 1 - teardown complete Set discoverable on - Not powered 1 - done
Set discoverable on - Not powered 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Not powered 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set discoverable on - Not powered 2 - setup complete Set discoverable on - Not powered 2 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Not Powered (0x0f) Test condition complete, 0 left
Set discoverable on - Not powered 2 - test passed Set discoverable on - Not powered 2 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Not powered 2 - teardown complete Set discoverable on - Not powered 2 - done
Set discoverable on - Rejected 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Rejected 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set discoverable on - Rejected 1 - setup complete
Set discoverable on - Rejected 1 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Rejected (0x0b)
Test condition complete, 0 left
Set discoverable on - Rejected 1 - test passed
Set discoverable on - Rejected 1 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Rejected 1 - teardown complete Set discoverable on - Rejected 1 - done
Set discoverable on - Rejected 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Rejected 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set discoverable on - Rejected 2 - setup complete
Set discoverable on - Rejected 2 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Rejected (0x0b)
Test condition complete, 0 left
Set discoverable on - Rejected 2 - test passed
Set discoverable on - Rejected 2 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Rejected 2 - teardown complete Set discoverable on - Rejected 2 - done
Set discoverable on - Rejected 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Rejected 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set discoverable on - Rejected 3 - setup complete
Set discoverable on - Rejected 3 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Rejected (0x0b)
Test condition complete, 0 left
Set discoverable on - Rejected 3 - test passed
Set discoverable on - Rejected 3 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Rejected 3 - teardown complete Set discoverable on - Rejected 3 - done
Set discoverable on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set discoverable on - Success 1 - setup complete
Set discoverable on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Discoverable (0x0006)
Test condition added, total 2
Set Discoverable (0x0006): Success (0x00)
Test condition complete, 1 left
New settings 0x0000008a received
Unregistering new settings notification
Test condition complete, 0 left
Set discoverable on - Success 1 - test passed
Set discoverable on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on - Success 1 - teardown complete Set discoverable on - Success 1 - done
Set discoverable on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set discoverable on - Success 2 - setup complete
Set discoverable on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Discoverable (0x0006)
Test condition added, total 3
HCI Command 0x0c3a length 4
HCI Command 0x0c1a length 1
Test condition complete, 2 left
Set Discoverable (0x0006): Success (0x00)
Test condition complete, 1 left
New settings 0x0000008b received
Unregistering new settings notification
Test condition complete, 0 left
Set discoverable on - Success 2 - test passed
Set discoverable on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set discoverable on - Success 2 - teardown complete Set discoverable on - Success 2 - done
Set discoverable on (LE) - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set discoverable on (LE) - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set discoverable on (LE) - Success 1 - setup complete Set discoverable on (LE) - Success 1 - run
Registering HCI command callback
Test condition added, total 1
Sending Set Discoverable (0x0006)
Test condition added, total 2
HCI Command 0x2008 length 32
Test condition complete, 1 left
Set Discoverable (0x0006): Success (0x00) Test condition complete, 0 left
Set discoverable on (LE) - Success 1 - test passed Set discoverable on (LE) - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set discoverable on (LE) - Success 1 - teardown complete Set discoverable on (LE) - Success 1 - done
Set discoverable off - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable off - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set discoverable off - Success 1 - setup complete
Set discoverable off - Success 1 - run
Sending Set Discoverable (0x0006)
Test condition added, total 1
Set Discoverable (0x0006): Success (0x00)
Test condition complete, 0 left
Set discoverable off - Success 1 - test passed
Set discoverable off - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set discoverable off - Success 1 - teardown complete Set discoverable off - Success 1 - done
Set discoverable off - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set discoverable off - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set discoverable off - Success 2 - setup complete
Set discoverable off - Success 2 - run
Registering HCI command callback
Test condition added, total 1
Sending Set Discoverable (0x0006)
Test condition added, total 2
HCI Command 0x0c1a length 1
Test condition complete, 1 left
Set Discoverable (0x0006): Success (0x00)
Test condition complete, 0 left
Set discoverable off - Success 2 - test passed
Set discoverable off - Success 2 - teardown
Index Removed callback
Index: 0x0000
Set discoverable off - Success 2 - teardown complete Set discoverable off - Success 2 - done
Set limited discoverable on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set limited discoverable on - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set limited discoverable on - Success 1 - setup complete Set limited discoverable on - Success 1 - run
Registering HCI command callback
Test condition added, total 1
Sending Set Discoverable (0x0006)
Test condition added, total 2
HCI Command 0x0c3a length 4
HCI Command 0x0c1a length 1
Test condition complete, 1 left
HCI Command 0x0c24 length 3
Set Discoverable (0x0006): Success (0x00) Test condition complete, 0 left
Set limited discoverable on - Success 1 - test passed Set limited discoverable on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set limited discoverable on - Success 1 - teardown complete Set limited discoverable on - Success 1 - done
Set limited discoverable on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set limited discoverable on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set limited discoverable on - Success 2 - setup complete Set limited discoverable on - Success 2 - run
Registering HCI command callback
Test condition added, total 1
Sending Set Discoverable (0x0006)
Test condition added, total 2
HCI Command 0x0c3a length 4
Test condition complete, 1 left
HCI Command 0x0c1a length 1
HCI Command 0x0c24 length 3
Set Discoverable (0x0006): Success (0x00) Test condition complete, 0 left
Set limited discoverable on - Success 2 - test passed Set limited discoverable on - Success 2 - teardown
Index Removed callback
Index: 0x0000
Set limited discoverable on - Success 2 - teardown complete Set limited discoverable on - Success 2 - done
Set limited discoverable on - Success 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set limited discoverable on - Success 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set limited discoverable on - Success 3 - setup complete Set limited discoverable on - Success 3 - run
Registering HCI command callback
Test condition added, total 1
Sending Set Discoverable (0x0006)
Test condition added, total 2
HCI Command 0x0c3a length 4
HCI Command 0x0c1a length 1
HCI Command 0x0c24 length 3
Test condition complete, 1 left
Set Discoverable (0x0006): Success (0x00) Test condition complete, 0 left
Set limited discoverable on - Success 3 - test passed Set limited discoverable on - Success 3 - teardown
Index Removed callback
Index: 0x0000
Set limited discoverable on - Success 3 - teardown complete Set limited discoverable on - Success 3 - done
Set limited discoverable on (LE) - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001be1b
Current settings: 0x00000200
Class: 0x000000
Name:
Short name: Set limited discoverable on (LE) - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set limited discoverable on (LE) - Success 1 - setup complete Set limited discoverable on (LE) - Success 1 - run
Registering HCI command callback
Test condition added, total 1
Sending Set Discoverable (0x0006)
Test condition added, total 2
HCI Command 0x2008 length 32
Test condition complete, 1 left
Set Discoverable (0x0006): Success (0x00)
Test condition complete, 0 left
Set limited discoverable on (LE) - Success 1 - test passed Set limited discoverable on (LE) - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set limited discoverable on (LE) - Success 1 - teardown complete Set limited discoverable on (LE) - Success 1 - done
Set link security on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security on - Success 1 - setup
Set link security on - Success 1 - setup complete
Set link security on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Link Security (0x000a)
Test condition added, total 2
Set Link Security (0x000a): Success (0x00)
Test condition complete, 1 left
New settings 0x000000a0 received
Unregistering new settings notification
Test condition complete, 0 left
Set link security on - Success 1 - test passed
Set link security on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set link security on - Success 1 - teardown complete Set link security on - Success 1 - done
Set link security on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set link security on - Success 2 - setup complete
Set link security on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Link Security (0x000a)
Test condition added, total 3
HCI Command 0x0c20 length 1
Test condition complete, 2 left
Set Link Security (0x000a): Success (0x00)
Test condition complete, 1 left
New settings 0x000000a1 received
Unregistering new settings notification
Test condition complete, 0 left
Set link security on - Success 2 - test passed
Set link security on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set link security on - Success 2 - teardown complete Set link security on - Success 2 - done
Set link security on - Success 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security on - Success 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set link security on - Success 3 - setup complete
Set link security on - Success 3 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Powered (0x0005)
Test condition added, total 3
HCI Command 0x0c20 length 1
Test condition complete, 2 left
HCI Command 0x0c13 length 248
Set Powered (0x0005): Success (0x00)
Test condition complete, 1 left
New settings 0x000000a1 received
Unregistering new settings notification
Test condition complete, 0 left
Set link security on - Success 3 - test passed
Set link security on - Success 3 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set link security on - Success 3 - teardown complete Set link security on - Success 3 - done
Set link security on - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security on - Invalid parameters 1 - setup Set link security on - Invalid parameters 1 - setup complete Set link security on - Invalid parameters 1 - run
Sending Set Link Security (0x000a)
Test condition added, total 1
Set Link Security (0x000a): Invalid Parameters (0x0d) Test condition complete, 0 left
Set link security on - Invalid parameters 1 - test passed Set link security on - Invalid parameters 1 - teardown
Index Removed callback
Index: 0x0000
Set link security on - Invalid parameters 1 - teardown complete Set link security on - Invalid parameters 1 - done
Set link security on - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security on - Invalid parameters 2 - setup Set link security on - Invalid parameters 2 - setup complete Set link security on - Invalid parameters 2 - run
Sending Set Link Security (0x000a)
Test condition added, total 1
Set Link Security (0x000a): Invalid Parameters (0x0d) Test condition complete, 0 left
Set link security on - Invalid parameters 2 - test passed Set link security on - Invalid parameters 2 - teardown
Index Removed callback
Index: 0x0000
Set link security on - Invalid parameters 2 - teardown complete Set link security on - Invalid parameters 2 - done
Set link security on - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security on - Invalid parameters 3 - setup Set link security on - Invalid parameters 3 - setup complete Set link security on - Invalid parameters 3 - run
Sending Set Link Security (0x000a)
Test condition added, total 1
Set Link Security (0x000a): Invalid Parameters (0x0d) Test condition complete, 0 left
Set link security on - Invalid parameters 3 - test passed Set link security on - Invalid parameters 3 - teardown
Index Removed callback
Index: 0x0000
Set link security on - Invalid parameters 3 - teardown complete Set link security on - Invalid parameters 3 - done
Set link security on - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security on - Invalid index - setup Set link security on - Invalid index - setup complete Set link security on - Invalid index - run
Sending Set Link Security (0x000a)
Test condition added, total 1
Set Link Security (0x000a): Invalid Index (0x11) Test condition complete, 0 left
Set link security on - Invalid index - test passed Set link security on - Invalid index - teardown
Index Removed callback
Index: 0x0000
Set link security on - Invalid index - teardown complete Set link security on - Invalid index - done
Set link security off - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security off - Success 1 - setup
Initial settings completed
Test setup condition added, total 1 Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set link security off - Success 1 - setup complete Set link security off - Success 1 - run
Registering new settings notification Test condition added, total 1
Sending Set Link Security (0x000a)
Test condition added, total 2
Set Link Security (0x000a): Success (0x00) Test condition complete, 1 left
New settings 0x00000080 received Unregistering new settings notification Test condition complete, 0 left
Set link security off - Success 1 - test passed Set link security off - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set link security off - Success 1 - teardown complete Set link security off - Success 1 - done
Set link security off - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set link security off - Success 2 - setup
Initial settings completed
Test setup condition added, total 1 Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set link security off - Success 2 - setup complete Set link security off - Success 2 - run
Registering new settings notification Test condition added, total 1 Registering HCI command callback
Test condition added, total 2
Sending Set Link Security (0x000a)
Test condition added, total 3
HCI Command 0x0c20 length 1
Test condition complete, 2 left
Set Link Security (0x000a): Success (0x00) Test condition complete, 1 left
New settings 0x00000081 received Unregistering new settings notification Test condition complete, 0 left
Set link security off - Success 2 - test passed Set link security off - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set link security off - Success 2 - teardown complete Set link security off - Success 2 - done
Set SSP on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set SSP on - Success 1 - setup
Set SSP on - Success 1 - setup complete
Set SSP on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Secure Simple Pairing (0x000b) Test condition added, total 2
Set Secure Simple Pairing (0x000b): Success (0x00) Test condition complete, 1 left
New settings 0x000000c0 received Unregistering new settings notification Test condition complete, 0 left
Set SSP on - Success 1 - test passed
Set SSP on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set SSP on - Success 1 - teardown complete
Set SSP on - Success 1 - done
Set SSP on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set SSP on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00) Test setup condition complete, 0 left
Set SSP on - Success 2 - setup complete
Set SSP on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Secure Simple Pairing (0x000b) Test condition added, total 3
HCI Command 0x0c56 length 1
Test condition complete, 2 left
Set Secure Simple Pairing (0x000b): Success (0x00) Test condition complete, 1 left
New settings 0x000000c1 received Unregistering new settings notification Test condition complete, 0 left
Set SSP on - Success 2 - test passed
HCI Command 0x0c52 length 241
Set SSP on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set SSP on - Success 2 - teardown complete
Set SSP on - Success 2 - done
Set SSP on - Success 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set SSP on - Success 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set SSP on - Success 3 - setup complete
Set SSP on - Success 3 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Powered (0x0005)
Test condition added, total 3
HCI Command 0x0c56 length 1
Test condition complete, 2 left
HCI Command 0x0c13 length 248
HCI Command 0x0c52 length 241
Set Powered (0x0005): Success (0x00)
Test condition complete, 1 left
New settings 0x000000c1 received
Unregistering new settings notification
Test condition complete, 0 left
Set SSP on - Success 3 - test passed
Set SSP on - Success 3 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set SSP on - Success 3 - teardown complete
Set SSP on - Success 3 - done
Set SSP on - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set SSP on - Invalid parameters 1 - setup
Set SSP on - Invalid parameters 1 - setup complete Set SSP on - Invalid parameters 1 - run
Sending Set Secure Simple Pairing (0x000b)
Test condition added, total 1
Set Secure Simple Pairing (0x000b): Invalid Parameters (0x0d) Test condition complete, 0 left
Set SSP on - Invalid parameters 1 - test passed
Set SSP on - Invalid parameters 1 - teardown
Index Removed callback
Index: 0x0000
Set SSP on - Invalid parameters 1 - teardown complete Set SSP on - Invalid parameters 1 - done
Set SSP on - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set SSP on - Invalid parameters 2 - setup
Set SSP on - Invalid parameters 2 - setup complete Set SSP on - Invalid parameters 2 - run
Sending Set Secure Simple Pairing (0x000b)
Test condition added, total 1
Set Secure Simple Pairing (0x000b): Invalid Parameters (0x0d) Test condition complete, 0 left
Set SSP on - Invalid parameters 2 - test passed
Set SSP on - Invalid parameters 2 - teardown
Index Removed callback
Index: 0x0000
Set SSP on - Invalid parameters 2 - teardown complete Set SSP on - Invalid parameters 2 - done
Set SSP on - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set SSP on - Invalid parameters 3 - setup
Set SSP on - Invalid parameters 3 - setup complete Set SSP on - Invalid parameters 3 - run
Sending Set Secure Simple Pairing (0x000b)
Test condition added, total 1
Set Secure Simple Pairing (0x000b): Invalid Parameters (0x0d) Test condition complete, 0 left
Set SSP on - Invalid parameters 3 - test passed
Set SSP on - Invalid parameters 3 - teardown
Index Removed callback
Index: 0x0000
Set SSP on - Invalid parameters 3 - teardown complete Set SSP on - Invalid parameters 3 - done
Set SSP on - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set SSP on - Invalid index - setup
Set SSP on - Invalid index - setup complete
Set SSP on - Invalid index - run
Sending Set Secure Simple Pairing (0x000b)
Test condition added, total 1
Set Secure Simple Pairing (0x000b): Invalid Index (0x11) Test condition complete, 0 left
Set SSP on - Invalid index - test passed
Set SSP on - Invalid index - teardown
Index Removed callback
Index: 0x0000
Set SSP on - Invalid index - teardown complete
Set SSP on - Invalid index - done
Set Secure Connections on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections on - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections on - Success 1 - setup complete Set Secure Connections on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Secure Connections (0x002d) Test condition added, total 2
Set Secure Connections (0x002d): Success (0x00) Test condition complete, 1 left
New settings 0x000008c0 received Unregistering new settings notification Test condition complete, 0 left
Set Secure Connections on - Success 1 - test passed Set Secure Connections on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set Secure Connections on - Success 1 - teardown complete Set Secure Connections on - Success 1 - done
Set Secure Connections on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections on - Success 2 - setup complete Set Secure Connections on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Secure Connections (0x002d) Test condition added, total 3
HCI Command 0x0c7a length 1
Test condition complete, 2 left
Set Secure Connections (0x002d): Success (0x00) Test condition complete, 1 left
New settings 0x000008c1 received Unregistering new settings notification Test condition complete, 0 left
Set Secure Connections on - Success 2 - test passed Set Secure Connections on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set Secure Connections on - Success 2 - teardown complete Set Secure Connections on - Success 2 - done
Set Secure Connections on - Invalid params 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections on - Invalid params 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections on - Invalid params 1 - setup complete Set Secure Connections on - Invalid params 1 - run
Sending Set Secure Connections (0x002d)
Test condition added, total 1
Set Secure Connections (0x002d): Invalid Parameters (0x0d) Test condition complete, 0 left
Set Secure Connections on - Invalid params 1 - test passed Set Secure Connections on - Invalid params 1 - teardown
Index Removed callback
Index: 0x0000
Set Secure Connections on - Invalid params 1 - teardown complete Set Secure Connections on - Invalid params 1 - done
Set Secure Connections on - Invalid params 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections on - Invalid params 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections on - Invalid params 2 - setup complete Set Secure Connections on - Invalid params 2 - run
Sending Set Secure Connections (0x002d)
Test condition added, total 1
Set Secure Connections (0x002d): Invalid Parameters (0x0d) Test condition complete, 0 left
Set Secure Connections on - Invalid params 2 - test passed Set Secure Connections on - Invalid params 2 - teardown
Index Removed callback
Index: 0x0000
Set Secure Connections on - Invalid params 2 - teardown complete Set Secure Connections on - Invalid params 2 - done
Set Secure Connections on - Invalid params 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections on - Invalid params 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections on - Invalid params 3 - setup complete Set Secure Connections on - Invalid params 3 - run
Sending Set Secure Connections (0x002d)
Test condition added, total 1
Set Secure Connections (0x002d): Invalid Parameters (0x0d) Test condition complete, 0 left
Set Secure Connections on - Invalid params 3 - test passed Set Secure Connections on - Invalid params 3 - teardown
Index Removed callback
Index: 0x0000
Set Secure Connections on - Invalid params 3 - teardown complete Set Secure Connections on - Invalid params 3 - done
Set Secure Connections on - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections on - Invalid index - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections on - Invalid index - setup complete Set Secure Connections on - Invalid index - run
Sending Set Secure Connections (0x002d)
Test condition added, total 1
Set Secure Connections (0x002d): Invalid Index (0x11) Test condition complete, 0 left
Set Secure Connections on - Invalid index - test passed Set Secure Connections on - Invalid index - teardown
Index Removed callback
Index: 0x0000
Set Secure Connections on - Invalid index - teardown complete Set Secure Connections on - Invalid index - done
Set Secure Connections on - Not supported 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections on - Not supported 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections on - Not supported 1 - setup complete Set Secure Connections on - Not supported 1 - run
Sending Set Secure Connections (0x002d)
Test condition added, total 1
Set Secure Connections (0x002d): Not Supported (0x0c) Test condition complete, 0 left
Set Secure Connections on - Not supported 1 - test passed Set Secure Connections on - Not supported 1 - teardown
Index Removed callback
Index: 0x0000
Set Secure Connections on - Not supported 1 - teardown complete Set Secure Connections on - Not supported 1 - done
Set Secure Connections on - Not supported 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x05
Manufacturer: 0x003f
Supported settings: 0x000110ff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections on - Not supported 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections on - Not supported 2 - setup complete Set Secure Connections on - Not supported 2 - run
Sending Set Secure Connections (0x002d)
Test condition added, total 1
Set Secure Connections (0x002d): Not Supported (0x0c) Test condition complete, 0 left
Set Secure Connections on - Not supported 2 - test passed Set Secure Connections on - Not supported 2 - teardown
Index Removed callback
Index: 0x0000
Set Secure Connections on - Not supported 2 - teardown complete Set Secure Connections on - Not supported 2 - done
Set Secure Connections Only on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections Only on - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections Only on - Success 1 - setup complete Set Secure Connections Only on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Secure Connections (0x002d)
Test condition added, total 2
Set Secure Connections (0x002d): Success (0x00) Test condition complete, 1 left
New settings 0x000008c0 received
Unregistering new settings notification
Test condition complete, 0 left
Set Secure Connections Only on - Success 1 - test passed Set Secure Connections Only on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set Secure Connections Only on - Success 1 - teardown complete Set Secure Connections Only on - Success 1 - done
Set Secure Connections Only on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Secure Connections Only on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Secure Connections Only on - Success 2 - setup complete Set Secure Connections Only on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Secure Connections (0x002d)
Test condition added, total 3
HCI Command 0x0c7a length 1
Test condition complete, 2 left
Set Secure Connections (0x002d): Success (0x00) Test condition complete, 1 left
New settings 0x000008c1 received
Unregistering new settings notification
Test condition complete, 0 left
Set Secure Connections Only on - Success 2 - test passed Set Secure Connections Only on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set Secure Connections Only on - Success 2 - teardown complete Set Secure Connections Only on - Success 2 - done
Set High Speed on - Success - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Expected bit 8 not supported
Expected supported settings: 0x0001beff != 0x0001bfff
Set High Speed on - Success - pre setup failed
Index Removed callback
Index: 0x0000
Set High Speed on - Success - done
Set High Speed on - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Expected bit 8 not supported
Expected supported settings: 0x0001beff != 0x0001bfff
Set High Speed on - Invalid parameters 1 - pre setup failed
Index Removed callback
Index: 0x0000
Set High Speed on - Invalid parameters 1 - done
Set High Speed on - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Expected bit 8 not supported
Expected supported settings: 0x0001beff != 0x0001bfff
Set High Speed on - Invalid parameters 2 - pre setup failed
Index Removed callback
Index: 0x0000
Set High Speed on - Invalid parameters 2 - done
Set High Speed on - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Expected bit 8 not supported
Expected supported settings: 0x0001beff != 0x0001bfff
Set High Speed on - Invalid parameters 3 - pre setup failed
Index Removed callback
Index: 0x0000
Set High Speed on - Invalid parameters 3 - done
Set High Speed on - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Expected bit 8 not supported
Expected supported settings: 0x0001beff != 0x0001bfff
Set High Speed on - Invalid index - pre setup failed
Index Removed callback
Index: 0x0000
Set High Speed on - Invalid index - done
Set Low Energy on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Low Energy on - Success 1 - setup
Set Low Energy on - Success 1 - setup complete
Set Low Energy on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Low Energy (0x000d)
Test condition added, total 2
Set Low Energy (0x000d): Success (0x00)
Test condition complete, 1 left
New settings 0x00000280 received
Unregistering new settings notification
Test condition complete, 0 left
Set Low Energy on - Success 1 - test passed
Set Low Energy on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set Low Energy on - Success 1 - teardown complete
Set Low Energy on - Success 1 - done
Set Low Energy on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Low Energy on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Low Energy on - Success 2 - setup complete
Set Low Energy on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Low Energy (0x000d)
Test condition added, total 3
HCI Command 0x0c6d length 2
Test condition complete, 2 left
Set Low Energy (0x000d): Success (0x00)
Test condition complete, 1 left
New settings 0x00000281 received
Unregistering new settings notification
Test condition complete, 0 left
Set Low Energy on - Success 2 - test passed
HCI Command 0x2008 length 32
Set Low Energy on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set Low Energy on - Success 2 - teardown complete
Set Low Energy on - Success 2 - done
Set Low Energy on - Success 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Low Energy on - Success 3 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Low Energy on - Success 3 - setup complete
Set Low Energy on - Success 3 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Powered (0x0005)
Test condition added, total 3
HCI Command 0x0c6d length 2
Test condition complete, 2 left
HCI Command 0x2008 length 32
HCI Command 0x0c13 length 248
Set Powered (0x0005): Success (0x00)
Test condition complete, 1 left
New settings 0x00000281 received
Unregistering new settings notification
Test condition complete, 0 left
Set Low Energy on - Success 3 - test passed
Set Low Energy on - Success 3 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set Low Energy on - Success 3 - teardown complete
Set Low Energy on - Success 3 - done
Set Low Energy on - Invalid parameters 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Low Energy on - Invalid parameters 1 - setup Set Low Energy on - Invalid parameters 1 - setup complete Set Low Energy on - Invalid parameters 1 - run
Sending Set Low Energy (0x000d)
Test condition added, total 1
Set Low Energy (0x000d): Invalid Parameters (0x0d) Test condition complete, 0 left
Set Low Energy on - Invalid parameters 1 - test passed Set Low Energy on - Invalid parameters 1 - teardown
Index Removed callback
Index: 0x0000
Set Low Energy on - Invalid parameters 1 - teardown complete Set Low Energy on - Invalid parameters 1 - done
Set Low Energy on - Invalid parameters 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Low Energy on - Invalid parameters 2 - setup Set Low Energy on - Invalid parameters 2 - setup complete Set Low Energy on - Invalid parameters 2 - run
Sending Set Low Energy (0x000d)
Test condition added, total 1
Set Low Energy (0x000d): Invalid Parameters (0x0d) Test condition complete, 0 left
Set Low Energy on - Invalid parameters 2 - test passed Set Low Energy on - Invalid parameters 2 - teardown
Index Removed callback
Index: 0x0000
Set Low Energy on - Invalid parameters 2 - teardown complete Set Low Energy on - Invalid parameters 2 - done
Set Low Energy on - Invalid parameters 3 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Low Energy on - Invalid parameters 3 - setup Set Low Energy on - Invalid parameters 3 - setup complete Set Low Energy on - Invalid parameters 3 - run
Sending Set Low Energy (0x000d)
Test condition added, total 1
Set Low Energy (0x000d): Invalid Parameters (0x0d) Test condition complete, 0 left
Set Low Energy on - Invalid parameters 3 - test passed Set Low Energy on - Invalid parameters 3 - teardown
Index Removed callback
Index: 0x0000
Set Low Energy on - Invalid parameters 3 - teardown complete Set Low Energy on - Invalid parameters 3 - done
Set Low Energy on - Invalid index - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Low Energy on - Invalid index - setup Set Low Energy on - Invalid index - setup complete Set Low Energy on - Invalid index - run
Sending Set Low Energy (0x000d)
Test condition added, total 1
Set Low Energy (0x000d): Invalid Index (0x11) Test condition complete, 0 left
Set Low Energy on - Invalid index - test passed Set Low Energy on - Invalid index - teardown
Index Removed callback
Index: 0x0000
Set Low Energy on - Invalid index - teardown complete Set Low Energy on - Invalid index - done
Set Advertising on - Success 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Advertising on - Success 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Advertising on - Success 1 - setup complete
Set Advertising on - Success 1 - run
Registering new settings notification
Test condition added, total 1
Sending Set Advertising (0x0029)
Test condition added, total 2
Set Advertising (0x0029): Success (0x00)
Test condition complete, 1 left
New settings 0x00000680 received
Unregistering new settings notification
Test condition complete, 0 left
Set Advertising on - Success 1 - test passed
Set Advertising on - Success 1 - teardown
Index Removed callback
Index: 0x0000
Set Advertising on - Success 1 - teardown complete Set Advertising on - Success 1 - done
Set Advertising on - Success 2 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Advertising on - Success 2 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Advertising on - Success 2 - setup complete
Set Advertising on - Success 2 - run
Registering new settings notification
Test condition added, total 1
Registering HCI command callback
Test condition added, total 2
Sending Set Advertising (0x0029)
Test condition added, total 3
HCI Command 0x2005 length 6
HCI Command 0x2006 length 15
HCI Command 0x200a length 1
Test condition complete, 2 left
Set Advertising (0x0029): Success (0x00)
Test condition complete, 1 left
New settings 0x00000681 received
Unregistering new settings notification
Test condition complete, 0 left
Set Advertising on - Success 2 - test passed
Set Advertising on - Success 2 - teardown
New settings event received
Index Removed callback
Index: 0x0000
Set Advertising on - Success 2 - teardown complete Set Advertising on - Success 2 - done
Set Advertising on - Rejected 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Advertising on - Rejected 1 - setup
Initial settings completed
Test setup condition added, total 1
Client set connectable: Success (0x00)
Test setup condition complete, 0 left
Set Advertising on - Rejected 1 - setup complete
Set Advertising on - Rejected 1 - run
Sending Set Advertising (0x0029)
Test condition added, total 1
Set Advertising (0x0029): Rejected (0x0b)
Test condition complete, 0 left
Set Advertising on - Rejected 1 - test passed
Set Advertising on - Rejected 1 - teardown
Index Removed callback
Index: 0x0000
Set Advertising on - Rejected 1 - teardown complete Set Advertising on - Rejected 1 - done
Set Advertising on - Appearance 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: Set Advertising on - Appearance 1 - setup
Initial settings completed
Setup sending Set Appearance (0x0043) Test setup condition added, total 1
Test setup condition complete, 0 left
Set Advertising on - Appearance 1 - setup complete Set Advertising on - Appearance 1 - run
Registering HCI command callback
Test condition added, total 1
Sending Set Advertising (0x0029)
Test condition added, total 2
HCI Command 0x2009 length 32
Test condition complete, 1 left
HCI Command 0x2005 length 6
HCI Command 0x2006 length 15
HCI Command 0x200a length 1
Set Advertising (0x0029): Success (0x00) Test condition complete, 0 left
Set Advertising on - Appearance 1 - test passed Set Advertising on - Appearance 1 - teardown
Index Removed callback
Index: 0x0000
Set Advertising on - Appearance 1 - teardown complete Set Advertising on - Appearance 1 - done
Set Advertising on - Local name 1 - init
Read Version callback
Status: Success (0x00)
Version 1.20
Read Commands callback
Status: Success (0x00)
Read Index List callback
Status: Success (0x00)
Index Added callback
Index: 0x0000
Read Info callback
Status: Success (0x00)
Address: 00:AA:01:00:00:00
Version: 0x09
Manufacturer: 0x003f
Supported settings: 0x0001beff
Current settings: 0x00000080
Class: 0x000000
Name:
Short name: 14,972 lines not shown · raw message
Part of this message is not shown here. View the raw message.
PATCH v3 2/7 regulator: qca6390: add support for QCA639x powerup sequence
In reply to Dmitry BaryshkovQualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
--- drivers/regulator/Kconfig | 13 +++ drivers/regulator/Makefile | 1 + drivers/regulator/qcom-qca639x.c | 157 +++++++++++++++++++++++++++++++ 3 files changed, 171 insertions(+) create mode 100644 drivers/regulator/qcom-qca639x.c
drivers/regulator/Kconfig +13 -0
@@ -909,6 +909,19 @@ config REGULATOR_PWM This driver supports PWM controlled voltage regulators. PWM duty cycle can increase or decrease the voltage. +config REGULATOR_QCOM_QCA639X + tristate "Qualcomm QCA639x WiFi/Bluetooth module support" + help + If you say yes to this option, support will be included for Qualcomm + QCA639x family of WiFi and Bluetooth SoCs. Note, this driver supports + only power control for this SoC, you still have to enable individual + Bluetooth and WiFi drivers. This driver is only necessary on ARM + platforms with this chip. PCIe cards handle power sequencing on their + own. + + Say M here if you want to include support for QCA639x chips as a + module. This will build a module called "qcom-qca639x". + config REGULATOR_QCOM_RPM tristate "Qualcomm RPM regulator driver" depends on MFD_QCOM_RPM
drivers/regulator/Makefile +1 -0
@@ -99,6 +99,7 @@ obj-$(CONFIG_REGULATOR_MT6380) += mt6380-regulator.o obj-$(CONFIG_REGULATOR_MT6397) += mt6397-regulator.o obj-$(CONFIG_REGULATOR_MTK_DVFSRC) += mtk-dvfsrc-regulator.o obj-$(CONFIG_REGULATOR_QCOM_LABIBB) += qcom-labibb-regulator.o +obj-$(CONFIG_REGULATOR_QCOM_QCA639X) += qcom-qca639x.o obj-$(CONFIG_REGULATOR_QCOM_RPM) += qcom_rpm-regulator.o obj-$(CONFIG_REGULATOR_QCOM_RPMH) += qcom-rpmh-regulator.o obj-$(CONFIG_REGULATOR_QCOM_SMD_RPM) += qcom_smd-regulator.o
drivers/regulator/qcom-qca639x.c new file +157 -0
157 lines not on this page · raw message
Signature · 1 line
2.30.2
Mark Brown
maintainerRe: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 4 lines · Dmitry Baryshkov
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Are you sure this is a regulator and not a MFD? It appears to be a consumer driver that turns on and off a bunch of regulators en masse which for some reason exposes that on/off control as a single supply. This looks like it'd be much more appropriate to implement as a MFD or possibly power domain with the subdevices using runtime PM, it's clearly not a regulator.
drivers/regulator/qcom-qca639x.c line 4
Quoted 4 lines
drivers/regulator/qcom-qca639x.c new file +4
-0+// SPDX-License-Identifier: GPL-2.0-only +/* +* Copyright (c) 2021, Linaro Limited +*/
Please make the entire comment a C++ one so things look more intentional.
drivers/regulator/qcom-qca639x.c line 57
Quoted 10 lines
drivers/regulator/qcom-qca639x.c new file +10
-0+static int qca6390_enable (struct regulator_dev *rdev) +{ +struct qca6390_data *data =rdev_get_drvdata (rdev); +int ret; + + ret =regulator_bulk_enable (data->num_vregs, data->regulators); +if (ret) { +dev_err (data->dev,"Failed to enable regulators" ); +return ret; + }
The regulator API is *not* recursive, I am astonished this works.
drivers/regulator/qcom-qca639x.c line 60
Quoted 2 lines
drivers/regulator/qcom-qca639x.c new file +2
-0+/* Wait for 1ms before toggling enable pins. */ +usleep_range (1000 ,2000 );
There's core support for delays after power on, better to use it.
drivers/regulator/qcom-qca639x.c line 62
Quoted 1 line
drivers/regulator/qcom-qca639x.c new file +1
-0+ data->enable_counter++;
You shouldn't assume that enable and disable calls are matched.
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 8 lines · Mark Brown
Quoted 4 lines · Dmitry Baryshkov
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Quoted 6 lines
Are you sure this is a regulator and not a MFD? It appears to be a consumer driver that turns on and off a bunch of regulators en masse which for some reason exposes that on/off control as a single supply. This looks like it'd be much more appropriate to implement as a MFD or possibly power domain with the subdevices using runtime PM, it's clearly not a regulator.
First attempt was designed to be an MFD. And Lee clearly stated that this is wrong:
"This is not an MFD, since it utilised neither the MFD API nor of_platform_populate() to register child devices." [1]
I've attempted implementing that as a genpd (in previous iterations), but it results in worse design. PCIe controllers are not expected to handle power domains for EP devices, especially in cases when the PD must come up before the controller does link training and bus probe. I've tried following Rob's suggestions on implementing things clearly, but doing so results in too big restructure just for a single device.
Quoted 7 lines
drivers/regulator/qcom-qca639x.c line 4
Quoted 4 lines
drivers/regulator/qcom-qca639x.c new file +4
-0+// SPDX-License-Identifier: GPL-2.0-only +/* +* Copyright (c) 2021, Linaro Limited +*/ Please make the entire comment a C++ one so things look more intentional.
Ack.
Quoted 13 lines
drivers/regulator/qcom-qca639x.c line 57
Quoted 11 lines
drivers/regulator/qcom-qca639x.c new file +10
-0+static int qca6390_enable (struct regulator_dev *rdev) +{ +struct qca6390_data *data =rdev_get_drvdata (rdev); +int ret; + + ret =regulator_bulk_enable (data->num_vregs, data->regulators); +if (ret) { +dev_err (data->dev,"Failed to enable regulators" ); +return ret; + }The regulator API is *not* recursive, I am astonished this works.
It does, even with lockdep enabled. Moreover BT regularly does disable and enable this regulator, so both enable and disable paths were well tested.
Should I change this into some internal call to remove API recursiveness?
Quoted 5 lines
drivers/regulator/qcom-qca639x.c line 60
Quoted 3 lines
drivers/regulator/qcom-qca639x.c new file +2
-0+/* Wait for 1ms before toggling enable pins. */ +usleep_range (1000 ,2000 );There's core support for delays after power on, better to use it.
Ack.
Quoted 4 lines
Quoted 2 lines
+ data->enable_counter++;
You shouldn't assume that enable and disable calls are matched.
Ack.
--
With best wishes
Dmitry
Mark Brown
maintainerRe: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 15 lines · Dmitry Baryshkov
Quoted 7 lines · Mark Brown
Quoted 4 lines · Dmitry Baryshkov
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Quoted 6 lines
Are you sure this is a regulator and not a MFD? It appears to be a consumer driver that turns on and off a bunch of regulators en masse which for some reason exposes that on/off control as a single supply. This looks like it'd be much more appropriate to implement as a MFD or possibly power domain with the subdevices using runtime PM, it's clearly not a regulator.
Quoted 4 lines
First attempt was designed to be an MFD. And Lee clearly stated that this is wrong:
"This is not an MFD, since it utilised neither the MFD API norof_platform_populate()to register child devices." [1]
Well, perhaps it should do one of those things then? Like I say this is very clearly not a regulator, it looks like a consumer of some kind. The regulator API isn't there just to absorb things that need reference counting, it's there to represent things providing supplies. This seems to be very clearly not a supply given that it's grouping together a bunch of other supplies and switching them on and off together without providing a clear output supply.
Quoted 2 lines
I've tried following Rob's suggestions on implementing things clearly, but doing so results in too big restructure just for a single device.
I don't know what that suggestion was? If there's only one device that uses this why is it not implemented as part of that device?
Quoted 11 lines
Quoted 10 lines
Quoted 10 lines
drivers/regulator/qcom-qca639x.c new file +9
-0+static int qca6390_enable (struct regulator_dev *rdev) +{ +struct qca6390_data *data =rdev_get_drvdata (rdev); +int ret; + ret =regulator_bulk_enable (data->num_vregs, data->regulators); +if (ret) { +dev_err (data->dev,"Failed to enable regulators" ); +return ret; + }
Quoted 6 lines
Quoted 1 line
The regulator API is *not* recursive, I am astonished this works.
It does, even with lockdep enabled. Moreover BT regularly does disable and enable this regulator, so both enable and disable paths were well tested.
Should I change this into some internal call to remove API recursiveness?
You should not be implementing this as a regulator at all.
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 17 lines · Mark Brown
Quoted 14 lines · Dmitry Baryshkov
Quoted 13 lines · Mark Brown
Quoted 4 lines · Dmitry Baryshkov
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Are you sure this is a regulator and not a MFD? It appears to be a consumer driver that turns on and off a bunch of regulators en masse which for some reason exposes that on/off control as a single supply. This looks like it'd be much more appropriate to implement as a MFD or possibly power domain with the subdevices using runtime PM, it's clearly not a regulator.
Quoted 6 lines
Quoted 4 lines
First attempt was designed to be an MFD. And Lee clearly stated that this is wrong:
"This is not an MFD, since it utilised neither the MFD API norof_platform_populate()to register child devices." [1]Well, perhaps it should do one of those things then?
I don't think so. BT part is just a serdev sitting on top of UART, WiFi is PCIe device (for qca6390). So using MFD API (which primarily targets platform devices) does not seem logical and feasible.
Quoted 7 lines
Like I say this is
very clearly not a regulator, it looks like a consumer of some kind. The regulator API isn't there just to absorb things that need reference counting, it's there to represent things providing supplies. This seems to be very clearly not a supply given that it's grouping together a bunch of other supplies and switching them on and off together without providing a clear output supply.
Ack.
Quoted 5 lines
Quoted 2 lines
I've tried following Rob's suggestions on implementing things clearly, but doing so results in too big restructure just for a single device.
I don't know what that suggestion was? If there's only one device that uses this why is it not implemented as part of that device?
One device = qca6390 (or 91). Because it is still a device sitting on a PCI bus which is typically discoverable, while adding power sequencer to the device driver would demand making the bus fully descibiable (like PCI bus is on Spark).
Quoted 11 lines
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
drivers/regulator/qcom-qca639x.c new file +9
-0+static int qca6390_enable (struct regulator_dev *rdev) +{ +struct qca6390_data *data =rdev_get_drvdata (rdev); +int ret; + ret =regulator_bulk_enable (data->num_vregs, data->regulators); +if (ret) { +dev_err (data->dev,"Failed to enable regulators" ); +return ret; + }
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
The regulator API is *not* recursive, I am astonished this works.
It does, even with lockdep enabled. Moreover BT regularly does disable and enable this regulator, so both enable and disable paths were well tested.
Should I change this into some internal call to remove API recursiveness?You should not be implementing this as a regulator at all.
Ack
Signature · 2 lines
With best wishes Dmitry
Mark Brown
maintainerRe: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 7 lines · Dmitry Baryshkov
Quoted 1 line · Mark Brown
Well, perhaps it should do one of those things then?
I don't think so. BT part is just a serdev sitting on top of UART, WiFi is PCIe device (for qca6390). So using MFD API (which primarily targets platform devices) does not seem logical and feasible.
That really does sound like a MFD - AIUI it's a single chip with multiple interfaces that needs some glue logic to hold it together. It doesn't fit well with the current framework that MFD offers but it's definitely the same sort of one chip in multiple Linux frameworks sort of thing. The only other thing I can think might fit is handling it like a plug in module for a development board (eg, RPi hats) but we've not been doing so great at getting them supported upstream.
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
In reply to Dmitry Baryshkov+ Peter
Quoted 7 lines · Dmitry Baryshkov
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Signed-off-by Dmitry Baryshkov <[email protected]>
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Note that, this isn't specific to the PCIe bus, but rather to all buses that may have discoverable devices attached and which need some kind of pre-power-sequence before they can be discovered/probed. USB, PCIe, SDIO, etc.
Long time ago, we fixed the problem for SDIO (that also can have WiFi, UART, bluetooth chips attached), but unfortunately through an MMC subsystem specific implementation, that can't be re-used in a generic way.
In any case, I have looped in Peter Chen, maybe he can provide us with a better update on how things have moved forward, if at all.
Kind regards
Uffe
[1]
https://www.spinics.net/lists/linux-usb/msg158451.html
Quoted 209 lines
--- drivers/regulator/Kconfig | 13 +++ drivers/regulator/Makefile | 1 + drivers/regulator/qcom-qca639x.c | 157 +++++++++++++++++++++++++++++++ 3 files changed, 171 insertions(+) create mode 100644 drivers/regulator/qcom-qca639x.cdrivers/regulator/Kconfig +13
-0@@ -909,6 +909,19 @@ config REGULATOR_PWM This driver supports PWM controlled voltage regulators. PWM duty cycle can increase or decrease the voltage. +config REGULATOR_QCOM_QCA639X + tristate "Qualcomm QCA639x WiFi/Bluetooth module support" + help + If you say yes to this option, support will be included for Qualcomm + QCA639x family of WiFi and Bluetooth SoCs. Note, this driver supports + only power control for this SoC, you still have to enable individual + Bluetooth and WiFi drivers. This driver is only necessary on ARM + platforms with this chip. PCIe cards handle power sequencing on their + own. + + Say M here if you want to include support for QCA639x chips as a + module. This will build a module called "qcom-qca639x". + config REGULATOR_QCOM_RPM tristate "Qualcomm RPM regulator driver" depends on MFD_QCOM_RPMdrivers/regulator/Makefile +1
-0@@ -99,6 +99,7 @@ obj-$(CONFIG_REGULATOR_MT6380) += mt6380-regulator.o obj-$(CONFIG_REGULATOR_MT6397) += mt6397-regulator.o obj-$(CONFIG_REGULATOR_MTK_DVFSRC) += mtk-dvfsrc-regulator.o obj-$(CONFIG_REGULATOR_QCOM_LABIBB) += qcom-labibb-regulator.o +obj-$(CONFIG_REGULATOR_QCOM_QCA639X) += qcom-qca639x.o obj-$(CONFIG_REGULATOR_QCOM_RPM) += qcom_rpm-regulator.o obj-$(CONFIG_REGULATOR_QCOM_RPMH) += qcom-rpmh-regulator.o obj-$(CONFIG_REGULATOR_QCOM_SMD_RPM) += qcom_smd-regulator.odrivers/regulator/qcom-qca639x.c new file +157
-1@@ -0,0 +1,157 @@ +// SPDX-License-Identifier: GPL-2.0-only +/* +* Copyright (c) 2021, Linaro Limited +*/ +#include <linux/delay.h> +#include <linux/of.h> +#include <linux/platform_device.h> +#include <linux/regulator/consumer.h> +#include <linux/regulator/driver.h> +#include <linux/regulator/of_regulator.h> +#include <linux/slab.h> + +#define MAX_NUM_REGULATORS 8 + +static struct vreg { +const char *name; +unsigned int load_uA; +} vregs[MAX_NUM_REGULATORS ] = { +/* 2.0 V */ + {"vddpcie2" ,15000 }, + {"vddrfa3" ,400000 }, + +/* 0.95 V */ + {"vddaon" ,100000 }, + {"vddpmu" ,1250000 }, + {"vddrfa1" ,200000 }, + +/* 1.35 V */ + {"vddrfa2" ,400000 }, + {"vddpcie1" ,35000 }, + +/* 1.8 V */ + {"vddio" ,20000 }, +}; + +struct qca6390_data { +struct device *dev; +struct regulator_bulk_data regulators[MAX_NUM_REGULATORS ]; +size_t num_vregs; + +struct regulator_desc desc; +struct regulator_dev *regulator_dev; +unsigned int enable_counter; +}; + +#define domain_to_data (domain) container_of(domain, struct qca6390_data, pd) + +static int qca6390_enable (struct regulator_dev *rdev) +{ +struct qca6390_data *data =rdev_get_drvdata (rdev); +int ret; + + ret =regulator_bulk_enable (data->num_vregs, data->regulators); +if (ret) { +dev_err (data->dev,"Failed to enable regulators" ); +return ret; + } + +/* Wait for 1ms before toggling enable pins. */ +usleep_range (1000 ,2000 ); + + data->enable_counter++; + +return 0 ; +} + +static int qca6390_disable (struct regulator_dev *rdev) +{ +struct qca6390_data *data =rdev_get_drvdata (rdev); + +regulator_bulk_disable (data->num_vregs, data->regulators); + + data->enable_counter--; + +return 0 ; +} + +static int qca6390_is_enabled (struct regulator_dev *rdev) +{ +struct qca6390_data *data =rdev_get_drvdata (rdev); + +return data->enable_counter >0 ; +} + +static const struct regulator_ops qca6390_ops = { + .enable = qca6390_enable, + .disable = qca6390_disable, + .is_enabled = qca6390_is_enabled, +}; + +static int qca6390_probe (struct platform_device *pdev) +{ +struct qca6390_data *data; +struct device *dev = &pdev->dev; +struct regulator_config cfg = { }; +int i, ret; + + data =devm_kzalloc (dev,sizeof (*data),GFP_KERNEL ); +if (!data) +return -ENOMEM ; + + data->dev = dev; + data->num_vregs =ARRAY_SIZE (vregs); + +for (i =0 ; i < data->num_vregs; i++) + data->regulators[i].supply = vregs[i].name; + + ret =devm_regulator_bulk_get (dev, data->num_vregs, data->regulators); +if (ret <0 ) +return ret; + +for (i =0 ; i < data->num_vregs; i++) { + ret =regulator_set_load (data->regulators[i].consumer, vregs[i].load_uA); +if (ret) +return ret; + } + + data->desc.name =devm_kstrdup (dev,dev_name (dev),GFP_KERNEL ); +if (!data->desc.name) +return -ENOMEM ; + + data->desc.type =REGULATOR_VOLTAGE ; + data->desc.owner =THIS_MODULE ; + data->desc.ops = &qca6390_ops; + + cfg.dev = dev; + cfg.of_node = dev->of_node; + cfg.driver_data = data; + cfg.init_data =of_get_regulator_init_data (dev, dev->of_node, &data->desc); + + data->regulator_dev =devm_regulator_register (dev, &data->desc, &cfg); +if (IS_ERR (data->regulator_dev)) { + ret =PTR_ERR (data->regulator_dev); +return ret; + } + +platform_set_drvdata (pdev, data); + +return 0 ; +} + +static const struct of_device_id qca6390_of_match[] = { + { .compatible ="qcom,qca6390" }, +}; + +static struct platform_driver qca6390_driver = { + .probe = qca6390_probe, + .driver = { + .name ="qca6390" , + .of_match_table = qca6390_of_match, + }, +}; + +module_platform_driver (qca6390_driver); +MODULE_AUTHOR ("Dmitry Baryshkov <[email protected]>" ); +MODULE_DESCRIPTION ("Power control for Qualcomm QCA6390/1 BT/WiFi chip" ); +MODULE_LICENSE ("GPL v2" ); --2.30.2
Mark Brown
maintainerRe: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 10 lines · Ulf Hansson
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
- Peter (the email was bouncing)
Quoted 13 lines · Mark Brown
Quoted 10 lines · Ulf Hansson
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
Therefore, I think it would be worth having a common solution for this, rather than a solution per subsystem or even worse, per device.
Unfortunately, it looks like Peter's email is bouncing so we can't get an update from him.
Kind regards
Uffe
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Hi,
Quoted 2 lines · Ulf Hansson
- Peter (the email was bouncing)
+ Peter's kernel.org address
Quoted 22 lines · Mark Brown
Quoted 13 lines · Ulf Hansson
Quoted 10 lines
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Quoted 5 lines
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
In our case we'd definitely use pwrseq for PCIe bus and we can also benefit from using pwrseq for serdev and for platform busses also (for the same story of WiFi+BT chips).
I can take a look at rewriting pwrseq code to also handle the PCIe bus. Rewriting it to be a generic lib seems like an easy task, plugging it into PCIe code would be more fun.
Platform and serdev... Definitely even more fun.
Quoted 5 lines
Therefore, I think it would be worth having a common solution for this, rather than a solution per subsystem or even worse, per device.
Unfortunately, it looks like Peter's email is bouncing so we can't get an update from him.
Let's see if the kernel.org email will get to him.
Signature · 2 lines
With best wishes Dmitry
Rob Herring
maintainerRe: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 40 lines · Dmitry Baryshkov
Hi,
Quoted 2 lines · Ulf Hansson
- Peter (the email was bouncing)
+ Peter's kernel.org address
Quoted 22 lines · Mark Brown
Quoted 13 lines · Ulf Hansson
Quoted 10 lines
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Quoted 5 lines
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
In our case we'd definitely use pwrseq for PCIe bus and we can also benefit from using pwrseq for serdev and for platform busses also (for the same story of WiFi+BT chips).
Quoted 5 lines
I can take a look at rewriting pwrseq code to also handle the PCIe bus. Rewriting it to be a generic lib seems like an easy task, plugging it into PCIe code would be more fun.
Platform and serdev... Definitely even more fun.
I don't want to see pwrseq (the binding) expanded to other buses. If that was the answer, we wouldn't be having this discussion. It was a mistake for MMC IMO.
If pwrseq works as a kernel library/api, then I have no issue with that.
Quoted 3 lines
Quoted 3 lines
Therefore, I think it would be worth having a common solution for this, rather than a solution per subsystem or even worse, per device.
Power sequencing requirements are inheritently per device unless we're talking about standard connectors.
This is a solved problem on MDIO. It's quite simple. If there's a DT node for a device you haven't discovered, then probe it anyways.
Rob
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 45 lines · Rob Herring
Quoted 44 lines · Dmitry Baryshkov
Hi,
Quoted 2 lines · Ulf Hansson
- Peter (the email was bouncing)
+ Peter's kernel.org address
Quoted 22 lines · Mark Brown
Quoted 13 lines · Ulf Hansson
Quoted 10 lines
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Quoted 5 lines
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
In our case we'd definitely use pwrseq for PCIe bus and we can also benefit from using pwrseq for serdev and for platform busses also (for the same story of WiFi+BT chips).
I can take a look at rewriting pwrseq code to also handle the PCIe bus. Rewriting it to be a generic lib seems like an easy task, plugging it into PCIe code would be more fun.
Quoted 6 lines
Quoted 1 line
Platform and serdev... Definitely even more fun.
I don't want to see pwrseq (the binding) expanded to other buses. If that was the answer, we wouldn't be having this discussion. It was a mistake for MMC IMO.
But what do you want to see?
We have a single piece of hardware that needs a specific power sequence, which is interacted with using both UART and PCIe.
Quoted 9 lines
If pwrseq works as a kernel library/api, then I have no issue with that.
Quoted 3 lines
Quoted 3 lines
Therefore, I think it would be worth having a common solution for this, rather than a solution per subsystem or even worse, per device.
Power sequencing requirements are inheritently per device unless we're talking about standard connectors.
Do you mean "device" as in the IC or device as in struct device? Because we do have one physical IC, that has a need for a specific power on sequence, but we have two struct device, on two different busses in Linux interacting with this thing.
Quoted 3 lines
This is a solved problem on MDIO. It's quite simple. If there's a DT node for a device you haven't discovered, then probe it anyways.
Okay, so DT tells us that there's actually a WiFi thing on the PCIe bus, even though we can't find it, so we probe something...then what?
Regards,
Bjorn
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
In reply to Rob HerringQuoted 46 lines · Rob Herring
Quoted 44 lines · Dmitry Baryshkov
Hi,
Quoted 2 lines · Ulf Hansson
- Peter (the email was bouncing)
+ Peter's kernel.org address
Quoted 22 lines · Mark Brown
Quoted 13 lines · Ulf Hansson
Quoted 10 lines
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Quoted 5 lines
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
In our case we'd definitely use pwrseq for PCIe bus and we can also benefit from using pwrseq for serdev and for platform busses also (for the same story of WiFi+BT chips).
I can take a look at rewriting pwrseq code to also handle the PCIe bus. Rewriting it to be a generic lib seems like an easy task, plugging it into PCIe code would be more fun.
Quoted 5 lines
Quoted 1 line
Platform and serdev... Definitely even more fun.
I don't want to see pwrseq (the binding) expanded to other buses. If that was the answer, we wouldn't be having this discussion. It was a mistake for MMC IMO.
Let's make sure we get your point correctly. I think we have discussed this in the past, but let's refresh our memories.
If I recall correctly, you are against the mmc pwrseq DT bindings because we are using a separate pwrseq OF node, that we point to via a "mmc-pwrseq" property that contains a phandle from the mmc controller device node. Is that correct?
If we would have encoded the power sequence specific properties, from within a child node for the mmc controller node, that would have been okay for you, right?
Quoted 2 lines
If pwrseq works as a kernel library/api, then I have no issue with that.
That's what Peter Chen was trying to do. A generic interface, flexible enough so it can be used for many similar configurations (but not exactly the same).
Perhaps it was too generic though.
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Therefore, I think it would be worth having a common solution for this, rather than a solution per subsystem or even worse, per device.
Power sequencing requirements are inheritently per device unless we're talking about standard connectors.
The requirements are certainly per device, but the way to manage them doesn't have to be.
As you said above, a generic library that subsystems/drivers can call to power on/off a discoverable device, before trying to probe it would be a good start.
Quoted 3 lines
This is a solved problem on MDIO. It's quite simple. If there's a DT node for a device you haven't discovered, then probe it anyways.
A child OF node?
Then what do you think about some common power sequence properties that we can use in such node?
Quoted 2 lines
Rob
Kind regards
Uffe
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 56 lines · Ulf Hansson
Quoted 46 lines · Rob Herring
Quoted 44 lines · Dmitry Baryshkov
Hi,
Quoted 2 lines · Ulf Hansson
- Peter (the email was bouncing)
+ Peter's kernel.org address
Quoted 22 lines · Mark Brown
Quoted 13 lines · Ulf Hansson
Quoted 10 lines
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Quoted 5 lines
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
In our case we'd definitely use pwrseq for PCIe bus and we can also benefit from using pwrseq for serdev and for platform busses also (for the same story of WiFi+BT chips).
I can take a look at rewriting pwrseq code to also handle the PCIe bus. Rewriting it to be a generic lib seems like an easy task, plugging it into PCIe code would be more fun.
Quoted 5 lines
Quoted 1 line
Platform and serdev... Definitely even more fun.
I don't want to see pwrseq (the binding) expanded to other buses. If that was the answer, we wouldn't be having this discussion. It was a mistake for MMC IMO.
Let's make sure we get your point correctly. I think we have discussed this in the past, but let's refresh our memories.
Quoted 9 lines
If I recall correctly, you are against the mmc pwrseq DT bindings because we are using a separate pwrseq OF node, that we point to via a "mmc-pwrseq" property that contains a phandle from the mmc controller device node. Is that correct?
If we would have encoded the power sequence specific properties, from within a child node for the mmc controller node, that would have been okay for you, right?
In Dmitry's case, we have an external chip with that needs to be powered on per a specific sequence, at which point the WiFi driver on PCIe and BT driver on serdev will be able to communicate with the device.
The extended case of this is where we have an SDX55 modem soldered onto the pcb next to the SoC, in which case the power sequencing is even more complex and additionally there are incoming gpios used to detect things such as the firmware of the modem has crashed and Linux needs to toggle power and rescan the PCIe bus.
In both of these cases it seems quite reasonable to represent that external chip (and it's power needs) as a separate DT node. But we need a way to link the functional devices to that thing.
Regards,
Bjorn
Quoted 38 lines
Quoted 2 lines
If pwrseq works as a kernel library/api, then I have no issue with that.
That's what Peter Chen was trying to do. A generic interface, flexible enough so it can be used for many similar configurations (but not exactly the same).
Perhaps it was too generic though.
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Therefore, I think it would be worth having a common solution for this, rather than a solution per subsystem or even worse, per device.
Power sequencing requirements are inheritently per device unless we're talking about standard connectors.
The requirements are certainly per device, but the way to manage them doesn't have to be.
As you said above, a generic library that subsystems/drivers can call to power on/off a discoverable device, before trying to probe it would be a good start.
Quoted 3 lines
This is a solved problem on MDIO. It's quite simple. If there's a DT node for a device you haven't discovered, then probe it anyways.
A child OF node?
Then what do you think about some common power sequence properties that we can use in such node?
Quoted 2 lines
Rob
Kind regards
Uffe
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 64 lines · Bjorn Andersson
Quoted 61 lines · Ulf Hansson
Quoted 46 lines · Rob Herring
Quoted 44 lines · Dmitry Baryshkov
Hi,
Quoted 2 lines · Ulf Hansson
- Peter (the email was bouncing)
+ Peter's kernel.org address
Quoted 22 lines · Mark Brown
Quoted 13 lines · Ulf Hansson
Quoted 10 lines
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Quoted 5 lines
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
In our case we'd definitely use pwrseq for PCIe bus and we can also benefit from using pwrseq for serdev and for platform busses also (for the same story of WiFi+BT chips).
I can take a look at rewriting pwrseq code to also handle the PCIe bus. Rewriting it to be a generic lib seems like an easy task, plugging it into PCIe code would be more fun.
Quoted 5 lines
Quoted 1 line
Platform and serdev... Definitely even more fun.
I don't want to see pwrseq (the binding) expanded to other buses. If that was the answer, we wouldn't be having this discussion. It was a mistake for MMC IMO.
Let's make sure we get your point correctly. I think we have discussed this in the past, but let's refresh our memories.
If I recall correctly, you are against the mmc pwrseq DT bindings because we are using a separate pwrseq OF node, that we point to via a "mmc-pwrseq" property that contains a phandle from the mmc controller device node. Is that correct?
Quoted 8 lines
Quoted 4 lines
If we would have encoded the power sequence specific properties, from within a child node for the mmc controller node, that would have been okay for you, right?
In Dmitry's case, we have an external chip with that needs to be powered on per a specific sequence, at which point the WiFi driver on PCIe and BT driver on serdev will be able to communicate with the device.
Thanks for sharing more details.
So, not only do we have a discoverable device that needs to be powered on in a device specific way before probing, but in fact we have two consumers of that "combo chip", one (PCIe) for Wifi and one (serdev) for Bluetooth.
Quoted 6 lines
The extended case of this is where we have an SDX55 modem soldered onto the pcb next to the SoC, in which case the power sequencing is even more complex and additionally there are incoming gpios used to detect things such as the firmware of the modem has crashed and Linux needs to toggle power and rescan the PCIe bus.
That sounds very similar to what we manage for the SDIO bus already.
We have a mmc pwrseq node to describe what resources that are needed to power on/off the external chip. The driver for the functional device (Wifi chip for example) may then call SDIO APIs provided by the mmc core to power on/off the device, in case some kind of reset would be needed.
Additionally, we have a child node below the mmc controller node, allowing us to describe device specific things for the SDIO functional device, like an out-of-band IRQ line for example.
Overall, this seems to work fine, even if the DT bindings may be questionable.
Quoted 4 lines
In both of these cases it seems quite reasonable to represent that external chip (and it's power needs) as a separate DT node. But we need a way to link the functional devices to that thing.
Don't get me wrong, I am not suggesting we should re-use the mmc-pwrseq DT bindings - but just trying to share our experience around them.
In the cases you describe, it certainly sounds like we need some kind of minimal description in DT for these functional external devices. For GPIO pins, for example.
How to describe this in DT is one thing, let's see if Rob can help to point us in some direction of what could make sense.
When it comes to implementing a library/interface to manage these functional devices, I guess we just have to continue to explore various options. Perhaps just start simple with another subsystem, like PCIe and see where this brings us.
Quoted 4 lines
Regards,
Bjorn
[...]
Kind regards
Uffe
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
Quoted 116 lines · Ulf Hansson
Quoted 64 lines · Bjorn Andersson
Quoted 61 lines · Ulf Hansson
Quoted 46 lines · Rob Herring
Quoted 44 lines · Dmitry Baryshkov
Hi,
Quoted 2 lines · Ulf Hansson
- Peter (the email was bouncing)
+ Peter's kernel.org address
Quoted 22 lines · Mark Brown
Quoted 13 lines · Ulf Hansson
Quoted 10 lines
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Quoted 5 lines
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
In our case we'd definitely use pwrseq for PCIe bus and we can also benefit from using pwrseq for serdev and for platform busses also (for the same story of WiFi+BT chips).
I can take a look at rewriting pwrseq code to also handle the PCIe bus. Rewriting it to be a generic lib seems like an easy task, plugging it into PCIe code would be more fun.
Quoted 5 lines
Quoted 1 line
Platform and serdev... Definitely even more fun.
I don't want to see pwrseq (the binding) expanded to other buses. If that was the answer, we wouldn't be having this discussion. It was a mistake for MMC IMO.
Let's make sure we get your point correctly. I think we have discussed this in the past, but let's refresh our memories.
If I recall correctly, you are against the mmc pwrseq DT bindings because we are using a separate pwrseq OF node, that we point to via a "mmc-pwrseq" property that contains a phandle from the mmc controller device node. Is that correct?
Quoted 8 lines
Quoted 4 lines
If we would have encoded the power sequence specific properties, from within a child node for the mmc controller node, that would have been okay for you, right?
In Dmitry's case, we have an external chip with that needs to be powered on per a specific sequence, at which point the WiFi driver on PCIe and BT driver on serdev will be able to communicate with the device.
Thanks for sharing more details.
So, not only do we have a discoverable device that needs to be powered on in a device specific way before probing, but in fact we have two consumers of that "combo chip", one (PCIe) for Wifi and one (serdev) for Bluetooth.
Quoted 6 lines
The extended case of this is where we have an SDX55 modem soldered onto the pcb next to the SoC, in which case the power sequencing is even more complex and additionally there are incoming gpios used to detect things such as the firmware of the modem has crashed and Linux needs to toggle power and rescan the PCIe bus.
That sounds very similar to what we manage for the SDIO bus already.
We have a mmc pwrseq node to describe what resources that are needed to power on/off the external chip. The driver for the functional device (Wifi chip for example) may then call SDIO APIs provided by the mmc core to power on/off the device, in case some kind of reset would be needed.
Additionally, we have a child node below the mmc controller node, allowing us to describe device specific things for the SDIO functional device, like an out-of-band IRQ line for example.
Overall, this seems to work fine, even if the DT bindings may be questionable.
Quoted 4 lines
In both of these cases it seems quite reasonable to represent that external chip (and it's power needs) as a separate DT node. But we need a way to link the functional devices to that thing.
Don't get me wrong, I am not suggesting we should re-use the mmc-pwrseq DT bindings - but just trying to share our experience around them.
In the cases you describe, it certainly sounds like we need some kind of minimal description in DT for these functional external devices. For GPIO pins, for example.
Quoted 7 lines
How to describe this in DT is one thing, let's see if Rob can help to point us in some direction of what could make sense.
When it comes to implementing a library/interface to manage these functional devices, I guess we just have to continue to explore various options. Perhaps just start simple with another subsystem, like PCIe and see where this brings us.
Thank you for your opinion and suggestions. In fact I'm probably going to start working on non-discoverable busses first (by chaning support for few other BT+WiFi Qualcomm chips), later shifting the attention to the PCIe part. While this may seem like a longer path, I'd like to narrow pwrseq subsystem first, before going into PCIe details.
Signature · 2 lines
With best wishes Dmitry
Re: [PATCH v3 2/7] regulator: qca6390: add support for QCA639x powerup sequence
In reply to Ulf HanssonQuoted 23 lines · Ulf Hansson
- Peter (the email was bouncing)
Quoted 13 lines · Mark Brown
Quoted 10 lines · Ulf Hansson
On Tue, 22 Jun 2021 at 00:32, Dmitry Baryshkov
Quoted 4 lines
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part being controlled through the UART and WiFi being present on PCIe bus. Both blocks share common power sources. Add device driver handling power sequencing of QCA6390/1.
Power sequencing of discoverable buses have been discussed several times before at LKML. The last attempt [1] I am aware of, was in 2017 from Peter Chen. I don't think there is a common solution, yet.
Quoted 6 lines
This feels a bit different to the power sequencing problem - it's not exposing the individual inputs to the device but rather is a block that manages everything but needs a bit of a kick to get things going (I'd guess that with ACPI it'd be triggered via AML). It's in the same space but it's not quite the same issue I think, something that can handle control of the individual resources might still struggle with this.
Quoted 9 lines
Well, to me it looks very similar to those resouses we could manage with the mmc pwrseq, for SDIO. It's also typically the same kind of combo-chips that moved from supporting SDIO to PCIe, for improved performance I guess. More importantly, the same constraint to pre-power on the device is needed to allow it to be discovered/probed.
Therefore, I think it would be worth having a common solution for this, rather than a solution per subsystem or even worse, per device.
Representing the chip and its power needs, separate from the busses does seem reasonable. It's pretty much what Dmitry suggested originally, but his attempts to use either power-domain or regulator references to ensure ordering has been objected.
Beyond this, there is a similar case (that you and I have talked about earlier) in supporting the SDX55 PCIe modem found in some devices. Where in addition to ensuring that the power rails are configured, a couple of gpios needs to be controlled and there's an incoming gpio line indicating that the firmware of the device has locked up and the power needs to be toggled and the device re-enumerated.
Quoted 3 lines
Unfortunately, it looks like Peter's email is bouncing so we can't get an update from him.
And for this second part, where we need some additional logic it seems to go beyond what the power sequence discussions has touched upon so far.
Regards,
Bjorn
PATCH v3 3/7 Bluetooth: hci_qca: provide default device data
In reply to Dmitry BaryshkovIn order to simplify probe function provide default device data. This removes the rest of if (data) checks.
--- drivers/bluetooth/hci_qca.c | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-)
drivers/bluetooth/hci_qca.c +14 -10
@@ -1874,6 +1874,11 @@ static const struct qca_device_data qca_soc_data_wcn6750 = { .capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES, }; +static const struct qca_device_data qca_soc_data_default = { + .soc_type =QCA_ROME , + .num_vregs =0 , +}; +static void qca_power_shutdown (struct hci_uart *hu) {struct qca_serdev *qcadev;
@@ -2019,12 +2024,15 @@ static int qca_serdev_probe(struct serdev_device *serdev)int err;bool power_ctrl_enabled = true; + data =device_get_match_data (&serdev->dev); +if (!data) +return -EINVAL ; + qcadev =devm_kzalloc (&serdev->dev,sizeof (*qcadev),GFP_KERNEL );if (!qcadev)return -ENOMEM ; qcadev->serdev_hu.serdev = serdev; - data =device_get_match_data (&serdev->dev);serdev_device_set_drvdata (serdev, qcadev);device_property_read_string (&serdev->dev,"firmware-name" , &qcadev->firmware_name);
@@ -2033,9 +2041,8 @@ static int qca_serdev_probe(struct serdev_device *serdev)if (!qcadev->oper_speed)BT_DBG ("UART will pick default operating speed" ); -if (data && - (qca_is_wcn399x (data->soc_type) || -qca_is_wcn6750 (data->soc_type))) { +if ((qca_is_wcn399x (data->soc_type) || +qca_is_wcn6750 (data->soc_type))) { qcadev->btsoc_type = data->soc_type; qcadev->bt_power = devm_kzalloc(&serdev->dev, sizeof(struct qca_power),
@@ -2077,10 +2084,7 @@ static int qca_serdev_probe(struct serdev_device *serdev)return err; } }else { -if (data) - qcadev->btsoc_type = data->soc_type; -else - qcadev->btsoc_type =QCA_ROME ; + qcadev->btsoc_type = data->soc_type; qcadev->bt_en =devm_gpiod_get_optional (&serdev->dev,"enable" ,GPIOD_OUT_LOW );
@@ -2309,9 +2313,9 @@ static SIMPLE_DEV_PM_OPS(qca_pm_ops, qca_suspend, qca_resume);#ifdef CONFIG_OF static const struct of_device_id qca_bluetooth_of_match[] = { - { .compatible ="qcom,qca6174-bt" }, + { .compatible ="qcom,qca6174-bt" , .data = &qca_soc_data_default}, { .compatible ="qcom,qca6390-bt" , .data = &qca_soc_data_qca6390}, - { .compatible ="qcom,qca9377-bt" }, + { .compatible ="qcom,qca9377-bt" , .data = &qca_soc_data_default}, { .compatible ="qcom,wcn3990-bt" , .data = &qca_soc_data_wcn3990}, { .compatible ="qcom,wcn3991-bt" , .data = &qca_soc_data_wcn3991}, { .compatible = "qcom,wcn3998-bt", .data = &qca_soc_data_wcn3998},
Signature · 1 line
2.30.2
kernel test robot
build botRe: [PATCH v3 3/7] Bluetooth: hci_qca: provide default device data
Thank you for the patch! Perhaps something to improve:
Hi Dmitry,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on next-20210621]
[cannot apply to bluetooth/master regulator/for-next v5.13-rc7] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Dmitry-Baryshkov/Add-support-for-Qualcomm-QCA639x-chips-family/20210622-063340 base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master config: x86_64-randconfig-a002-20210622 (attached as .config) compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project b3634d3e88b7f26534a5057bff182b7dced584fc)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://github.com/0day-ci/linux/commit/7a46fc12b366a2ea83bf92e48892147159c202ed
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Dmitry-Baryshkov/Add-support-for-Qualcomm-QCA639x-chips-family/20210622-063340 git checkout 7a46fc12b366a2ea83bf92e48892147159c202ed
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
All warnings (new ones prefixed by >>):
drivers/bluetooth/hci_qca.c:1821:37: warning: unused variable 'qca_soc_data_wcn3990' [-Wunused-const-variable]
static const struct qca_device_data qca_soc_data_wcn3990 = {
^
drivers/bluetooth/hci_qca.c:1832:37: warning: unused variable 'qca_soc_data_wcn3991' [-Wunused-const-variable]
static const struct qca_device_data qca_soc_data_wcn3991 = {
^
drivers/bluetooth/hci_qca.c:1844:37: warning: unused variable 'qca_soc_data_wcn3998' [-Wunused-const-variable]
static const struct qca_device_data qca_soc_data_wcn3998 = {
^
drivers/bluetooth/hci_qca.c:1860:37: warning: unused variable 'qca_soc_data_wcn6750' [-Wunused-const-variable]
static const struct qca_device_data qca_soc_data_wcn6750 = {
^
>> drivers/bluetooth/hci_qca.c:1877:37: warning: unused variable 'qca_soc_data_default' [-Wunused-const-variable]
static const struct qca_device_data qca_soc_data_default = {
^5 warnings generated.
vim +/qca_soc_data_default +1877 drivers/bluetooth/hci_qca.c
1876
> 1877 static const struct qca_device_data qca_soc_data_default = { 1878 .soc_type = QCA_ROME,
1879 .num_vregs = 0,
1880 };
1881
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
Re: [PATCH v3 3/7] Bluetooth: hci_qca: provide default device data
In reply to Dmitry BaryshkovQuoted 3 lines · Dmitry Baryshkov
In order to simplify probe function provide default device data. This removes the rest of if (data) checks.
Regards,
Bjorn
Quoted 77 lines
Signed-off-by Dmitry Baryshkov <[email protected]>--- drivers/bluetooth/hci_qca.c | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-)drivers/bluetooth/hci_qca.c +14
-10@@ -1874,6 +1874,11 @@ static const struct qca_device_data qca_soc_data_wcn6750 = { .capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES, }; +static const struct qca_device_data qca_soc_data_default = { + .soc_type =QCA_ROME , + .num_vregs =0 , +}; +static void qca_power_shutdown (struct hci_uart *hu) {struct qca_serdev *qcadev;@@ -2019,12 +2024,15 @@ static int qca_serdev_probe(struct serdev_device *serdev)int err;bool power_ctrl_enabled = true; + data =device_get_match_data (&serdev->dev); +if (!data) +return -EINVAL ; + qcadev =devm_kzalloc (&serdev->dev,sizeof (*qcadev),GFP_KERNEL );if (!qcadev)return -ENOMEM ; qcadev->serdev_hu.serdev = serdev; - data =device_get_match_data (&serdev->dev);serdev_device_set_drvdata (serdev, qcadev);device_property_read_string (&serdev->dev,"firmware-name" , &qcadev->firmware_name);@@ -2033,9 +2041,8 @@ static int qca_serdev_probe(struct serdev_device *serdev)if (!qcadev->oper_speed)BT_DBG ("UART will pick default operating speed" ); -if (data && - (qca_is_wcn399x (data->soc_type) || -qca_is_wcn6750 (data->soc_type))) { +if ((qca_is_wcn399x (data->soc_type) || +qca_is_wcn6750 (data->soc_type))) { qcadev->btsoc_type = data->soc_type; qcadev->bt_power = devm_kzalloc(&serdev->dev, sizeof(struct qca_power),@@ -2077,10 +2084,7 @@ static int qca_serdev_probe(struct serdev_device *serdev)return err; } }else { -if (data) - qcadev->btsoc_type = data->soc_type; -else - qcadev->btsoc_type =QCA_ROME ; + qcadev->btsoc_type = data->soc_type; qcadev->bt_en =devm_gpiod_get_optional (&serdev->dev,"enable" ,GPIOD_OUT_LOW );@@ -2309,9 +2313,9 @@ static SIMPLE_DEV_PM_OPS(qca_pm_ops, qca_suspend, qca_resume);#ifdef CONFIG_OF static const struct of_device_id qca_bluetooth_of_match[] = { - { .compatible ="qcom,qca6174-bt" }, + { .compatible ="qcom,qca6174-bt" , .data = &qca_soc_data_default}, { .compatible ="qcom,qca6390-bt" , .data = &qca_soc_data_qca6390}, - { .compatible ="qcom,qca9377-bt" }, + { .compatible ="qcom,qca9377-bt" , .data = &qca_soc_data_default}, { .compatible ="qcom,wcn3990-bt" , .data = &qca_soc_data_wcn3990}, { .compatible ="qcom,wcn3991-bt" , .data = &qca_soc_data_wcn3991}, { .compatible = "qcom,wcn3998-bt", .data = &qca_soc_data_wcn3998},Signature · 1 line
2.30.2
PATCH v3 4/7 Bluetooth: hci_qca: merge qca_power into qca_serdev
In reply to Dmitry BaryshkovThere is no need to allocate separate structure for handling regulators used by QCA chips, we gain nothing from it. Move all used data fields directly to struct qca_serdev.
--- drivers/bluetooth/hci_qca.c | 58 ++++++++++++++----------------------- 1 file changed, 22 insertions(+), 36 deletions(-)
drivers/bluetooth/hci_qca.c +22 -36
@@ -208,20 +208,15 @@ struct qca_device_data {/* * Platform data for the QCA Bluetooth power driver. */ -struct qca_power { -struct device *dev; -struct regulator_bulk_data *vreg_bulk; -int num_vregs; -bool vregs_on; -}; -struct qca_serdev {struct hci_uart serdev_hu;struct gpio_desc *bt_en;struct gpio_desc *sw_ctrl;struct clk *susclk;enum qca_btsoc_type btsoc_type; -struct qca_power *bt_power; +struct regulator_bulk_data *vreg_bulk; +int num_vregs; +bool vregs_on;u32 init_speed;u32 oper_speed;const char *firmware_name;
@@ -1602,7 +1597,7 @@ static int qca_regulator_init(struct hci_uart *hu)* off the voltage regulator. */ qcadev =serdev_device_get_drvdata (hu->serdev); -if (!qcadev->bt_power->vregs_on) { +if (!qcadev->vregs_on) {serdev_device_close (hu->serdev); ret =qca_regulator_enable (qcadev);if (ret)
@@ -1945,20 +1940,19 @@ static int qca_power_off(struct hci_dev *hdev)static int qca_regulator_enable (struct qca_serdev *qcadev) { -struct qca_power *power = qcadev->bt_power;int ret;/* Already enabled */ -if (power->vregs_on) +if (qcadev->vregs_on)return 0 ; -BT_DBG ("enabling %d regulators)" , power->num_vregs); +BT_DBG ("enabling %d regulators)" , qcadev->num_vregs); - ret =regulator_bulk_enable (power->num_vregs, power->vreg_bulk); + ret =regulator_bulk_enable (qcadev->num_vregs, qcadev->vreg_bulk);if (ret)return ret; - power->vregs_on = true; + qcadev->vregs_on = true; ret =clk_prepare_enable (qcadev->susclk);if (ret)
@@ -1969,38 +1963,37 @@ static int qca_regulator_enable(struct qca_serdev *qcadev)static void qca_regulator_disable (struct qca_serdev *qcadev) { -struct qca_power *power; -if (!qcadev)return ; - power = qcadev->bt_power; -/* Already disabled? */ -if (!power->vregs_on) +if (!qcadev->vregs_on)return ; -regulator_bulk_disable (power->num_vregs, power->vreg_bulk); - power->vregs_on = false; +regulator_bulk_disable (qcadev->num_vregs, qcadev->vreg_bulk); + qcadev->vregs_on = false;clk_disable_unprepare (qcadev->susclk); } -static int qca_init_regulators (struct qca_power *qca, -const struct qca_vreg *vregs,size_t num_vregs) +static int qca_init_regulators (struct device *dev,struct qca_serdev *qca, +const struct qca_vreg *vregs,size_t num_vregs) {struct regulator_bulk_data *bulk;int ret;int i; - bulk =devm_kcalloc (qca->dev, num_vregs,sizeof (*bulk),GFP_KERNEL ); +if (!num_vregs) +return 0 ; + + bulk =devm_kcalloc (dev, num_vregs,sizeof (*bulk),GFP_KERNEL );if (!bulk)return -ENOMEM ;for (i =0 ; i < num_vregs; i++) bulk[i].supply = vregs[i].name; - ret =devm_regulator_bulk_get (qca->dev, num_vregs, bulk); + ret =devm_regulator_bulk_get (dev, num_vregs, bulk);if (ret <0 )return ret;
@@ -2044,21 +2037,15 @@ static int qca_serdev_probe(struct serdev_device *serdev)if ((qca_is_wcn399x (data->soc_type) ||qca_is_wcn6750 (data->soc_type))) { qcadev->btsoc_type = data->soc_type; - qcadev->bt_power =devm_kzalloc (&serdev->dev, -sizeof (struct qca_power ), -GFP_KERNEL ); -if (!qcadev->bt_power) -return -ENOMEM ; - - qcadev->bt_power->dev = &serdev->dev; - err =qca_init_regulators (qcadev->bt_power, data->vregs, + + err =qca_init_regulators (&serdev->dev, qcadev, data->vregs, data->num_vregs);if (err) {BT_ERR ("Failed to init regulators:%d" , err);return err; } - qcadev->bt_power->vregs_on = false; + qcadev->vregs_on = false; qcadev->bt_en =devm_gpiod_get_optional (&serdev->dev,"enable" ,GPIOD_OUT_LOW );
@@ -2139,11 +2126,10 @@ static int qca_serdev_probe(struct serdev_device *serdev)static void qca_serdev_remove (struct serdev_device *serdev) {struct qca_serdev *qcadev =serdev_device_get_drvdata (serdev); -struct qca_power *power = qcadev->bt_power;if ((qca_is_wcn399x (qcadev->btsoc_type) ||qca_is_wcn6750 (qcadev->btsoc_type)) && - power->vregs_on) + qcadev->vregs_on)qca_power_shutdown (&qcadev->serdev_hu);else if (qcadev->susclk)clk_disable_unprepare (qcadev->susclk);
Signature · 1 line
2.30.2
Re: [PATCH v3 4/7] Bluetooth: hci_qca: merge qca_power into qca_serdev
Quoted 4 lines · Dmitry Baryshkov
There is no need to allocate separate structure for handling regulators used by QCA chips, we gain nothing from it. Move all used data fields directly to struct
qca_serdev.
Regards,
Bjorn
Quoted 157 lines
Signed-off-by Dmitry Baryshkov <[email protected]>--- drivers/bluetooth/hci_qca.c | 58 ++++++++++++++----------------------- 1 file changed, 22 insertions(+), 36 deletions(-)drivers/bluetooth/hci_qca.c +22
-36@@ -208,20 +208,15 @@ struct qca_device_data {/* * Platform data for the QCA Bluetooth power driver. */ -struct qca_power { -struct device *dev; -struct regulator_bulk_data *vreg_bulk; -int num_vregs; -bool vregs_on; -}; -struct qca_serdev {struct hci_uart serdev_hu;struct gpio_desc *bt_en;struct gpio_desc *sw_ctrl;struct clk *susclk;enum qca_btsoc_type btsoc_type; -struct qca_power *bt_power; +struct regulator_bulk_data *vreg_bulk; +int num_vregs; +bool vregs_on;u32 init_speed;u32 oper_speed;const char *firmware_name;@@ -1602,7 +1597,7 @@ static int qca_regulator_init(struct hci_uart *hu)* off the voltage regulator. */ qcadev =serdev_device_get_drvdata (hu->serdev); -if (!qcadev->bt_power->vregs_on) { +if (!qcadev->vregs_on) {serdev_device_close (hu->serdev); ret =qca_regulator_enable (qcadev);if (ret)@@ -1945,20 +1940,19 @@ static int qca_power_off(struct hci_dev *hdev)static int qca_regulator_enable (struct qca_serdev *qcadev) { -struct qca_power *power = qcadev->bt_power;int ret;/* Already enabled */ -if (power->vregs_on) +if (qcadev->vregs_on)return 0 ; -BT_DBG ("enabling %d regulators)" , power->num_vregs); +BT_DBG ("enabling %d regulators)" , qcadev->num_vregs); - ret =regulator_bulk_enable (power->num_vregs, power->vreg_bulk); + ret =regulator_bulk_enable (qcadev->num_vregs, qcadev->vreg_bulk);if (ret)return ret; - power->vregs_on = true; + qcadev->vregs_on = true; ret =clk_prepare_enable (qcadev->susclk);if (ret)@@ -1969,38 +1963,37 @@ static int qca_regulator_enable(struct qca_serdev *qcadev)static void qca_regulator_disable (struct qca_serdev *qcadev) { -struct qca_power *power; -if (!qcadev)return ; - power = qcadev->bt_power; -/* Already disabled? */ -if (!power->vregs_on) +if (!qcadev->vregs_on)return ; -regulator_bulk_disable (power->num_vregs, power->vreg_bulk); - power->vregs_on = false; +regulator_bulk_disable (qcadev->num_vregs, qcadev->vreg_bulk); + qcadev->vregs_on = false;clk_disable_unprepare (qcadev->susclk); } -static int qca_init_regulators (struct qca_power *qca, -const struct qca_vreg *vregs,size_t num_vregs) +static int qca_init_regulators (struct device *dev,struct qca_serdev *qca, +const struct qca_vreg *vregs,size_t num_vregs) {struct regulator_bulk_data *bulk;int ret;int i; - bulk =devm_kcalloc (qca->dev, num_vregs,sizeof (*bulk),GFP_KERNEL ); +if (!num_vregs) +return 0 ; + + bulk =devm_kcalloc (dev, num_vregs,sizeof (*bulk),GFP_KERNEL );if (!bulk)return -ENOMEM ;for (i =0 ; i < num_vregs; i++) bulk[i].supply = vregs[i].name; - ret =devm_regulator_bulk_get (qca->dev, num_vregs, bulk); + ret =devm_regulator_bulk_get (dev, num_vregs, bulk);if (ret <0 )return ret;@@ -2044,21 +2037,15 @@ static int qca_serdev_probe(struct serdev_device *serdev)if ((qca_is_wcn399x (data->soc_type) ||qca_is_wcn6750 (data->soc_type))) { qcadev->btsoc_type = data->soc_type; - qcadev->bt_power =devm_kzalloc (&serdev->dev, -sizeof (struct qca_power ), -GFP_KERNEL ); -if (!qcadev->bt_power) -return -ENOMEM ; - - qcadev->bt_power->dev = &serdev->dev; - err =qca_init_regulators (qcadev->bt_power, data->vregs, + + err =qca_init_regulators (&serdev->dev, qcadev, data->vregs, data->num_vregs);if (err) {BT_ERR ("Failed to init regulators:%d" , err);return err; } - qcadev->bt_power->vregs_on = false; + qcadev->vregs_on = false; qcadev->bt_en =devm_gpiod_get_optional (&serdev->dev,"enable" ,GPIOD_OUT_LOW );@@ -2139,11 +2126,10 @@ static int qca_serdev_probe(struct serdev_device *serdev)static void qca_serdev_remove (struct serdev_device *serdev) {struct qca_serdev *qcadev =serdev_device_get_drvdata (serdev); -struct qca_power *power = qcadev->bt_power;if ((qca_is_wcn399x (qcadev->btsoc_type) ||qca_is_wcn6750 (qcadev->btsoc_type)) && - power->vregs_on) + qcadev->vregs_on)qca_power_shutdown (&qcadev->serdev_hu);else if (qcadev->susclk)clk_disable_unprepare (qcadev->susclk);Signature · 1 line
2.30.2
PATCH v3 5/7 Bluetooth: hci_qca: merge wcn & non-wcn code paths
In reply to Dmitry BaryshkovIn preparation to add power sequencer support to qca6390, merge wcnxxxx and non-wcn codepaths.
--- drivers/bluetooth/hci_qca.c | 152 +++++++++++++++++------------------- 1 file changed, 71 insertions(+), 81 deletions(-)
drivers/bluetooth/hci_qca.c +71 -81
@@ -84,6 +84,7 @@ enum qca_flags {enum qca_capabilities {QCA_CAP_WIDEBAND_SPEECH =BIT (0 ),QCA_CAP_VALID_LE_STATES =BIT (1 ), +QCA_CAP_NEEDS_BT_ENABLE =BIT (2 ), };/* HCI_IBS transmit side sleep protocol states */
@@ -203,6 +204,7 @@ struct qca_device_data {struct qca_vreg *vregs;size_t num_vregs;uint32_t capabilities; +const char *name; };/*
@@ -220,6 +222,7 @@ struct qca_serdev {u32 init_speed;u32 oper_speed;const char *firmware_name; +const char *name; };static int qca_regulator_enable (struct qca_serdev *qcadev);
@@ -254,6 +257,17 @@ static const char *qca_get_firmware_name(struct hci_uart *hu) } } +static const char *qca_soc_name (struct hci_uart *hu) +{ +if (hu->serdev) { +struct qca_serdev *qsd =serdev_device_get_drvdata (hu->serdev); + +return qsd->name; + }else { +return "ROME" ; + } +} +static void __serial_clock_on (struct tty_struct *tty) {/* TODO: Some chipset requires to enable UART clock on client
@@ -1623,14 +1637,16 @@ static int qca_regulator_init(struct hci_uart *hu)gpiod_set_value_cansleep (qcadev->bt_en,0 );msleep (50 );gpiod_set_value_cansleep (qcadev->bt_en,1 ); -msleep (50 ); +msleep (150 );if (qcadev->sw_ctrl) { sw_ctrl_state =gpiod_get_value_cansleep (qcadev->sw_ctrl);bt_dev_dbg (hu->hdev,"SW_CTRL is %d" , sw_ctrl_state); } } -qca_set_speed (hu,QCA_INIT_SPEED ); +if (qca_is_wcn399x (soc_type) || +qca_is_wcn6750 (soc_type)) +qca_set_speed (hu,QCA_INIT_SPEED );if (qca_is_wcn399x (soc_type)) { ret =qca_send_power_pulse (hu, true);
@@ -1650,7 +1666,9 @@ static int qca_regulator_init(struct hci_uart *hu)return ret; } -hci_uart_set_flow_control (hu, false); +if (qca_is_wcn399x (soc_type) || +qca_is_wcn6750 (soc_type)) +hci_uart_set_flow_control (hu, false);return 0 ; }
@@ -1658,8 +1676,6 @@ static int qca_regulator_init(struct hci_uart *hu)static int qca_power_on (struct hci_dev *hdev) {struct hci_uart *hu =hci_get_drvdata (hdev); -enum qca_btsoc_type soc_type =qca_soc_type (hu); -struct qca_serdev *qcadev;struct qca_data *qca = hu->priv;int ret =0 ;
@@ -1669,17 +1685,7 @@ static int qca_power_on(struct hci_dev *hdev)if (!hu->serdev)return 0 ; -if (qca_is_wcn399x (soc_type) || -qca_is_wcn6750 (soc_type)) { - ret =qca_regulator_init (hu); - }else { - qcadev =serdev_device_get_drvdata (hu->serdev); -if (qcadev->bt_en) { -gpiod_set_value_cansleep (qcadev->bt_en,1 ); -/* Controller needs time to bootup. */ -msleep (150 ); - } - } + ret =qca_regulator_init (hu);clear_bit (QCA_BT_OFF , &qca->flags);return ret;
@@ -1709,9 +1715,7 @@ static int qca_setup(struct hci_uart *hu)*/ set_bit (HCI_QUIRK_SIMULTANEOUS_DISCOVERY , &hdev->quirks); -bt_dev_info (hdev,"setting up %s" , -qca_is_wcn399x (soc_type) ?"wcn399x" : - (soc_type ==QCA_WCN6750 ) ?"wcn6750" :"ROME/QCA6390" ); +bt_dev_info (hdev,"setting up %s" ,qca_soc_name (hu)); qca->memdump_state =QCA_MEMDUMP_IDLE ;
@@ -1822,6 +1826,7 @@ static const struct qca_device_data qca_soc_data_wcn3990 = { { "vddch0", 450000 }, }, .num_vregs = 4, + .name = "wcn3990", }; static const struct qca_device_data qca_soc_data_wcn3991 = {
@@ -1834,6 +1839,7 @@ static const struct qca_device_data qca_soc_data_wcn3991 = { }, .num_vregs = 4, .capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES, + .name = "wcn3991", };static const struct qca_device_data qca_soc_data_wcn3998 = {
@@ -1845,11 +1851,14 @@ static const struct qca_device_data qca_soc_data_wcn3998 = { { "vddch0", 450000 }, }, .num_vregs = 4, + .name = "wcn3998", };static const struct qca_device_data qca_soc_data_qca6390 = { .soc_type =QCA_QCA6390 , .num_vregs =0 , + .capabilities =QCA_CAP_NEEDS_BT_ENABLE , + .name ="qca6390" , }; static const struct qca_device_data qca_soc_data_wcn6750 = {
@@ -1866,12 +1875,15 @@ static const struct qca_device_data qca_soc_data_wcn6750 = { { "vddasd", 200 }, }, .num_vregs = 9, - .capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES, + .capabilities = QCA_CAP_WIDEBAND_SPEECH | QCA_CAP_VALID_LE_STATES | QCA_CAP_NEEDS_BT_ENABLE, + .name = "wcn6750", };static const struct qca_device_data qca_soc_data_default = { .soc_type =QCA_ROME , .num_vregs =0 , + .capabilities =QCA_CAP_NEEDS_BT_ENABLE , + .name ="ROME" , };static void qca_power_shutdown (struct hci_uart *hu)
@@ -1903,7 +1915,7 @@ static void qca_power_shutdown(struct hci_uart *hu)host_set_baudrate (hu,2400 );qca_send_power_pulse (hu, false);qca_regulator_disable (qcadev); - }else if (soc_type ==QCA_WCN6750 ) { + }else if (qcadev->bt_en) {gpiod_set_value_cansleep (qcadev->bt_en,0 );msleep (100 );qca_regulator_disable (qcadev);
@@ -1911,8 +1923,6 @@ static void qca_power_shutdown(struct hci_uart *hu) sw_ctrl_state =gpiod_get_value_cansleep (qcadev->sw_ctrl);bt_dev_dbg (hu->hdev,"SW_CTRL is %d" , sw_ctrl_state); } - }else if (qcadev->bt_en) { -gpiod_set_value_cansleep (qcadev->bt_en,0 ); }set_bit (QCA_BT_OFF , &qca->flags);
@@ -2034,71 +2044,51 @@ static int qca_serdev_probe(struct serdev_device *serdev)if (!qcadev->oper_speed)BT_DBG ("UART will pick default operating speed" ); -if ((qca_is_wcn399x (data->soc_type) || -qca_is_wcn6750 (data->soc_type))) { - qcadev->btsoc_type = data->soc_type; - - err =qca_init_regulators (&serdev->dev, qcadev, data->vregs, - data->num_vregs); -if (err) { -BT_ERR ("Failed to init regulators:%d" , err); -return err; - } + qcadev->name = data->name; + qcadev->btsoc_type = data->soc_type; - qcadev->vregs_on = false; - - qcadev->bt_en =devm_gpiod_get_optional (&serdev->dev,"enable" , -GPIOD_OUT_LOW ); -if (!qcadev->bt_en && data->soc_type ==QCA_WCN6750 ) { -dev_err (&serdev->dev,"failed to acquire BT_EN gpio\n" ); - power_ctrl_enabled = false; - } + err =qca_init_regulators (&serdev->dev, qcadev, data->vregs, + data->num_vregs); +if (err) { +BT_ERR ("Failed to init regulators:%d" , err); +return err; + } - qcadev->sw_ctrl =devm_gpiod_get_optional (&serdev->dev,"swctrl" , -GPIOD_IN ); -if (!qcadev->sw_ctrl && data->soc_type ==QCA_WCN6750 ) -dev_warn (&serdev->dev,"failed to acquire SW_CTRL gpio\n" ); + qcadev->vregs_on = false; - qcadev->susclk =devm_clk_get_optional (&serdev->dev,NULL ); -if (IS_ERR (qcadev->susclk)) { -dev_err (&serdev->dev,"failed to acquire clk\n" ); -return PTR_ERR (qcadev->susclk); - } + qcadev->bt_en =devm_gpiod_get_optional (&serdev->dev,"enable" , +GPIOD_OUT_LOW ); +if (!qcadev->bt_en && (data->capabilities &QCA_CAP_NEEDS_BT_ENABLE )) { +dev_err (&serdev->dev,"failed to acquire BT_EN gpio\n" ); + power_ctrl_enabled = false; + } - err =hci_uart_register_device (&qcadev->serdev_hu, &qca_proto); -if (err) { -BT_ERR ("wcn3990 serdev registration failed" ); -return err; - } - }else { - qcadev->btsoc_type = data->soc_type; + qcadev->sw_ctrl =devm_gpiod_get_optional (&serdev->dev,"swctrl" , +GPIOD_IN ); +if (!qcadev->sw_ctrl && data->soc_type ==QCA_WCN6750 ) +dev_warn (&serdev->dev,"failed to acquire SW_CTRL gpio\n" ); - qcadev->bt_en =devm_gpiod_get_optional (&serdev->dev,"enable" , -GPIOD_OUT_LOW ); -if (!qcadev->bt_en) { -dev_warn (&serdev->dev,"failed to acquire enable gpio\n" ); - power_ctrl_enabled = false; - } + qcadev->susclk =devm_clk_get_optional (&serdev->dev,NULL ); +if (IS_ERR (qcadev->susclk)) { +dev_err (&serdev->dev,"failed to acquire clk\n" ); +return PTR_ERR (qcadev->susclk); + } - qcadev->susclk =devm_clk_get_optional (&serdev->dev,NULL ); -if (IS_ERR (qcadev->susclk)) { -dev_warn (&serdev->dev,"failed to acquire clk\n" ); -return PTR_ERR (qcadev->susclk); - } - err =clk_set_rate (qcadev->susclk,SUSCLK_RATE_32KHZ ); -if (err) -return err; + err =clk_set_rate (qcadev->susclk,SUSCLK_RATE_32KHZ ); +if (err) +return err; +if (!qca_is_wcn399x (qcadev->btsoc_type) && + !qca_is_wcn6750 (qcadev->btsoc_type)) { err =clk_prepare_enable (qcadev->susclk);if (err)return err; + } - err =hci_uart_register_device (&qcadev->serdev_hu, &qca_proto); -if (err) { -BT_ERR ("Rome serdev registration failed" ); -clk_disable_unprepare (qcadev->susclk); -return err; - } + err =hci_uart_register_device (&qcadev->serdev_hu, &qca_proto); +if (err) { +BT_ERR ("%s serdev registration failed" , qcadev->name); +return err; } hdev = qcadev->serdev_hu.hdev;
@@ -2127,11 +2117,11 @@ static void qca_serdev_remove(struct serdev_device *serdev) {struct qca_serdev *qcadev =serdev_device_get_drvdata (serdev); -if ((qca_is_wcn399x (qcadev->btsoc_type) || -qca_is_wcn6750 (qcadev->btsoc_type)) && - qcadev->vregs_on) +if (qcadev->vregs_on)qca_power_shutdown (&qcadev->serdev_hu); -else if (qcadev->susclk) + +if (!qca_is_wcn399x (qcadev->btsoc_type) && + !qca_is_wcn6750 (qcadev->btsoc_type))clk_disable_unprepare (qcadev->susclk);hci_uart_unregister_device (&qcadev->serdev_hu);
Signature · 1 line
2.30.2
PATCH v3 6/7 Bluetooth: hci_qca: add power sequencer support to qca6390
In reply to Dmitry BaryshkovQCA6390 uses on-chip power sequencer (and power management unit) to supply power to both WiFi and BT parts. Since this sequencer is supported by a separate driver, use it as a single "vin" regulator.
--- drivers/bluetooth/hci_qca.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/bluetooth/hci_qca.c +4 -1
@@ -1856,7 +1856,10 @@ static const struct qca_device_data qca_soc_data_wcn3998 = {static const struct qca_device_data qca_soc_data_qca6390 = { .soc_type =QCA_QCA6390 , - .num_vregs =0 , + .vregs = (struct qca_vreg []) { + {"vin" ,1000 }, + }, + .num_vregs =1 , .capabilities =QCA_CAP_NEEDS_BT_ENABLE , .name ="qca6390" , };
Signature · 1 line
2.30.2
PATCH v3 7/7 arm64: dts: qcom: qrb5165-rb5: add QCA6391 WiFi+BT SoC
In reply to Dmitry BaryshkovDescribe the onboard WiFi+BT SoC QCA6391. It is connected to uart6 to provide Bluetooth functionality (QCA) and to PCIe to provide WiFi (ath11k). A separate power sequencer device node is used to describe on-SoC power management unit common to both WiFi and BT parts.
--- arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 56 ++++++++++++++++++++++++ 1 file changed, 56 insertions(+)
arch/arm64/boot/dts/qcom/qrb5165-rb5.dts +56 -0
@@ -20,6 +20,7 @@ / { aliases { serial0 = &uart12; + serial1 = &uart6; sdhc2 = &sdhc_2; };
@@ -223,6 +224,28 @@ vreg_s4a_1p8: vreg-s4a-1p8 { regulator-max-microvolt = <1800000>; regulator-always-on; }; + + qca6391: qca6391 { + compatible = "qcom,qca6390"; + + vddaon-supply = <&vreg_s6a_0p95>; + vddpmu-supply = <&vreg_s2f_0p95>; + vddrfa1-supply = <&vreg_s2f_0p95>; + vddrfa2-supply = <&vreg_s8c_1p3>; + vddrfa3-supply = <&vreg_s5a_1p9>; + vddpcie1-supply = <&vreg_s8c_1p3>; + vddpcie2-supply = <&vreg_s5a_1p9>; + vddio-supply = <&vreg_s4a_1p8>; + }; + + vreg_wlan: vreg-wlan { + compatible = "regulator-fixed"; + regulator-name = "vreg-wlan"; + + vin-supply = <&qca6391>; + gpio = <&tlmm 20 GPIO_ACTIVE_LOW>; + enable-active-high; + }; }; &adsp {
@@ -668,6 +691,8 @@ &pcie0 { wake-gpio = <&tlmm 81 GPIO_ACTIVE_HIGH>; pinctrl-names = "default"; pinctrl-0 = <&pcie0_default_state>; + + vddpe-3v3-supply = <&vreg_wlan>; }; &pcie0_phy {
@@ -811,6 +836,26 @@ lt9611_rst_pin: lt9611-rst-pin { }; }; +&qup_uart6_default { + ctsrx { + pins = "gpio16", "gpio19"; + drive-strength = <2>; + bias-disable; + }; + + rts { + pins = "gpio17"; + drive-strength = <2>; + bias-disable; + }; + + tx { + pins = "gpio18"; + drive-strength = <2>; + bias-pull-up; + }; +}; + &qupv3_id_0 { status = "okay"; };
@@ -1275,6 +1320,17 @@ sdc2_card_det_n: sd-card-det-n { }; }; +&uart6 { + status = "okay"; + bluetooth { + compatible = "qcom,qca6390-bt"; + vin-supply = <&qca6391>; + clocks = <&sleep_clk>; + + enable-gpios = <&tlmm 21 GPIO_ACTIVE_HIGH>; + }; +}; + &uart12 { status = "okay"; };
Signature · 1 line
2.30.2