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] AR9380 MSI
Date: Fri, 1 Jul 2011 17:38:07 +0800	[thread overview]
Message-ID: <F6259B467C2CCE44A8F3D92A9BFE1D3D64BAFBBD36@EAPEX1MAIL1.st.com> (raw)
In-Reply-To: <20110630045048.GA16685@infinet.ru>

Hi,
Just to update you all I could not make MSI work for AR9285 card (this is the card I only tried with), even after I enabled it in the driver by pci_enable_msi() routine. I could make some Wi-Fi card from other vendor working using the same procedure.
I was interested to know whether AR9380 works OK with MSI.

Regarding correlation between Wi-Fi scan and MSI:
We can interpret that if Wi-Fi scan works OK ie Wi-Fi driver is active. This means Wi-Fi card is able to interrupt the host successfully. And the interrupt mechanism is either INTA(legacy interrupt) or MSI or MSI-X.

Regards,
Sucheta

-----Original Message-----
From: ath9k-devel-bounces@lists.ath9k.org [mailto:ath9k-devel-bounces at lists.ath9k.org] On Behalf Of Alex Hacker
Sent: Thursday, June 30, 2011 10:21 AM
To: Matevz Langus
Cc: ath9k-devel at venema.h4ckr.net
Subject: Re: [ath9k-devel] AR9380 MSI

I'd not work with MSI and our Atheros based hardware do not require it. I only
have a AR9380 based card and done some tests on standard PC for Sucheta ROY.
I haavn't much knowlege how the MSI is processed in Linux kernel, but it seems
not working with AR9380 without some special setup in hardware.
Really don't understand how MSI can correlate with scan results...
Best regards,
Alex.

On Wed, Jun 29, 2011 at 08:56:06PM +0200, Matevz Langus wrote:
> Hello,
> 
> I have tried the same thing as you did on Freescale P1020 processor (Power architecture) using 2.6.39.1 and I am getting some results when performing scanning.
> Before enabling MSI in ath9k pci.c, I newer got any scan results. But now when enabled I am getting at least 1 network very often.
> 
> However it seems the operation is not very stable. I can not connect to the AP. 
> 
> Have you made any progress on this one?
> I got an answer from Atheros guys, they use INTA by default. And also looking at defines AR_PCIE_MSI and AR_PCIE_MSI_ENABLE I got a question: who is using that defines? It seems like nobody???
> 
> regards,
>   Matevz Langus
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

  reply	other threads:[~2011-07-01  9:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30  4:50 [ath9k-devel] AR9380 MSI Alex Hacker
2011-07-01  9:38 ` Sucheta ROY [this message]
2011-07-01 10:18   ` Matevz Langus
  -- strict thread matches above, loose matches on Subject: below --
2011-06-28 22:12 [ath9k-devel] [RFC/RFT] ath9k: support for multiple beacon intervals Steve Brown
2011-06-29  1:31 ` Adrian Chadd
2011-06-29 13:22   ` Steve Brown
2011-06-29 17:15     ` Adrian Chadd
2011-06-29 18:56       ` [ath9k-devel] AR9380 MSI Matevz Langus
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:41   ` Mohammed Shafi
2011-05-18  1:09     ` Peter Stuge
2011-05-18  2:15       ` Adrian Chadd
2011-05-18  9:29         ` Sucheta ROY
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

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=F6259B467C2CCE44A8F3D92A9BFE1D3D64BAFBBD36@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.