All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sucheta ROY <sucheta.roy@st.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9285 MSI
Date: Wed, 18 May 2011 17:29:36 +0800	[thread overview]
Message-ID: <F6259B467C2CCE44A8F3D92A9BFE1D3D64BAB72B9F@EAPEX1MAIL1.st.com> (raw)
In-Reply-To: BANLkTimh=OEc7s3Z3Kc_V8H4uNgkUT9d5A@mail.gmail.com

Hi,

I am afraid whether AR9285 chip can generate MSI at all, although it shows MSI capability structure at the time of enumeration. In continuation to my previous mail here goes my observation:
Even if MSI is enabled; MSI (a kind of PCIe Mem WR TLP) interrupt is not generated by AR9285 at the time of iwlist wlan0 scan. I have tested this part through PCIe protocol analyzer. Have anybody worked with some later on cards like AR9340 or AR9380? If yes, can it be checked whether they are actually working with MSI?

Thanks and Regards,
Sucheta
-----Original Message-----
From: Sucheta ROY 
Sent: Wednesday, May 18, 2011 9:58 AM
To: 'Adrian Chadd'; ath9k-devel at lists.ath9k.org
Subject: RE: [ath9k-devel] AR9285 MSI

Hi,

Thanks to all for your response. The limitation of my platform is it only supports MSI and does not support legacy interrupt. I am using with AR9285 card and in 
reg.h:

#define AR_PCIE_MSI                              0x4094
#define AR_PCIE_MSI_ENABLE                       0x00000001   

are defined.

I have also called "pci_enable_msi(pdev)" before request_irq(...) in pci.c file of ath9K. 
Wlan0 is detected, when I do cat /proc/interrupts it shows PCIe_MSI for ath9K in the interrupt lists.But the problem is wlan0 cannot scan any WiFi network around. When I use the same AR9285 card on some other platform which supports legacy interrupt scan works OK.

Kindly provide your suggestions.

Thanks and Regards,
Sucheta

-----Original Message-----
From: ath9k-devel-bounces@lists.ath9k.org [mailto:ath9k-devel-bounces at lists.ath9k.org] On Behalf Of Adrian Chadd
Sent: Wednesday, May 18, 2011 7:45 AM
To: ath9k-devel at lists.ath9k.org
Subject: Re: [ath9k-devel] AR9285 MSI

On 18 May 2011 09:09, Peter Stuge <peter@stuge.se> wrote:
> Mohammed Shafi wrote:
>> bits 8:4 MSI Interrupt vector
>
> Cool!
>
>
>> but several things need to be addressed before enabling this interrupt
>
> Which ones?

Is MSI really that important just yet? :-) An AR9285 is only going to
be doing up to 150mbit of traffic. The MACs on AR5416 and later have
interrupt mitigation (and its enabled in ath9k.)

I mean, MSI would be cool, but there's other things to try and nut out
first, no? :)


Adrian
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

  parent reply	other threads:[~2011-05-18  9:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 11:16 [ath9k-devel] setting AR_NAV register Andrés García Saavedra
2011-05-17 13:29 ` [ath9k-devel] AR9285 MSI Sucheta ROY
2011-05-17 14:39   ` Mohammed Shafi
2011-05-17 14:41   ` Mohammed Shafi
2011-05-18  1:09     ` Peter Stuge
2011-05-18  2:15       ` Adrian Chadd
2011-05-18  4:28         ` Sucheta ROY
2011-05-18  9:29         ` Sucheta ROY [this message]
2011-05-18 10:54           ` Senthilkumar Balasubramanian
2011-05-19  0:32             ` Peter Stuge
2011-05-19  4:33               ` Sucheta ROY
2011-05-19  6:01                 ` Alex Hacker
2011-05-19  8:35                   ` [ath9k-devel] AR9380 MSI Sucheta ROY
2011-05-19 11:06                     ` Falk-Moritz Schaefer
2011-05-19 12:02                       ` Sucheta ROY
2011-05-19 12:32                         ` Falk-Moritz Schaefer
2011-05-19 12:16                     ` Alex Hacker
2011-05-20  9:30                       ` Sucheta ROY
2011-05-20 10:15                         ` Alex Hacker
2011-05-19  8:41                   ` [ath9k-devel] AR9285 MSI Sucheta ROY
2011-05-18  4:45       ` Mohammed Shafi
2011-05-17 14:27 ` [ath9k-devel] setting AR_NAV register Mohammed Shafi
2011-08-09 12:37   ` Manuel Sáez

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=F6259B467C2CCE44A8F3D92A9BFE1D3D64BAB72B9F@EAPEX1MAIL1.st.com \
    --to=sucheta.roy@st.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.