Re: ATH9 driver issues on ARM64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
>>> root@Xilinx-ZCU102-2016_3:~# cat /proc/interrupts
>>>            CPU0       CPU1       CPU2       CPU3
>>>   1:          0          0          0          0     GICv2  29 Edge      arch_timer
>>>   2:      19873      20058      19089      17435     GICv2  30 Edge      arch_timer

By the way, please use a recent kernel. Seeing edge here means you're
running with something that is a bit old (and broken). And since you
haven't even said what revision of the kernel you're using, hslping you
is not an easy task. tglx told you something similar about a week ago.

>>>  12:          0          0          0          0     GICv2 156 Level     zynqmp-dma
>>>  13:          0          0          0          0     GICv2 157 Level     zynqmp-dma
>>>  14:          0          0          0          0     GICv2 158 Level     zynqmp-dma
>>>  15:          0          0          0          0     GICv2 159 Level     zynqmp-dma
>>>  16:          0          0          0          0     GICv2 160 Level     zynqmp-dma
>>>  17:          0          0          0          0     GICv2 161 Level     zynqmp-dma
>>>  18:          0          0          0          0     GICv2 162 Level     zynqmp-dma
>>>  19:          0          0          0          0     GICv2 163 Level     zynqmp-dma
>>>  20:          0          0          0          0     GICv2 164 Level     Mali_GP_MMU, Mali_GP,
>> Mali_PP0_MMU, Mali_PP0, Mali_PP1_MMU, Mali_PP1
>>
>> I'm not even going to consider looking at something that is running out of tree
>> code. So please start things with a fresh kernel that doesn't contain stuff we
>> can't debug.
>>
> Ok will test with fresh kernel.
> 
>>>  30:          0          0          0          0     GICv2  95 Level     eth0, eth0
>>> 206:        314          0          0          0     GICv2  49 Level     cdns-i2c
>>> 207:         40          0          0          0     GICv2  50 Level     cdns-i2c
>>> 209:          0          0          0          0     GICv2 150 Level     nwl_pcie:misc
>>> 214:         12          0          0          0     GICv2  47 Level     ff0f0000.spi
>>> 215:          0          0          0          0     GICv2  58 Level     ffa60000.rtc
>>> 216:          0          0          0          0     GICv2  59 Level     ffa60000.rtc
>>> 217:          0          0          0          0     GICv2 165 Level     ahci-ceva[fd0c0000.ahci]
>>> 218:         61          0          0          0     GICv2  81 Level     mmc0
>>> 219:          0          0          0          0     GICv2 187 Level     arm-smmu global fault
>>> 220:        471          0          0          0     GICv2  53 Level     xuartps
>>> 223:          0          0          0          0     GICv2 154 Level     fd4c0000.dma
>>> 224:          3          0          0          0     dummy   1 Edge      ath9k
>>
>> What is this "dummy" controller? And if that's supposed to be a legacy interrupt
>> from the PCI device, it has the wrong trigger.
> 
> Yes it is for legacy interrupt, wrong trigger means ? 

Aren't legacy interrupts supposed to be *level* triggered, and not edge?

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux