I'm testing a Yuncore XD3200 in comparison to an UAP-AC-LITE, both running snapshot r3226-726e45d.
They have (nearly) identical hardware setup (QCA9563+QCA988x, 2 streams each), but the XD3200 has additional, external LNAs and PAs (SKY65174-21).
Both are running on channel 11, HT20, same txpower (10dBm) and same distance to the client (~2m)
While I'm only getting 18-22MBit (TCP, AP>Client) with the XD3200, the UAP-AC-LITE is stable at 38-45MBit, with the 'stock' XD3200 QSDK firmware and proprietary atheros driver I'm getting stable 39-41MBit.
it has been a few days since i tested QSDK and didn't write down the results, I just redid the test, again same setup as r3226.
SNR seems to be pretty identical to UAP-AC-LITE apart from ~3db tolerance.
LNA usually have set eeprom value of about 13dB which corresponds differences in your test. recently i've found how to enable it on xiaomi mini and it improved the throughput. if you can find reference driver it could be of help.
Ok, I did a few measurements on the LNA/PA supply and TX/RX switches with a DSO.
RX/TX switching seems to be fine, also LNA is getting ~3.3V when not transmitting and the PA is enabled at TX (although I did not measure if the chip is actulally transmitting at that time frame, I haven't got the equipment for that)
The difference I found between QSDK and ath9k/LEDE was:
QSDK is driving the PA with ~3.2V at R503/R823 (which results at ~3.0-3.1V at REF1/2)
ath9k (again snapshot r3226) is only supplying 2.8V, which results in ~2.6V at REF1/2, which is too low for the SKY65174-21 PA (2.75-3.1V).
So I guess the PA bias level seems to be incorrectly set.
I'm not quite sure why there is a difference in ath9k between QCA9561 and QCA9565 or if this is just a problem of the XD3200 layout, I've neither got the QCA9561 datasheet nor XD3200 schematics.
It would be great if someone with ath9k-dev background could comment on this, otherwise I'll post it on linux-wireless.
btw: This doesn't change the RX or LNA levels, I guess the difference is actually a display error, since I can see no performance degradation and it seems to be hardwired to 3.3V / RX enable.
no, this is not fixed in 17.01.3, this actually lies within the upstream ath9k code.
I'm still not sure if it's a problem of ath9k or if it's a problem of this particular device and the ath9k code handles QCA9561 and QCA9565 different for a reason. I haven't had time to start a discussion in linux-wireless, but it's on my ToDo list.
The question for me is, why is the TX Bias in ath9k differently set between QCA9565 and QCA9561? AFAIK the only difference between these chips are the internal ethernet switch in QCA9565.