linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	"Janusz.Dziedzic@tieto.com" <Janusz.Dziedzic@tieto.com>,
	"rmanohar@qti.qualcomm.com" <rmanohar@qti.qualcomm.com>
Subject: ATH9 driver issues on ARM64
Date: Thu, 8 Dec 2016 13:49:42 +0000	[thread overview]
Message-ID: <8520D5D51A55D047800579B094147198263A7222@XAP-PVEXMBX02.xlnx.xilinx.com> (raw)

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.

We are trying to test it on ARM64 with (drivers/pci/host/pcie-xilinx-nwl.c) as root port.

EP is getting enumerated and able to link up. 

But when we start scan system gets hanged.

When we took trace we see that after we start scan assert message is sent but 
there is no de assert from end point.

What might cause end point not sending de assert ?

We are not seeing any issues on 32-bit ARM platform and X86 platform. 
 
Regards,
Bharat

             reply	other threads:[~2016-12-08 14:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 13:49 Bharat Kumar Gogada [this message]
2016-12-08 14:56 ` ATH9 driver issues on ARM64 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
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=8520D5D51A55D047800579B094147198263A7222@XAP-PVEXMBX02.xlnx.xilinx.com \
    --to=bharat.kumar.gogada@xilinx.com \
    --cc=Janusz.Dziedzic@tieto.com \
    --cc=helgaas@kernel.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).