| e6df5ff5 | 08-Jul-2016 |
Adrian Chadd <[email protected]> |
[ath_hal] add in locationing timer support and capabilities.
* add support to read the timer and capability * add support to enable/disable the location timer.
On AR9380 at least, enabling the loca
[ath_hal] add in locationing timer support and capabilities.
* add support to read the timer and capability * add support to enable/disable the location timer.
On AR9380 at least, enabling the location timer is required to make the timer tick, otherwise location packets return a timestamp of 0. However, it then makes /all/ RX packets use the RX location timestamp instead of the TSF timestamp.
So, unless I find another magical way to do location timestamping, we will have to dynamically switch things on/off and ensure the TX/RX path handles the "different" timestamps correctly.
Tested:
* AR9380, STA mode
show more ...
|
| b10add4e | 08-Jul-2016 |
Adrian Chadd <[email protected]> |
[ath_hal] add locationing / tx-beamforming RX status descriptor decoding.
* LOC_INFO is mostly just "did this packet come with a locationing timestamp instead of TSF"; * Decode not-sounding, uploa
[ath_hal] add locationing / tx-beamforming RX status descriptor decoding.
* LOC_INFO is mostly just "did this packet come with a locationing timestamp instead of TSF"; * Decode not-sounding, uploaded-data, data-valid, data type and number of extension spatial streams.
show more ...
|
| ada3f603 | 08-Jul-2016 |
Adrian Chadd <[email protected]> |
[ath_hal] Add setting positioning bit and clear sounding-disable bit.
* If fast_ts is set then the TX timestamp is the fast timestamp, not normal TSF. * If the TX descriptor has the position bit s
[ath_hal] Add setting positioning bit and clear sounding-disable bit.
* If fast_ts is set then the TX timestamp is the fast timestamp, not normal TSF. * If the TX descriptor has the position bit set then request locationing and clear sounding-disable. This way we (a) get the response with the TX timestamp from the location side of things, and (b) we get a CSI dump of the response ACK, which we will eventually use in the locationing path.
show more ...
|
| 3648197a | 08-Jun-2016 |
Adrian Chadd <[email protected]> |
[ath_hal] modify the xmit code to use temporary variables for setting qmisc/dmisc.
This is in preparation for some other TDMA fixes which will hopefully end with having working TDMA.
But, it does a
[ath_hal] modify the xmit code to use temporary variables for setting qmisc/dmisc.
This is in preparation for some other TDMA fixes which will hopefully end with having working TDMA.
But, it does avoid lots of read/modify/writes in the txq setup path.
show more ...
|
| e4eb838c | 08-Jun-2016 |
Adrian Chadd <[email protected]> |
[ath_hal] correctly initialise the CAB queue default value
* Allow readyTime to just be programmed in directly * The beacon interval and all of the beacon timing sysctl's are in TU, not TSF. So,
[ath_hal] correctly initialise the CAB queue default value
* Allow readyTime to just be programmed in directly * The beacon interval and all of the beacon timing sysctl's are in TU, not TSF. So, we were doing the wrong math on the CAB programming in the first place.
show more ...
|
| 09ff344b | 05-Jun-2016 |
Adrian Chadd <[email protected]> |
[ath_hal] add AR9462 (jupiter) RX gain / XLNA programming.
This seems to make 5G work better.
It doesn't fix powersave handling though, that still sees the PHY get stuck during initial calibration
[ath_hal] add AR9462 (jupiter) RX gain / XLNA programming.
This seems to make 5G work better.
It doesn't fix powersave handling though, that still sees the PHY get stuck during initial calibration and everything goes pear shaped. I'll look into that later.
Tested:
* QCAFN222 NIC, STA mode, 5GHz
Obtained from: Linux ath9k
show more ...
|
| fa63ec53 | 05-Jun-2016 |
Adrian Chadd <[email protected]> |
[ath_hal] Add Jupiter 2.1 (AR9462 mac 640.3) support.
Turns out I wasn't even initialising or programming a lot of stuff for the AR9462 2.1 chip. Oops.
This mostly gets it working. powersave scan
[ath_hal] Add Jupiter 2.1 (AR9462 mac 640.3) support.
Turns out I wasn't even initialising or programming a lot of stuff for the AR9462 2.1 chip. Oops.
This mostly gets it working. powersave scan results in some pretty hilarious NFcal hangs and I don't see beacons reliably. There are still some xlna gain tables missing that ath9k has; I'll follow up with some fixes and then see if the QCAFN222 NIC I have tests this path.
Tested:
* QCAFN222 NIC, STA mode, 2GHz and 5GHz
show more ...
|