linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
To: Marc Zyngier <marc.zyngier@arm.com>, Bjorn Helgaas <helgaas@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"Janusz.Dziedzic@tieto.com" <Janusz.Dziedzic@tieto.com>,
	"rmanohar@qti.qualcomm.com" <rmanohar@qti.qualcomm.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	"ath9k-devel@qca.qualcomm.com" <ath9k-devel@qca.qualcomm.com>
Subject: RE: ATH9 driver issues on ARM64
Date: Thu, 8 Dec 2016 18:33:17 +0000	[thread overview]
Message-ID: <8520D5D51A55D047800579B094147198263A77C5@XAP-PVEXMBX02.xlnx.xilinx.com> (raw)
In-Reply-To: <48ec7cdf-5a5f-bd4a-3ba2-a7bb294e161f@arm.com>

> 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
> >  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 ? 

Thanks & Regards,
Bharat

  reply	other threads:[~2016-12-08 18:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 13:49 ATH9 driver issues on ARM64 Bharat Kumar Gogada
2016-12-08 14:56 ` Bjorn Helgaas
2016-12-08 15:29   ` Bharat Kumar Gogada
2016-12-08 17:36     ` Kalle Valo
2016-12-09  5:00       ` Bharat Kumar Gogada
2016-12-09  6:55         ` Bharat Kumar Gogada
2016-12-09 14:22       ` Tobias Klausmann
2016-12-09 14:35         ` Bharat Kumar Gogada
2016-12-10 14:40         ` Bharat Kumar Gogada
2016-12-12 16:31           ` Bjorn Helgaas
2016-12-14  5:09             ` Bharat Kumar Gogada
2016-12-22  7:19               ` Bharat Kumar Gogada
2016-12-08 18:07     ` Marc Zyngier
2016-12-08 18:33       ` Bharat Kumar Gogada [this message]
2016-12-08 19:09         ` Marc Zyngier
2016-12-09  2:07           ` Bharat Kumar Gogada
2016-12-09  2:39             ` Bharat Kumar Gogada
2016-12-09 10:50             ` Marc Zyngier
2016-12-09 11:04               ` Bharat Kumar Gogada
2016-12-09 11:24                 ` Marc Zyngier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8520D5D51A55D047800579B094147198263A77C5@XAP-PVEXMBX02.xlnx.xilinx.com \
    --to=bharat.kumar.gogada@xilinx.com \
    --cc=Janusz.Dziedzic@tieto.com \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=helgaas@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=rmanohar@qti.qualcomm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).