[Matter 1.3][TCR] Add Wi-Fi network driver support to get supported bands for Linux platform #30109
Assignees
Labels
Milestone
Comments
tcarmelveilleux
added
commissioning
github-project-automation
bot
moved this to Open Cert Blockers
in [Certification] Blockers
tcarmelveilleux
added a commit
to tcarmelveilleux/connectedhomeip
that referenced
this issue
Jan 24, 2024
- Linux has noo easy/portable API to determine 5GHz Wi-Fisupport that could be used in Linux platform examples without large changes. - To be able to test SupportedWiFiBands attribute, we have to allow reporting the support for 5GHz Wi-Fi when available. - A workaround was found by adding `--wifi-supports-5g` command line argument to examples, and the requisite plumbing in Linux Wi-Fi driver. Fixes project-chip#30109 Testing done: - Automated test of TC-CNET-* that use this support the new argument will come in a follow-up. - Manually testing between invocations with the following: ``` Terminal1: rm -f kvs1 && out/debug/standalone/chip-all-clusters-app --KVS kvs1 --wifi --wifi-supports-5g Terminal2: ./out/debug/standalone/chip-tool pairing onnetwork 1 20202021 Terminal2: ./out/debug/standalone/chip-tool networkcommissioning read supported-wi-fi-bands 1 0 Verify read has 2 entries: [0, 2] Terminal1: killall chip-all-clusters-app Terminal1: out/debug/standalone/chip-all-clusters-app --KVS kvs1 --wifi Terminal2: ./out/debug/standalone/chip-tool networkcommissioning read supported-wi-fi-bands 1 0 Verify read has 1 entry: [0] ```
mergify bot
pushed a commit
that referenced
this issue
Jan 25, 2024
* Add support to Linux examples to report 5GHz Wi-Fi support - Linux has noo easy/portable API to determine 5GHz Wi-Fisupport that could be used in Linux platform examples without large changes. - To be able to test SupportedWiFiBands attribute, we have to allow reporting the support for 5GHz Wi-Fi when available. - A workaround was found by adding `--wifi-supports-5g` command line argument to examples, and the requisite plumbing in Linux Wi-Fi driver. Fixes #30109 Testing done: - Automated test of TC-CNET-* that use this support the new argument will come in a follow-up. - Manually testing between invocations with the following: ``` Terminal1: rm -f kvs1 && out/debug/standalone/chip-all-clusters-app --KVS kvs1 --wifi --wifi-supports-5g Terminal2: ./out/debug/standalone/chip-tool pairing onnetwork 1 20202021 Terminal2: ./out/debug/standalone/chip-tool networkcommissioning read supported-wi-fi-bands 1 0 Verify read has 2 entries: [0, 2] Terminal1: killall chip-all-clusters-app Terminal1: out/debug/standalone/chip-all-clusters-app --KVS kvs1 --wifi Terminal2: ./out/debug/standalone/chip-tool networkcommissioning read supported-wi-fi-bands 1 0 Verify read has 1 entry: [0] ``` * Restyled by clang-format * Improve comments --------- Co-authored-by: Restyled.io <[email protected]>
github-project-automation
bot
moved this from Open Cert Blockers
to Complete
in [Certification] Blockers
github-project-automation
bot
moved this from Todo
to Done
in [1.3] SDK Feature Complete
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To support the new
SupportedWiFiBandsenum in Network Commissioning cluster (see Matter 1.3 TCR https://github.com/CHIP-Specifications/connectedhomeip-spec/pull/7571), support for the band listing must be added to the Linux Wi-Fi commissioning driver.The text was updated successfully, but these errors were encountered: