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: Fri, 9 Dec 2016 11:04:00 +0000 [thread overview]
Message-ID: <8520D5D51A55D047800579B094147198263A7F11@XAP-PVEXMBX02.xlnx.xilinx.com> (raw)
In-Reply-To: <d8bc6283-8b37-76d6-8ff1-0847ee015380@arm.com>
> 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 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?
> >>
> > Yes agreed.
> > For legacy interrupts im using irq_set_chained_handler_and_data so the
> > irq line between bridge and GIC Will not be shown here. The above how
> > is virq for legacy, which is given by kernel, not sure why its state is set to edge.
>
> Well, you should try and find out. Edge triggering for legacy interrupts is a real
> bug, and I don't think it has anything to do with arm64 (despite what the subject
> says).
>
Thanks Marc. Here is the ARM32 bit log for cat /proc/interrupts,
Here also it shows edge but still scan works successfully.
root@:~#cat /proc/interrupts
CPU0 CPU1
16: 1 0 GIC-0 27 Edge gt
17: 0 0 GIC-0 43 Level ttc_clockevent
18: 3049 1170 GIC-0 29 Edge twd
21: 43 0 GIC-0 39 Level f8007100.adc
141: 462 0 GIC-0 57 Level cdns-i2c
143: 0 0 GIC-0 35 Level f800c000.ocmc
144: 1259 0 GIC-0 82 Level xuartps
145: 3 0 GIC-0 51 Level e000d000.spi
146: 0 0 GIC-0 54 Level eth0
147: 54 0 GIC-0 56 Level mmc0
148: 0 0 GIC-0 45 Level f8003000.dmac
149: 0 0 GIC-0 46 Level f8003000.dmac
150: 0 0 GIC-0 47 Level f8003000.dmac
151: 0 0 GIC-0 48 Level f8003000.dmac
152: 0 0 GIC-0 49 Level f8003000.dmac
153: 0 0 GIC-0 72 Level f8003000.dmac
154: 0 0 GIC-0 73 Level f8003000.dmac
155: 0 0 GIC-0 74 Level f8003000.dmac
156: 0 0 GIC-0 75 Level f8003000.dmac
157: 0 0 GIC-0 40 Level f8007000.devcfg
163: 0 0 GIC-0 53 Level e0002000.usb
164: 0 0 GIC-0 41 Edge f8005000.watchdog
165: 158 0 GIC-0 61 Level xilinx-pcie
166: 122 18 dummy 1 Edge ath9k
IPI1: 0 0 Timer broadcast interrupts
IPI2: 1101 2349 Rescheduling interrupts
IPI3: 34 20 Function call interrupts
IPI4: 0 0 CPU stop interrupts
IPI5: 0 0 IRQ work interrupts
IPI6: 0 0 completion interrupts
root@Xilinx-ZC706-2016_3:~# iw dev wlnan0 scan
BSS d8:c7:c8:26:6a:72(on wlan0)
TSF: 349496494967 usec (4d, 01:04:56)
freq: 2412
beacon interval: 100 TUs
capability: ESS ShortPreamble ShortSlotTime (0x0421)
signal: -47.00 dBm
last seen: 2170 ms ago
.....
....
Thanks & Regards,
Bharat
next prev parent reply other threads:[~2016-12-09 11:04 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
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 [this message]
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=8520D5D51A55D047800579B094147198263A7F11@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).