RE: ATH9 driver issues on ARM64

Hi All, After further debugging we know the place it hangs. In function: static int ath_reset_internal (struct ath_softc *sc, struct ath9k_channel *hchan) { disable_irq(sc->irq); tasklet_disable(>intr_tq); tasklet_disable(>bcon_tasklet);

RE: ATH9 driver issues on ARM64

Hi All, After further debugging we know the place it hangs. In function: static int ath_reset_internal (struct ath_softc *sc, struct ath9k_channel *hchan) { disable_irq(sc->irq); tasklet_disable(>intr_tq); tasklet_disable(>bcon_tasklet);

RE: ATH9 driver issues on ARM64

> On Sat, Dec 10, 2016 at 02:40:48PM +, Bharat Kumar Gogada wrote: > > Hi, > > > > After taking some more lecroy traces, we see that after 2nd ASSERT from EP > on ARM64 we see continuous data movement of 32 dwords or 12 dwords and > never sign of DEASSERT. > > Comparatively on working traces

RE: ATH9 driver issues on ARM64

> On Sat, Dec 10, 2016 at 02:40:48PM +, Bharat Kumar Gogada wrote: > > Hi, > > > > After taking some more lecroy traces, we see that after 2nd ASSERT from EP > on ARM64 we see continuous data movement of 32 dwords or 12 dwords and > never sign of DEASSERT. > > Comparatively on working traces

Re: ATH9 driver issues on ARM64

On Sat, Dec 10, 2016 at 02:40:48PM +, Bharat Kumar Gogada wrote: > Hi, > > After taking some more lecroy traces, we see that after 2nd ASSERT from EP on > ARM64 we see continuous data movement of 32 dwords or 12 dwords and never > sign of DEASSERT. > Comparatively on working traces (x86)

Re: ATH9 driver issues on ARM64

On Sat, Dec 10, 2016 at 02:40:48PM +, Bharat Kumar Gogada wrote: > Hi, > > After taking some more lecroy traces, we see that after 2nd ASSERT from EP on > ARM64 we see continuous data movement of 32 dwords or 12 dwords and never > sign of DEASSERT. > Comparatively on working traces (x86)

RE: ATH9 driver issues on ARM64

Hi, After taking some more lecroy traces, we see that after 2nd ASSERT from EP on ARM64 we see continuous data movement of 32 dwords or 12 dwords and never sign of DEASSERT. Comparatively on working traces (x86) after 2nd assert there are only BAR register reads and writes and then DEASSERT,

RE: ATH9 driver issues on ARM64

Hi, After taking some more lecroy traces, we see that after 2nd ASSERT from EP on ARM64 we see continuous data movement of 32 dwords or 12 dwords and never sign of DEASSERT. Comparatively on working traces (x86) after 2nd assert there are only BAR register reads and writes and then DEASSERT,

RE: ATH9 driver issues on ARM64

Correcting Manohar Mail ID. > Hello there, > > as this is a thread about ath9k and ARM64, i'm not sure if i should > answer here or not, but i have similar "stalls" with ath9k on x86_64 > (starting with 4.9rc), stack trace is posted down below where the > original ARM64 stall traces are. > >

RE: ATH9 driver issues on ARM64

Correcting Manohar Mail ID. > Hello there, > > as this is a thread about ath9k and ARM64, i'm not sure if i should > answer here or not, but i have similar "stalls" with ath9k on x86_64 > (starting with 4.9rc), stack trace is posted down below where the > original ARM64 stall traces are. > >

Re: ATH9 driver issues on ARM64

Hello there, as this is a thread about ath9k and ARM64, i'm not sure if i should answer here or not, but i have similar "stalls" with ath9k on x86_64 (starting with 4.9rc), stack trace is posted down below where the original ARM64 stall traces are. Greetings, Tobias On 08.12.2016 18:36,

Re: ATH9 driver issues on ARM64

Hello there, as this is a thread about ath9k and ARM64, i'm not sure if i should answer here or not, but i have similar "stalls" with ath9k on x86_64 (starting with 4.9rc), stack trace is posted down below where the original ARM64 stall traces are. Greetings, Tobias On 08.12.2016 18:36,

Re: ATH9 driver issues on ARM64

On 09/12/16 11:04, Bharat Kumar Gogada wrote: >> On 09/12/16 02:07, Bharat Kumar Gogada wrote: On 08/12/16 18:33, Bharat Kumar Gogada wrote: >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: >>> 218: 61 0 0 0 GICv2 81 Level >>> mmc0

Re: ATH9 driver issues on ARM64

On 09/12/16 11:04, Bharat Kumar Gogada wrote: >> On 09/12/16 02:07, Bharat Kumar Gogada wrote: On 08/12/16 18:33, Bharat Kumar Gogada wrote: >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: >>> 218: 61 0 0 0 GICv2 81 Level >>> mmc0

RE: ATH9 driver issues on ARM64

> On 09/12/16 02:07, Bharat Kumar Gogada wrote: > >> On 08/12/16 18:33, Bharat Kumar Gogada wrote: > On 08/12/16 15:29, Bharat Kumar Gogada wrote: > > 218: 61 0 0 0 GICv2 81 Level > > mmc0 > > 219: 0 0 0

RE: ATH9 driver issues on ARM64

> On 09/12/16 02:07, Bharat Kumar Gogada wrote: > >> On 08/12/16 18:33, Bharat Kumar Gogada wrote: > On 08/12/16 15:29, Bharat Kumar Gogada wrote: > > 218: 61 0 0 0 GICv2 81 Level > > mmc0 > > 219: 0 0 0

Re: ATH9 driver issues on ARM64

On 09/12/16 02:07, Bharat Kumar Gogada wrote: >> On 08/12/16 18:33, Bharat Kumar Gogada wrote: On 08/12/16 15:29, Bharat Kumar Gogada wrote: > 218: 61 0 0 0 GICv2 81 Level > mmc0 > 219: 0 0 0 0

Re: ATH9 driver issues on ARM64

On 09/12/16 02:07, Bharat Kumar Gogada wrote: >> On 08/12/16 18:33, Bharat Kumar Gogada wrote: On 08/12/16 15:29, Bharat Kumar Gogada wrote: > 218: 61 0 0 0 GICv2 81 Level > mmc0 > 219: 0 0 0 0

RE: ATH9 driver issues on ARM64

Sorry, Forgot to add kernel version, we are using 4.6 kernel. > Hi, > Can any one tell, when exactly the chip sends ASSERT & DEASSERT in driver. > It might help us to debug issue further. > > Thanks & Regards, > Bharat > > > > > [+cc Kalle, ath9k list] > > > > Thanks, but please also CC

RE: ATH9 driver issues on ARM64

Sorry, Forgot to add kernel version, we are using 4.6 kernel. > Hi, > Can any one tell, when exactly the chip sends ASSERT & DEASSERT in driver. > It might help us to debug issue further. > > Thanks & Regards, > Bharat > > > > > [+cc Kalle, ath9k list] > > > > Thanks, but please also CC

RE: ATH9 driver issues on ARM64

Hi, Can any one tell, when exactly the chip sends ASSERT & DEASSERT in driver. It might help us to debug issue further. Thanks & Regards, Bharat > > > [+cc Kalle, ath9k list] > > Thanks, but please also CC linux-wireless. Full thread below for the folks > there. > > >> On Thu, Dec 08, 2016

RE: ATH9 driver issues on ARM64

Hi, Can any one tell, when exactly the chip sends ASSERT & DEASSERT in driver. It might help us to debug issue further. Thanks & Regards, Bharat > > > [+cc Kalle, ath9k list] > > Thanks, but please also CC linux-wireless. Full thread below for the folks > there. > > >> On Thu, Dec 08, 2016

RE: ATH9 driver issues on ARM64

> > >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: > > >> > > >> Two things: > > >> > > >>> Here is the cat /proc/interrupts (after we do interface up): > > >>> > > >>> root@:~# ifconfig wlan0 up > > >>> [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > >>>

RE: ATH9 driver issues on ARM64

> > >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: > > >> > > >> Two things: > > >> > > >>> Here is the cat /proc/interrupts (after we do interface up): > > >>> > > >>> root@:~# ifconfig wlan0 up > > >>> [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > >>>

RE: ATH9 driver issues on ARM64

> On 08/12/16 18:33, Bharat Kumar Gogada wrote: > >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: > >> > >> Two things: > >> > >>> Here is the cat /proc/interrupts (after we do interface up): > >>> > >>> root@:~# ifconfig wlan0 up > >>> [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not

RE: ATH9 driver issues on ARM64

> On 08/12/16 18:33, Bharat Kumar Gogada wrote: > >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: > >> > >> Two things: > >> > >>> Here is the cat /proc/interrupts (after we do interface up): > >>> > >>> root@:~# ifconfig wlan0 up > >>> [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not

Re: ATH9 driver issues on ARM64

On 08/12/16 18:33, Bharat Kumar Gogada wrote: >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: >> >> Two things: >> >>> Here is the cat /proc/interrupts (after we do interface up): >>> >>> root@:~# ifconfig wlan0 up >>> [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready >>>

Re: ATH9 driver issues on ARM64

On 08/12/16 18:33, Bharat Kumar Gogada wrote: >> On 08/12/16 15:29, Bharat Kumar Gogada wrote: >> >> Two things: >> >>> Here is the cat /proc/interrupts (after we do interface up): >>> >>> root@:~# ifconfig wlan0 up >>> [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready >>>

RE: ATH9 driver issues on ARM64

> On 08/12/16 15:29, Bharat Kumar Gogada wrote: > > Two things: > > > Here is the cat /proc/interrupts (after we do interface up): > > > > root@:~# ifconfig wlan0 up > > [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > root@Xilinx-ZCU102-2016_3:~# cat /proc/interrupts > >

RE: ATH9 driver issues on ARM64

> On 08/12/16 15:29, Bharat Kumar Gogada wrote: > > Two things: > > > Here is the cat /proc/interrupts (after we do interface up): > > > > root@:~# ifconfig wlan0 up > > [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > root@Xilinx-ZCU102-2016_3:~# cat /proc/interrupts > >

Re: ATH9 driver issues on ARM64

On 08/12/16 15:29, Bharat Kumar Gogada wrote: Two things: > Here is the cat /proc/interrupts (after we do interface up): > > root@:~# ifconfig wlan0 up > [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > root@Xilinx-ZCU102-2016_3:~# cat /proc/interrupts >CPU0

Re: ATH9 driver issues on ARM64

On 08/12/16 15:29, Bharat Kumar Gogada wrote: Two things: > Here is the cat /proc/interrupts (after we do interface up): > > root@:~# ifconfig wlan0 up > [ 1548.926601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > root@Xilinx-ZCU102-2016_3:~# cat /proc/interrupts >CPU0

Re: ATH9 driver issues on ARM64

Bharat Kumar Gogada writes: > > [+cc Kalle, ath9k list] Thanks, but please also CC linux-wireless. Full thread below for the folks there. >> On Thu, Dec 08, 2016 at 01:49:42PM +, Bharat Kumar Gogada wrote: >> > Hi, >> > >> > Did anyone test Atheros ATH9

Re: ATH9 driver issues on ARM64

Bharat Kumar Gogada writes: > > [+cc Kalle, ath9k list] Thanks, but please also CC linux-wireless. Full thread below for the folks there. >> On Thu, Dec 08, 2016 at 01:49:42PM +, Bharat Kumar Gogada wrote: >> > Hi, >> > >> > Did anyone test Atheros ATH9

RE: ATH9 driver issues on ARM64

> [+cc Kalle, ath9k list] > > On Thu, Dec 08, 2016 at 01:49:42PM +, Bharat Kumar Gogada wrote: > > Hi, > > > > Did anyone test Atheros ATH9 driver(drivers/net/wireless/ath/ath9k/) > > on ARM64. The end point is TP link wifi card with which supports > > only legacy interrupts. > > If it

RE: ATH9 driver issues on ARM64

> [+cc Kalle, ath9k list] > > On Thu, Dec 08, 2016 at 01:49:42PM +, Bharat Kumar Gogada wrote: > > Hi, > > > > Did anyone test Atheros ATH9 driver(drivers/net/wireless/ath/ath9k/) > > on ARM64. The end point is TP link wifi card with which supports > > only legacy interrupts. > > If it

Re: ATH9 driver issues on ARM64

[+cc Kalle, ath9k list] On Thu, Dec 08, 2016 at 01:49:42PM +, Bharat Kumar Gogada wrote: > Hi, > > Did anyone test Atheros ATH9 driver(drivers/net/wireless/ath/ath9k/) > on ARM64. The end point is TP link wifi card with which supports > only legacy interrupts. If it works on other arches

Re: ATH9 driver issues on ARM64

[+cc Kalle, ath9k list] On Thu, Dec 08, 2016 at 01:49:42PM +, Bharat Kumar Gogada wrote: > Hi, > > Did anyone test Atheros ATH9 driver(drivers/net/wireless/ath/ath9k/) > on ARM64. The end point is TP link wifi card with which supports > only legacy interrupts. If it works on other arches