Skip to content

packagegroup-iq-9075-evk: include qca-qca61x4-usb#1279

Merged
vkraleti merged 1 commit intoqualcomm-linux:masterfrom
WeiDeng-weiden:package
Jan 2, 2026
Merged

packagegroup-iq-9075-evk: include qca-qca61x4-usb#1279
vkraleti merged 1 commit intoqualcomm-linux:masterfrom
WeiDeng-weiden:package

Conversation

@WeiDeng-weiden
Copy link
Copy Markdown

This firmware is required for setting up BT with HSP USB interface on the iq-9075-evk platform. Therefore add linux-firmware-qca-qca61x4-usb.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Dec 3, 2025

Is the USB Bluetooth present on board or is it attached separately?

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Dec 3, 2025

Test run workflow

Test jobs for commit eb81f2a39b4d7f6ccafbec185e1c00b1509e8b2e

@test-reporting-app
Copy link
Copy Markdown

test-reporting-app Bot commented Dec 3, 2025

Test Results

 12 files  ±0   24 suites  ±0   29m 49s ⏱️ -43s
 45 tests ±0   45 ✅ ±0  0 💤 ±0  0 ❌ ±0 
264 runs  ±0  264 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 91f6fb7. ± Comparison against base commit 9fa944d.

♻️ This comment has been updated with latest results.

@WeiDeng-weiden
Copy link
Copy Markdown
Author

Is the USB Bluetooth present on board or is it attached separately?

We attached connectivity chip separately through M.2 interface. UART and USB HSP are two different chips and require different firmware.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Dec 4, 2025

Is the USB Bluetooth present on board or is it attached separately?

We attached connectivity chip separately through M.2 interface. UART and USB HSP are two different chips and require different firmware.

You have attached it, it's fine. Why are you implying those changes on everybody? Please extend your local build config instead of adding irrelevant firmware to the machine configuration. Closing now.

@lumag lumag closed this Dec 4, 2025
@ricardosalveti
Copy link
Copy Markdown
Contributor

Unless attached by default (as part of the EVK hardware package), it should really be a distro level decision.

@WeiDeng-weiden
Copy link
Copy Markdown
Author

Is the USB Bluetooth present on board or is it attached separately?

We attached connectivity chip separately through M.2 interface. UART and USB HSP are two different chips and require different firmware.

You have attached it, it's fine. Why are you implying those changes on everybody? Please extend your local build config instead of adding irrelevant firmware to the machine configuration. Closing now.

Hello Maintainer, thanks for your comments.
The iq-9075-evk platform does not have an onboard card. As per PDM requirements, it is designed to support multiple connectivity chipsets (WCN685x/WCN7850) attached via the M.2 interface, including:

WCN685x USB interface
WCN685x UART interface
WCN7850 USB interface
WCN7850 UART interface

In the current .bb file, linux-firmware-qca-qca2066 provides the firmware required for WCN685x UART. However, additional firmware is needed for other interfaces. For example, my change adds linux-firmware-qca-qca61x4-usb, which is required for WCN685x USB. Therefore, I believe we should also include the firmware required for the other attached interface chips.

@lumag lumag reopened this Dec 10, 2025
@lumag
Copy link
Copy Markdown
Contributor

lumag commented Dec 10, 2025

Hello Maintainer, thanks for your comments. The iq-9075-evk platform does not have an onboard card. As per PDM requirements, it is designed to support multiple connectivity chipsets (WCN685x/WCN7850) attached via the M.2 interface, including:

WCN685x USB interface WCN685x UART interface WCN7850 USB interface WCN7850 UART interface

In the current .bb file, linux-firmware-qca-qca2066 provides the firmware required for WCN685x UART. However, additional firmware is needed for other interfaces. For example, my change adds linux-firmware-qca-qca61x4-usb, which is required for WCN685x USB. Therefore, I believe we should also include the firmware required for the other attached interface chips.

This needs to be explained in the commit message. Also please add WiFi and BT firmware for all these options.

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit eb81f2a39b4d7f6ccafbec185e1c00b1509e8b2e

@WeiDeng-weiden
Copy link
Copy Markdown
Author

Hello Maintainer, thanks for your comments. The iq-9075-evk platform does not have an onboard card. As per PDM requirements, it is designed to support multiple connectivity chipsets (WCN685x/WCN7850) attached via the M.2 interface, including:
WCN685x USB interface WCN685x UART interface WCN7850 USB interface WCN7850 UART interface
In the current .bb file, linux-firmware-qca-qca2066 provides the firmware required for WCN685x UART. However, additional firmware is needed for other interfaces. For example, my change adds linux-firmware-qca-qca61x4-usb, which is required for WCN685x USB. Therefore, I believe we should also include the firmware required for the other attached interface chips.

This needs to be explained in the commit message. Also please add WiFi and BT firmware for all these options.

Thanks, will update commit message and re-submit.

Copy link
Copy Markdown
Contributor

@lumag lumag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please wrap commit message on a reasonable boundary (usually 72-75 chars).

Other than that:

s/wlan/WiFi/
s/bt/BT/
s/uart/UART/

"other interfaces" - what does that mean? Which interfaces? Other than M.2?

"This change include" - rewrite to use imperative language.

"- linux-firmware-ath12k-wcn7850 for including wcn7850 wlan fw." - package contents is obvious. Describe why we need the package. I'd rather describe per card (name, SKU, whatever) which firmware packages it needs.

@WeiDeng-weiden
Copy link
Copy Markdown
Author

Please wrap commit message on a reasonable boundary (usually 72-75 chars).

Other than that:

s/wlan/WiFi/ s/bt/BT/ s/uart/UART/

"other interfaces" - what does that mean? Which interfaces? Other than M.2?

"This change include" - rewrite to use imperative language.

"- linux-firmware-ath12k-wcn7850 for including wcn7850 wlan fw." - package contents is obvious. Describe why we need the package. I'd rather describe per card (name, SKU, whatever) which firmware packages it needs.

Thanks for your suggestion. Will correct commit message.

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 0afcfa53ff84b6a62fda7d1cfb4f410fe7d3de53

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 88966bf30fdb5940f66210aa7c27ea720b080c8e

Copy link
Copy Markdown
Contributor

@lumag lumag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- linux-firmware-ath12k-wcn7850:
  WiFi firmware for WCN7850.

Other way around: a card name => firmware packages that are necessary for it.

@WeiDeng-weiden
Copy link
Copy Markdown
Author

- linux-firmware-ath12k-wcn7850:
  WiFi firmware for WCN7850.

Other way around: a card name => firmware packages that are necessary for it.

Okay, I will make updates according to your suggestion.

The IQ-9075-EVK platform does not have an on-board connectivity card.
Per PDM requirements it is designed to support WCN685x and WCN7850
connectivity modules over the M.2 interface and therefore needs the
corresponding WiFi and BT firmware.

Add the required firmware packages for the supported modules:

WCN685x connectivity module requires:
  - linux-firmware-qca-wcn685x (BT UART firmware)
  - linux-firmware-qca-qca61x4-usb (BT USB firmware)

WCN7850 connectivity module requires:
  - linux-firmware-ath12k-wcn7850 (WiFi firmware)
  - linux-firmware-qca-wcn7850 (BT UART firmware)
  - linux-firmware-qca-qca61x4-usb (BT USB firmware)

Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com>
@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 91f6fb7

@vkraleti vkraleti merged commit ce7b8ed into qualcomm-linux:master Jan 2, 2026
107 of 108 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants