Re: [ath9k-devel] regression: ath_tx_edma_tasklet() Illegal idle entry in RCU read-side critical section

2016-12-20 Thread Valo, Kalle
Gabriel C <nix.or@gmail.com> writes: > On 18.12.2016 21:14, Paul E. McKenney wrote: >> On Sun, Dec 18, 2016 at 07:57:42PM +0000, Valo, Kalle wrote: >>> Tobias Klausmann <tobias.johannes.klausm...@mni.thm.de> writes: >>> >>>> A patch for

Re: [ath9k-devel] regression: ath_tx_edma_tasklet() Illegal idle entry in RCU read-side critical section

2016-12-18 Thread Valo, Kalle
Tobias Klausmann writes: > A patch for this is already floating on the ML for a while now latest: > (ath9k: do not return early to fix rcu unlocking) It's here: https://patchwork.kernel.org/patch/9472709/ > Hopefully Kalle will include it in one of his

Re: [ath9k-devel] [PATCH v2 0/7] ath9k: EEPROM swapping improvements

2016-12-13 Thread Valo, Kalle
Martin Blumenstingl <martin.blumensti...@googlemail.com> writes: > Hello Kalle, > > On Fri, Nov 25, 2016 at 4:06 PM, Valo, Kalle <kv...@qca.qualcomm.com> wrote: >> Kalle Valo <kv...@codeaurora.org> writes: >> >>> Martin Blumenst

Re: [ath9k-devel] [PATCH] ath9k: Move generic entries below specific ones in ath_pci_id_table.

2016-11-19 Thread Valo, Kalle
"Vittorio Gambaletta (VittGam)" <linux-wirel...@vittgam.net> writes: > Hello, > > On 12/10/2016 17:01:08 CEST, Valo, Kalle wrote: > >> So to tell the full story I'll change the commit log to something like >> below. Does it look ok to you? > >

Re: [ath9k-devel] [RFC 1/2] ath9k: work around AR_CFG 0xdeadbeef chip hang

2016-11-19 Thread Valo, Kalle
Sven Eckelmann writes: > From: Simon Wunderlich > > QCA 802.11n chips (especially AR9330/AR9340) sometimes end up in a state in > which a read of AR_CFG always returns 0xdeadbeef. This should not happen > when when the power_mode of

Re: [ath9k-devel] [PATCH] ath9k: Move generic entries below specific ones in ath_pci_id_table.

2016-10-12 Thread Valo, Kalle
"Vittorio Gambaletta (VittGam)" writes: >>> So, after seeing that the rest of the file is sorted this way (generic >>> section after the specific ones), I concluded that the 0x002A sorting >>> was wrong in the first place, and so is 0x0029. Then I sent this patch >>>

Re: [ath9k-devel] ATH9K warnings from commit b2d70d494

2016-06-16 Thread Valo, Kalle
John S Gruber writes: > It's an AR9462 > > Here's the wifi adapter: > > 03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter > (rev 01) > Subsystem: Lite-On Communications Inc Device 6621 > Flags: bus master, fast devsel, latency 0, IRQ 19 > Memory

Re: [ath9k-devel] ATH9K warnings from commit b2d70d494

2016-06-16 Thread Valo, Kalle
(Adding linux-wireless) johnsgru...@gmail.com writes: > I'm getting many warning stack traces fom the above--at least two every 5 > seconds whether or not connected via wireless. > > Samples are below. > > On further investigation I see that for each of the pair gpio = 11, for > the first

Re: [ath9k-devel] [PATCH 1/3] ath9k: reuse ar9003_hw_tx_power_regwrite for tx99 setup

2016-05-09 Thread Valo, Kalle
Helmut Schaa writes: > The same functionality as ar9003_hw_tx_power_regwrite is hardcoded in > ar9003_hw_tx99_set_txpower. Just reuse the existing > ar9003_hw_tx_power_regwrite > for TX99 setup too. > > Signed-off-by: Helmut Schaa