Re: ath10k Issue with eduroam?

2017-05-31 Thread Ben Greear
I hacked quite a bit on the rate-ctrl, and have tested in /b, /g, a, n, and /AC modes. Blair, if you want, please try my firmware (beta-19) and see if it works better. If it crashes, send me dmesg and I will try to debug it. http://www.candelatech.com/ath10k-10.1.php Thanks, Ben On

Re: ath10k Issue with eduroam?

2017-05-31 Thread Adrian Chadd
oh is the NIC /disappearing/ or firmware crashing? There are ... and I know someone's going to slap me, but firmware/rate control bugs in STA mode on these chips in 11bg (not n, not ac) modes. I can't (yet) get eyeballs at QCA on it to fix them :( -adrian

Re: [PATCH] ath10k: add configurable debugging.

2017-05-31 Thread Adrian Chadd
On 31 May 2017 at 14:28, Arend van Spriel wrote: > On 31-05-17 22:23, Adrian Chadd wrote: >> On 31 May 2017 at 13:20, Arend van Spriel >> wrote: >>> On 31-05-17 14:16, Kalle Valo wrote: Adrian Chadd writes:

Re: [PATCH] ath10k: add configurable debugging.

2017-05-31 Thread Arend van Spriel
On 31-05-17 22:23, Adrian Chadd wrote: > On 31 May 2017 at 13:20, Arend van Spriel > wrote: >> On 31-05-17 14:16, Kalle Valo wrote: >>> Adrian Chadd writes: >>> This adds a few configurable debugging options: * driver debugging

Re: [PATCH] ath10k: add configurable debugging.

2017-05-31 Thread Adrian Chadd
On 31 May 2017 at 13:20, Arend van Spriel wrote: > On 31-05-17 14:16, Kalle Valo wrote: >> Adrian Chadd writes: >> >>> This adds a few configurable debugging options: >>> >>> * driver debugging and tracing is now configurable per device >>> *

Re: [PATCH] ath10k: add configurable debugging.

2017-05-31 Thread Arend van Spriel
On 31-05-17 14:16, Kalle Valo wrote: > Adrian Chadd writes: > >> This adds a few configurable debugging options: >> >> * driver debugging and tracing is now configurable per device >> * driver debugging and tracing is now configurable at runtime >> * the debugging / tracing

Re: is it possible to enable dualband or even 2.4 GHz on QCA9994? (Compex WLE1216V5-20)

2017-05-31 Thread Adrian Chadd
On 30 May 2017 at 22:23, Lindner, Frank wrote: > Hi. > 9994 is Cascade, which should be 2.4 GHz capable as fas as Qualcomm is > correct on their specs site. > Question was not, which other card can do 2.4 GHz. I want to enable 2.4 GHz / > dualband mode via some registers

Re: [2/3] ath10k: Fix napi related crash when otp fails.

2017-05-31 Thread Ben Greear
On 05/31/2017 05:27 AM, Kalle Valo wrote: Ben Greear wrote: The failure case is something like this: otp fails (probably because BMI timeout was too short) so core_start fails so the entire firmware load fails..but since it was not ever started properly, then it is

Re: [PATCH] Per chain RSSI reporting

2017-05-31 Thread Kalle Valo
Norik Dzhandzhapanyan writes: > Inserting the smoothing function here is motivated by what we see as > 'spikes' in rssi data under weak rssi conditions. Figured its best to > get rid of the 'bogus' data as close to the source as possible. Also > to minimize the impact on

Re: [3/3] ath10k: Log when longer bmi cmds happen.

2017-05-31 Thread Ben Greear
On 05/31/2017 05:46 AM, Kalle Valo wrote: Ben Greear wrote: This lets one have a clue that maybe timeouts are happening when we just aren't waiting long enough. Signed-off-by: Ben Greear Signed-off-by: Kalle Valo

Re: [PATCH] Per chain RSSI reporting

2017-05-31 Thread Kalle Valo
Adrian Chadd writes: > I have something local that I've been meaning to push up to do this, > but with no smoothing. Ideally (!) smoothing is done optionally in > mac80211. > > What do you think about just committing the per-chain RSSI stuff to > mac80211 so it shows up right

Re: [PATCH] Per chain RSSI reporting

2017-05-31 Thread Kalle Valo
Norik Dzhandzhapanyan writes: > Add support for per chain RSSI reporting w/smoothing. > > Signed-off-by: Norik Dzhandzhapanyan nor...@ethertronics.com > > > --- htt_rx.c.orig 2017-05-26 15:26:37.918504255 -0700 > +++ htt_rx.c2017-05-26 12:10:33.139809025 -0700 >

Re: [3/3] ath10k: Log when longer bmi cmds happen.

2017-05-31 Thread Kalle Valo
Ben Greear wrote: > This lets one have a clue that maybe timeouts are happening > when we just aren't waiting long enough. > > Signed-off-by: Ben Greear > Signed-off-by: Kalle Valo I did some cosmetic changes and ret

Re: [2/3] ath10k: Fix napi related crash when otp fails.

2017-05-31 Thread Kalle Valo
Ben Greear wrote: > The failure case is something like this: > > otp fails (probably because BMI timeout was too short) > so core_start fails > so the entire firmware load fails..but since it was not ever > started properly, then it is not stopped as far as PCI is

Re: [PATCH] ath10k: add configurable debugging.

2017-05-31 Thread Kalle Valo
Adrian Chadd writes: > This adds a few configurable debugging options: > > * driver debugging and tracing is now configurable per device > * driver debugging and tracing is now configurable at runtime > * the debugging / tracing is not run at all (besides a mask check) >

Re: [PATCH] ath10k: add configurable debugging.

2017-05-31 Thread Kalle Valo
Adrian Chadd writes: > This adds a few configurable debugging options: > > * driver debugging and tracing is now configurable per device So this means that there's a debugfs file /sys/kernel/debug/ieee80211/phy0/ath10k/debug for every ath10k device. Sounds like a good idea.

Re: go back to using dma_alloc_coherent() for firmware scratch memory.

2017-05-31 Thread Kalle Valo
Adrian Chadd wrote: > This reverts commit b057886524be ("ath10k: do not use coherent memory for > allocated device memory chunks") in 2015 which converted this allocation from > dma_map_coherent() to kzalloc() / dma_map_single(). > > The current problem manifests when using