ath10k-firmware: QCA9888 hw2.0: Add TP-Link Archer C6 v2 (US) / A6 v2 (US/TW) specific BDFs

[Jeff Johnson]

On 9/19/2024 1:33 PM, Adam Elyas Aliasaa wrote:
> Hello,
> 
> I wish to submit a specific BDF for this device.
> 
> The device have two names: TP-Link Archer C6 v2 (US), and TP-Link Archer A6 v2 (US/TW). They are identical, and has been supported by OpenWRT since 2019. Unfortunately, the 5GHz radio suffers from low RSSI. It seems that the radio components were changed substantially that the stock values in board-2.bin doesn't work well with it. Replacing the default board file with the one included in stock firmware fixes the 5GHz range.
> 
>> description for what hardware this is
> 
> It is a QCA9563 based board, consisting of one QCA9563 radio used for 2.4GHz WLAN, and one QCA9886 radio used for 5GHz WLAN.
> 
>> origin of the board file (did you create it yourself or where you downloaded)
> 
> I pulled it off the latest stock firmware image, from '/lib/firmware/QCA9888/hw.2/boardData_2_0_QCA9888_5G_YA105_us.bin'.
> 
>> ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
> 
> I'd suggest:
> bus=pci,bmi-chip-id=0,bmi-board-id=24,variant=tp-link-archer-c6-v2-us
> 
> Which is based off the console log after I intentionally replaced the board-2.bin with an invalid one:
> [   14.965856] ath10k_pci 0000:00:00.0: failed to fetch board data for bus=pci,bmi-chip-id=0,bmi-board-id=24 from ath10k/QCA9888/hw2.0/board-2.bin
> 
>> attach the actual board file (board.bin)
> 
> As attached. I left the original file name as is.
> 
> File name: boardData_2_0_QCA9888_5G_YA105_us.bin
> sha256 sum: 10ef67f14bab5d565ce777f7c852124acbfe4cd7e04a06d548f110201553dd25
> 
> Thank you.
> 
> Kind regards,
> Adam E.

I'm clearing the backlog. If you still want this to be processed, please
resubmit following the instructions to "attach the actual board file
(board.bin) with the exact name to be used in board-2.bin":
bus=pci,bmi-chip-id=0,bmi-board-id=24,variant=tp-link-archer-c6-v2-us.bin

That way the automation I inherited can correctly process the request.

However also see:
https://msgid.link/793a1944-b287-496e-9687-daf6ea8a6bb8@oss.qualcomm.com

It would be good for the two of you to work together to make sure you have
consistent naming across the variant IDs, starting with tplink vs tp-link.

Thanks,
/jeff

https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath10k/boardfiles.html