* [ath9k-devel] setting AR_NAV register
@ 2011-05-17 11:16 Andrés García Saavedra
2011-05-17 13:29 ` [ath9k-devel] AR9285 MSI Sucheta ROY
2011-05-17 14:27 ` [ath9k-devel] setting AR_NAV register Mohammed Shafi
0 siblings, 2 replies; 27+ messages in thread
From: Andrés García Saavedra @ 2011-05-17 11:16 UTC (permalink / raw)
To: ath9k-devel
Dear all,
I would like to set the NAV value from software in mac80211/ath9k. Is it
possible to change this value, e.g., using the AR_NAV?
Thank you for your help,
Andr?s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110517/737957a1/attachment.htm
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
2011-05-17 11:16 [ath9k-devel] setting AR_NAV register Andrés García Saavedra
@ 2011-05-17 13:29 ` Sucheta ROY
2011-05-17 14:39 ` Mohammed Shafi
2011-05-17 14:41 ` Mohammed Shafi
2011-05-17 14:27 ` [ath9k-devel] setting AR_NAV register Mohammed Shafi
1 sibling, 2 replies; 27+ messages in thread
From: Sucheta ROY @ 2011-05-17 13:29 UTC (permalink / raw)
To: ath9k-devel
Hi,
Has anybody ever tried Message Signal Interrupt (MSI) enabling in any of Atheros PCIe-WiFi card driver under Linux? By default driver supports legacy interrupt.
Regards,
Sucheta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110517/cb969b7a/attachment.htm
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] setting AR_NAV register
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:27 ` Mohammed Shafi
2011-08-09 12:37 ` Manuel Sáez
1 sibling, 1 reply; 27+ messages in thread
From: Mohammed Shafi @ 2011-05-17 14:27 UTC (permalink / raw)
To: ath9k-devel
2011/5/17 Andr?s Garc?a Saavedra <andres.garcia.saavedra@gmail.com>:
> Dear all,
>
> I would like to set the NAV value from software in mac80211/ath9k. Is it
> possible to change this value, e.g., using the AR_NAV?
AFAIK,
this register is hardware/software Read/Write
bits 0:25 for Current NAV value in micro seconds
good idea is to see the dump value of this register in ath9k debugfs
>
> Thank you for your help,
> Andr?s
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
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
1 sibling, 0 replies; 27+ messages in thread
From: Mohammed Shafi @ 2011-05-17 14:39 UTC (permalink / raw)
To: ath9k-devel
On Tue, May 17, 2011 at 6:59 PM, Sucheta ROY <sucheta.roy@st.com> wrote:
> Hi,
>
>
>
> Has anybody ever tried Message Signal Interrupt (MSI) enabling in any of
> Atheros PCIe-WiFi card driver under Linux? By default driver supports legacy
> interrupt.
its supported in Atheros cards, but its not there in ath9k.
>
>
>
> Regards,
>
> Sucheta
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
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
1 sibling, 1 reply; 27+ messages in thread
From: Mohammed Shafi @ 2011-05-17 14:41 UTC (permalink / raw)
To: ath9k-devel
On Tue, May 17, 2011 at 6:59 PM, Sucheta ROY <sucheta.roy@st.com> wrote:
> Hi,
>
>
>
> Has anybody ever tried Message Signal Interrupt (MSI) enabling in any of
> Atheros PCIe-WiFi card driver under Linux? By default driver supports legacy
> interrupt.
in reg.h
#define AR_PCIE_MSI (AR_SREV_9340(ah) ? 0x40d8 : \
(AR_SREV_9300_20_OR_LATER(ah) ? 0x40a4 : 0x4094))
#define AR_PCIE_MSI_ENABLE 0x00000001
bits 8:4 MSI Interrupt vector
but several things need to be addressed before enabling this interrupt
>
>
>
> Regards,
>
> Sucheta
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
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:45 ` Mohammed Shafi
0 siblings, 2 replies; 27+ messages in thread
From: Peter Stuge @ 2011-05-18 1:09 UTC (permalink / raw)
To: ath9k-devel
Mohammed Shafi wrote:
> bits 8:4 MSI Interrupt vector
Cool!
> but several things need to be addressed before enabling this interrupt
Which ones?
//Peter
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
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
2011-05-18 4:45 ` Mohammed Shafi
1 sibling, 2 replies; 27+ messages in thread
From: Adrian Chadd @ 2011-05-18 2:15 UTC (permalink / raw)
To: ath9k-devel
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
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
2011-05-18 2:15 ` Adrian Chadd
@ 2011-05-18 4:28 ` Sucheta ROY
2011-05-18 9:29 ` Sucheta ROY
1 sibling, 0 replies; 27+ messages in thread
From: Sucheta ROY @ 2011-05-18 4:28 UTC (permalink / raw)
To: ath9k-devel
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
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
2011-05-18 1:09 ` Peter Stuge
2011-05-18 2:15 ` Adrian Chadd
@ 2011-05-18 4:45 ` Mohammed Shafi
1 sibling, 0 replies; 27+ messages in thread
From: Mohammed Shafi @ 2011-05-18 4:45 UTC (permalink / raw)
To: ath9k-devel
On Wed, May 18, 2011 at 6:39 AM, 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?
I have not digged deep into this.
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
--
shafi
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
2011-05-18 2:15 ` Adrian Chadd
2011-05-18 4:28 ` Sucheta ROY
@ 2011-05-18 9:29 ` Sucheta ROY
2011-05-18 10:54 ` Senthilkumar Balasubramanian
1 sibling, 1 reply; 27+ messages in thread
From: Sucheta ROY @ 2011-05-18 9:29 UTC (permalink / raw)
To: ath9k-devel
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
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
2011-05-18 9:29 ` Sucheta ROY
@ 2011-05-18 10:54 ` Senthilkumar Balasubramanian
2011-05-19 0:32 ` Peter Stuge
0 siblings, 1 reply; 27+ messages in thread
From: Senthilkumar Balasubramanian @ 2011-05-18 10:54 UTC (permalink / raw)
To: ath9k-devel
On Wed, May 18, 2011 at 2:59 PM, Sucheta ROY <sucheta.roy@st.com> wrote:
> 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?
AR9285 doesn't support MSI and to answer your other question, MSI
should work AR9380. However ath9k lacks MSI support (some changes are
require in the driver also as you know)
>
> 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 at 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
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
2011-05-18 10:54 ` Senthilkumar Balasubramanian
@ 2011-05-19 0:32 ` Peter Stuge
2011-05-19 4:33 ` Sucheta ROY
0 siblings, 1 reply; 27+ messages in thread
From: Peter Stuge @ 2011-05-19 0:32 UTC (permalink / raw)
To: ath9k-devel
Senthilkumar Balasubramanian wrote:
> AR9285 doesn't support MSI
> MSI should work AR9380.
Awesome! Thanks for clear info!
> However ath9k lacks MSI support (some changes are require
What changes?
//Peter
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
2011-05-19 0:32 ` Peter Stuge
@ 2011-05-19 4:33 ` Sucheta ROY
2011-05-19 6:01 ` Alex Hacker
0 siblings, 1 reply; 27+ messages in thread
From: Sucheta ROY @ 2011-05-19 4:33 UTC (permalink / raw)
To: ath9k-devel
Hi,
I would like to know on what basis it is said AR9380 should work with MSI.I am aware that ath9K Linux driver does not support MSI by default. As you are suggesting that certain changes need to be incorporated in the driver. What all suggestion I received in previous mail I incorporated but could not make AR9285 work, although it exposes MSI capability structure and cat /proc/interrupts show pcie_msi interrupt in the table. So I am afraid whether the same would happen for AR9380!
If anybody is having that card, and can make a quick check by enabling MSI,that will be of great help. I don't have the card at this moment. If it is ensured that the card works with MSI I will plan to buy one.
Thanks and Regards,
Sucheta
-----Original Message-----
From: ath9k-devel-bounces@lists.ath9k.org [mailto:ath9k-devel-bounces at lists.ath9k.org] On Behalf Of Peter Stuge
Sent: Thursday, May 19, 2011 6:02 AM
To: ath9k-devel at lists.ath9k.org
Subject: Re: [ath9k-devel] AR9285 MSI
Senthilkumar Balasubramanian wrote:
> AR9285 doesn't support MSI
> MSI should work AR9380.
Awesome! Thanks for clear info!
> However ath9k lacks MSI support (some changes are require
What changes?
//Peter
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
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 8:41 ` [ath9k-devel] AR9285 MSI Sucheta ROY
0 siblings, 2 replies; 27+ messages in thread
From: Alex Hacker @ 2011-05-19 6:01 UTC (permalink / raw)
To: ath9k-devel
I have one currently installed on my PC, but do not have much time to
experimenting with MSI. If you tell me exactly what I should do to enable it
I'll report the results.
On Thu, May 19, 2011 at 12:33:29PM +0800, Sucheta ROY wrote:
> Hi,
>
> I would like to know on what basis it is said AR9380 should work with MSI.I am aware that ath9K Linux driver does not support MSI by default. As you are suggesting that certain changes need to be incorporated in the driver. What all suggestion I received in previous mail I incorporated but could not make AR9285 work, although it exposes MSI capability structure and cat /proc/interrupts show pcie_msi interrupt in the table. So I am afraid whether the same would happen for AR9380!
>
> If anybody is having that card, and can make a quick check by enabling MSI,that will be of great help. I don't have the card at this moment. If it is ensured that the card works with MSI I will plan to buy one.
>
> Thanks and Regards,
> Sucheta
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-05-19 6:01 ` Alex Hacker
@ 2011-05-19 8:35 ` Sucheta ROY
2011-05-19 11:06 ` Falk-Moritz Schaefer
2011-05-19 12:16 ` Alex Hacker
2011-05-19 8:41 ` [ath9k-devel] AR9285 MSI Sucheta ROY
1 sibling, 2 replies; 27+ messages in thread
From: Sucheta ROY @ 2011-05-19 8:35 UTC (permalink / raw)
To: ath9k-devel
Hi,
I believe you have AR9380 card installed in your PC?
You have to build your kernel with CONFIG_PCI_MSI option enabled. "CONFIG_PCI_MSI" Depends on: PCI [=y] && ARCH_SUPPORTS_MSI [=y]. Also you have to include
int pci_enable_msi(struct pci_dev *dev) function in pci.c file of ath9k. This function should be called before the driver calls request_irq().With a successful call the device will be switched from pin-based legacy interrupt mode to MSI mode. The dev->irq number will be changed to a new number which represents the message signaled interrupt.
Also can you please let me know PCI Vendor Id/Device Id of this card ie AR9380?
Thanks in advance for your support.
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, May 19, 2011 11:32 AM
To: ath9k-devel at venema.h4ckr.net
Subject: Re: [ath9k-devel] AR9285 MSI
I have one currently installed on my PC, but do not have much time to
experimenting with MSI. If you tell me exactly what I should do to enable it
I'll report the results.
On Thu, May 19, 2011 at 12:33:29PM +0800, Sucheta ROY wrote:
> Hi,
>
> I would like to know on what basis it is said AR9380 should work with MSI.I am aware that ath9K Linux driver does not support MSI by default. As you are suggesting that certain changes need to be incorporated in the driver. What all suggestion I received in previous mail I incorporated but could not make AR9285 work, although it exposes MSI capability structure and cat /proc/interrupts show pcie_msi interrupt in the table. So I am afraid whether the same would happen for AR9380!
>
> If anybody is having that card, and can make a quick check by enabling MSI,that will be of great help. I don't have the card at this moment. If it is ensured that the card works with MSI I will plan to buy one.
>
> Thanks and Regards,
> Sucheta
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9285 MSI
2011-05-19 6:01 ` Alex Hacker
2011-05-19 8:35 ` [ath9k-devel] AR9380 MSI Sucheta ROY
@ 2011-05-19 8:41 ` Sucheta ROY
1 sibling, 0 replies; 27+ messages in thread
From: Sucheta ROY @ 2011-05-19 8:41 UTC (permalink / raw)
To: ath9k-devel
Sorry did not receive the ack so sending it again!
Hi,
I believe you have AR9380 card installed in your PC?
You have to build your kernel with CONFIG_PCI_MSI option enabled. "CONFIG_PCI_MSI" Depends on: PCI [=y] && ARCH_SUPPORTS_MSI [=y]. Also you have to include int pci_enable_msi(struct pci_dev *dev) function in pci.c file of ath9k. This function should be called before the driver calls request_irq().With a successful call the device will be switched from pin-based legacy interrupt mode to MSI mode. The dev->irq number will be changed to a new number which represents the message signaled interrupt.
Also can you please let me know PCI Vendor Id/Device Id of this card ie AR9380?
Thanks in advance for your support.
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, May 19, 2011 11:32 AM
To: ath9k-devel at venema.h4ckr.net
Subject: Re: [ath9k-devel] AR9285 MSI
I have one currently installed on my PC, but do not have much time to
experimenting with MSI. If you tell me exactly what I should do to enable it
I'll report the results.
On Thu, May 19, 2011 at 12:33:29PM +0800, Sucheta ROY wrote:
> Hi,
>
> I would like to know on what basis it is said AR9380 should work with MSI.I am aware that ath9K Linux driver does not support MSI by default. As you are suggesting that certain changes need to be incorporated in the driver. What all suggestion I received in previous mail I incorporated but could not make AR9285 work, although it exposes MSI capability structure and cat /proc/interrupts show pcie_msi interrupt in the table. So I am afraid whether the same would happen for AR9380!
>
> If anybody is having that card, and can make a quick check by enabling MSI,that will be of great help. I don't have the card at this moment. If it is ensured that the card works with MSI I will plan to buy one.
>
> Thanks and Regards,
> Sucheta
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
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:16 ` Alex Hacker
1 sibling, 1 reply; 27+ messages in thread
From: Falk-Moritz Schaefer @ 2011-05-19 11:06 UTC (permalink / raw)
To: ath9k-devel
Hi,
I have an AR9382 card (SparkLAN WPEA-121N, 168c:3116 ) in an Lenovo R500
laptop. "pci_enable_msi" returns zero, and the card seems to work fine.
There are lspci outputs below. Hope that helps.
lspci output without "pci_enable_msi":
03:00.0 Network controller: Atheros Communications Inc. Device 0030 (rev 01)
Subsystem: Atheros Communications Inc. Device 3116
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=128K]
[virtual] Expansion ROM@7c400000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
Queue=0/2 Enable-
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <4us, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain-
CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: ath9k
Kernel modules: ath9k
Lspci with "pci_enable_msi":
03:00.0 Network controller: Atheros Communications Inc. Device 0030 (rev 01)
Subsystem: Atheros Communications Inc. Device 3116
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 33
Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=128K]
[virtual] Expansion ROM@7c400000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
Queue=0/2 Enable+
Address: 00000000fee0300c Data: 41d1
Masking: 0000000e Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <4us, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain-
CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: ath9k
Kernel modules: ath9k
> -----Original Message-----
> From: ath9k-devel-bounces at venema.h4ckr.net [mailto:ath9k-devel-
> bounces at venema.h4ckr.net] On Behalf Of Sucheta ROY
> Sent: Thursday, May 19, 2011 10:36 AM
> To: Alex Hacker; ath9k-devel at venema.h4ckr.net
> Subject: Re: [ath9k-devel] AR9380 MSI
>
> Hi,
>
> I believe you have AR9380 card installed in your PC?
>
> You have to build your kernel with CONFIG_PCI_MSI option enabled.
> "CONFIG_PCI_MSI" Depends on: PCI [=y] && ARCH_SUPPORTS_MSI [=y].
> Also you have to include int pci_enable_msi(struct pci_dev *dev) function
in
> pci.c file of ath9k. This function should be called before the driver
calls
> request_irq().With a successful call the device will be switched from pin-
> based legacy interrupt mode to MSI mode. The dev->irq number will be
> changed to a new number which represents the message signaled interrupt.
>
> Also can you please let me know PCI Vendor Id/Device Id of this card ie
> AR9380?
>
> Thanks in advance for your support.
>
> Regards,
> Sucheta
> -----Original Message-----
> From: ath9k-devel-bounces at lists.ath9k.org [mailto:ath9k-devel-
> bounces at lists.ath9k.org] On Behalf Of Alex Hacker
> Sent: Thursday, May 19, 2011 11:32 AM
> To: ath9k-devel at venema.h4ckr.net
> Subject: Re: [ath9k-devel] AR9285 MSI
>
> I have one currently installed on my PC, but do not have much time to
> experimenting with MSI. If you tell me exactly what I should do to enable
it
> I'll report the results.
>
> On Thu, May 19, 2011 at 12:33:29PM +0800, Sucheta ROY wrote:
> > Hi,
> >
> > I would like to know on what basis it is said AR9380 should work with
MSI.I
> am aware that ath9K Linux driver does not support MSI by default. As you
> are suggesting that certain changes need to be incorporated in the driver.
> What all suggestion I received in previous mail I incorporated but could
not
> make AR9285 work, although it exposes MSI capability structure and cat
> /proc/interrupts show pcie_msi interrupt in the table. So I am afraid
whether
> the same would happen for AR9380!
> >
> > If anybody is having that card, and can make a quick check by enabling
> MSI,that will be of great help. I don't have the card at this moment. If
it is
> ensured that the card works with MSI I will plan to buy one.
> >
> > Thanks and Regards,
> > Sucheta
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-05-19 11:06 ` Falk-Moritz Schaefer
@ 2011-05-19 12:02 ` Sucheta ROY
2011-05-19 12:32 ` Falk-Moritz Schaefer
0 siblings, 1 reply; 27+ messages in thread
From: Sucheta ROY @ 2011-05-19 12:02 UTC (permalink / raw)
To: ath9k-devel
Hi,
Thanks a lot for your efforts. It's great news for me.
After you enable "pci_enable_msi" have you checked cat /proc/interrupts? What does it show? And do you confirm that the WiFi card works successfully that is able to scan WiFi networks after MSI is enabled?
Also what all modifications you have done in the driver? Which version of Linux kernel your are using?
Thanks and Regards,
Sucheta
-----Original Message-----
From: Falk-Moritz Schaefer [mailto:falk.schaefer at tu-dortmund.de]
Sent: Thursday, May 19, 2011 4:36 PM
To: ath9k-devel at venema.h4ckr.net
Cc: Sucheta ROY
Subject: RE: [ath9k-devel] AR9380 MSI
Hi,
I have an AR9382 card (SparkLAN WPEA-121N, 168c:3116 ) in an Lenovo R500
laptop. "pci_enable_msi" returns zero, and the card seems to work fine.
There are lspci outputs below. Hope that helps.
lspci output without "pci_enable_msi":
03:00.0 Network controller: Atheros Communications Inc. Device 0030 (rev 01)
Subsystem: Atheros Communications Inc. Device 3116
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=128K]
[virtual] Expansion ROM@7c400000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
Queue=0/2 Enable-
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <4us, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain-
CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: ath9k
Kernel modules: ath9k
Lspci with "pci_enable_msi":
03:00.0 Network controller: Atheros Communications Inc. Device 0030 (rev 01)
Subsystem: Atheros Communications Inc. Device 3116
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 33
Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=128K]
[virtual] Expansion ROM@7c400000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
Queue=0/2 Enable+
Address: 00000000fee0300c Data: 41d1
Masking: 0000000e Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <4us, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain-
CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: ath9k
Kernel modules: ath9k
> -----Original Message-----
> From: ath9k-devel-bounces at venema.h4ckr.net [mailto:ath9k-devel-
> bounces at venema.h4ckr.net] On Behalf Of Sucheta ROY
> Sent: Thursday, May 19, 2011 10:36 AM
> To: Alex Hacker; ath9k-devel at venema.h4ckr.net
> Subject: Re: [ath9k-devel] AR9380 MSI
>
> Hi,
>
> I believe you have AR9380 card installed in your PC?
>
> You have to build your kernel with CONFIG_PCI_MSI option enabled.
> "CONFIG_PCI_MSI" Depends on: PCI [=y] && ARCH_SUPPORTS_MSI [=y].
> Also you have to include int pci_enable_msi(struct pci_dev *dev) function
in
> pci.c file of ath9k. This function should be called before the driver
calls
> request_irq().With a successful call the device will be switched from pin-
> based legacy interrupt mode to MSI mode. The dev->irq number will be
> changed to a new number which represents the message signaled interrupt.
>
> Also can you please let me know PCI Vendor Id/Device Id of this card ie
> AR9380?
>
> Thanks in advance for your support.
>
> Regards,
> Sucheta
> -----Original Message-----
> From: ath9k-devel-bounces at lists.ath9k.org [mailto:ath9k-devel-
> bounces at lists.ath9k.org] On Behalf Of Alex Hacker
> Sent: Thursday, May 19, 2011 11:32 AM
> To: ath9k-devel at venema.h4ckr.net
> Subject: Re: [ath9k-devel] AR9285 MSI
>
> I have one currently installed on my PC, but do not have much time to
> experimenting with MSI. If you tell me exactly what I should do to enable
it
> I'll report the results.
>
> On Thu, May 19, 2011 at 12:33:29PM +0800, Sucheta ROY wrote:
> > Hi,
> >
> > I would like to know on what basis it is said AR9380 should work with
MSI.I
> am aware that ath9K Linux driver does not support MSI by default. As you
> are suggesting that certain changes need to be incorporated in the driver.
> What all suggestion I received in previous mail I incorporated but could
not
> make AR9285 work, although it exposes MSI capability structure and cat
> /proc/interrupts show pcie_msi interrupt in the table. So I am afraid
whether
> the same would happen for AR9380!
> >
> > If anybody is having that card, and can make a quick check by enabling
> MSI,that will be of great help. I don't have the card at this moment. If
it is
> ensured that the card works with MSI I will plan to buy one.
> >
> > Thanks and Regards,
> > Sucheta
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-05-19 8:35 ` [ath9k-devel] AR9380 MSI Sucheta ROY
2011-05-19 11:06 ` Falk-Moritz Schaefer
@ 2011-05-19 12:16 ` Alex Hacker
2011-05-20 9:30 ` Sucheta ROY
1 sibling, 1 reply; 27+ messages in thread
From: Alex Hacker @ 2011-05-19 12:16 UTC (permalink / raw)
To: ath9k-devel
On Thu, May 19, 2011 at 04:35:59PM +0800, Sucheta ROY wrote:
> Hi,
>
> I believe you have AR9380 card installed in your PC?
>
> You have to build your kernel with CONFIG_PCI_MSI option enabled. "CONFIG_PCI_MSI" Depends on: PCI [=y] && ARCH_SUPPORTS_MSI [=y]. Also you have to include
> int pci_enable_msi(struct pci_dev *dev) function in pci.c file of ath9k. This function should be called before the driver calls request_irq().With a successful call the device will be switched from pin-based legacy interrupt mode to MSI mode. The dev->irq number will be changed to a new number which represents the message signaled interrupt.
>
> Also can you please let me know PCI Vendor Id/Device Id of this card ie AR9380?
>
> Thanks in advance for your support.
>
> Regards,
> Sucheta
The results I got below. If I do something wrong advise me what I should do.
--- pci.c.old 2011-05-19 17:59:59.000000000 +0600
+++ pci.c 2011-05-19 18:00:14.000000000 +0600
@@ -221,6 +221,9 @@
/* Will be cleared in ath9k_start() */
sc->sc_flags |= SC_OP_INVALID;
+printk("pci_enable_msi=%d.\n",pci_enable_msi(pdev));
+printk("pdev->irq=%d.\n",pdev->irq);
+
ret = request_irq(pdev->irq, ath_isr, IRQF_SHARED, "ath9k", sc);
if (ret) {
# cat /proc/interrupts
dev_err(&pdev->dev, "request_irq failed\n");
CPU0 CPU1
0: 393 2628 IO-APIC-edge timer
1: 35884 676360 IO-APIC-edge i8042
4: 45 262178 IO-APIC-edge serial
8: 1 0 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
14: 0 0 IO-APIC-edge ata_piix
15: 0 0 IO-APIC-edge ata_piix
16: 30197 110785854 IO-APIC-fasteoi uhci_hcd:usb5
18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
19: 173216 10744489 IO-APIC-fasteoi ata_piix, uhci_hcd:usb3
20: 191379417 133 IO-APIC-fasteoi eth0
23: 776135 27633305 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
42: 0 0 PCI-MSI-edge ath9k
NMI: 0 0 Non-maskable interrupts
LOC: 527052638 535023710 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
IWI: 0 0 IRQ work interrupts
RES: 3026801 3065734 Rescheduling interrupts
CAL: 14585 15117 Function call interrupts
TLB: 78368 128713 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 2981 2981 Machine check polls
ERR: 1
MIS: 0
# lspci -vvn
02:00.0 Class 0280: 168c:0030 (rev 01)
Subsystem: 168c:3112
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 08
Interrupt: pin A routed to IRQ 42
Region 0: Memory at feae0000 (64-bit, non-prefetchable) [size=128K]
Expansion ROM@fead0000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/2 Enable+
Address: 00000000fee0300c Data: 4179
Capabilities: [70] #10 [0002]
# modprobe ath9k
# iw dev wlan0 set freq 5240
# iw dev wlan0 set monitor none
# ifconfig wlan0 up
# dmesg
May 19 17:51:00 hacker kernel: ath9k 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
May 19 17:51:00 hacker kernel: ath9k 0000:02:00.0: setting latency timer to 64
May 19 17:51:00 hacker kernel: ath9k 0000:02:00.0: irq 42 for MSI/MSI-X
May 19 17:51:00 hacker kernel: pci_enable_msi=0.
May 19 17:51:00 hacker kernel: pdev->irq=42.
May 19 17:51:00 hacker kernel: ath: EEPROM regdomain: 0x0
May 19 17:51:00 hacker kernel: ath: EEPROM indicates default country code should be used
May 19 17:51:00 hacker kernel: ath: doing EEPROM country->regdmn map search
May 19 17:51:00 hacker kernel: ath: country maps to regdmn code: 0x3a
May 19 17:51:00 hacker kernel: ath: Country alpha2 being used: US
May 19 17:51:00 hacker kernel: ath: Regpair used: 0x3a
May 19 17:51:00 hacker kernel: ieee80211 phy1: Selected rate control algorithm 'ath9k_rate_control'
May 19 17:51:00 hacker kernel: Registered led device: ath9k-phy1::radio
May 19 17:51:00 hacker kernel: Registered led device: ath9k-phy1::assoc
May 19 17:51:00 hacker kernel: Registered led device: ath9k-phy1::tx
May 19 17:51:00 hacker kernel: Registered led device: ath9k-phy1::rx
May 19 17:51:00 hacker kernel: ieee80211 phy1: Atheros AR9300 Rev:3 mem=0xf8640000, irq=42
May 19 17:53:59 hacker kernel: do_IRQ: 0.120 No irq handler for vector (irq -1)
May 19 17:53:59 hacker kernel: do_IRQ: 1.120 No irq handler for vector (irq -1)
May 19 17:53:59 hacker kernel: do_IRQ: 1.120 No irq handler for vector (irq -1)
May 19 17:54:06 hacker kernel: device wlan0 entered promiscuous mode
Does not work.
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-05-19 12:02 ` Sucheta ROY
@ 2011-05-19 12:32 ` Falk-Moritz Schaefer
0 siblings, 0 replies; 27+ messages in thread
From: Falk-Moritz Schaefer @ 2011-05-19 12:32 UTC (permalink / raw)
To: ath9k-devel
Sorry, seems like Alex is right. As you suspected scanning does not work and
dmesg shows "No irq handler for vector (irq -1)" messages.
> -----Original Message-----
> From: Sucheta ROY [mailto:sucheta.roy at st.com]
> Sent: Thursday, May 19, 2011 2:03 PM
> To: Falk-Moritz Schaefer; ath9k-devel at venema.h4ckr.net
> Subject: RE: [ath9k-devel] AR9380 MSI
>
> Hi,
>
> Thanks a lot for your efforts. It's great news for me.
> After you enable "pci_enable_msi" have you checked cat /proc/interrupts?
> What does it show? And do you confirm that the WiFi card works
successfully
> that is able to scan WiFi networks after MSI is enabled?
>
> Also what all modifications you have done in the driver? Which version of
> Linux kernel your are using?
>
> Thanks and Regards,
> Sucheta
>
> -----Original Message-----
> From: Falk-Moritz Schaefer [mailto:falk.schaefer at tu-dortmund.de]
> Sent: Thursday, May 19, 2011 4:36 PM
> To: ath9k-devel at venema.h4ckr.net
> Cc: Sucheta ROY
> Subject: RE: [ath9k-devel] AR9380 MSI
>
> Hi,
>
> I have an AR9382 card (SparkLAN WPEA-121N, 168c:3116 ) in an Lenovo R500
> laptop. "pci_enable_msi" returns zero, and the card seems to work fine.
> There are lspci outputs below. Hope that helps.
>
> lspci output without "pci_enable_msi":
> 03:00.0 Network controller: Atheros Communications Inc. Device 0030 (rev
> 01)
> Subsystem: Atheros Communications Inc. Device 3116
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 17
> Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=128K]
> [virtual] Expansion ROM at 7c400000 [disabled] [size=64K]
> Capabilities: [40] Power Management version 3
> Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
> PME(D0+,D1+,D2-,D3hot+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
> Queue=0/2 Enable-
> Address: 0000000000000000 Data: 0000
> Masking: 00000000 Pending: 00000000
> Capabilities: [70] Express (v2) Endpoint, MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency
> L0s
> unlimited, L1 <64us
> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
> MaxPayload 128 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+
> AuxPwr-
> TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s
> L1,
> Latency L0 <4us, L1 <64us
> ClockPM- Suprise- LLActRep- BwNot-
> LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain-
> CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMgmt-
> Capabilities: [100] Advanced Error Reporting <?>
> Capabilities: [140] Virtual Channel <?>
> Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00
> Kernel driver in use: ath9k
> Kernel modules: ath9k
>
> Lspci with "pci_enable_msi":
> 03:00.0 Network controller: Atheros Communications Inc. Device 0030 (rev
> 01)
> Subsystem: Atheros Communications Inc. Device 3116
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 33
> Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=128K]
> [virtual] Expansion ROM at 7c400000 [disabled] [size=64K]
> Capabilities: [40] Power Management version 3
> Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
> PME(D0+,D1+,D2-,D3hot+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
> Queue=0/2 Enable+
> Address: 00000000fee0300c Data: 41d1
> Masking: 0000000e Pending: 00000000
> Capabilities: [70] Express (v2) Endpoint, MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency
> L0s
> unlimited, L1 <64us
> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
> MaxPayload 128 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+
> AuxPwr-
> TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s
> L1,
> Latency L0 <4us, L1 <64us
> ClockPM- Suprise- LLActRep- BwNot-
> LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain-
> CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMgmt-
> Capabilities: [100] Advanced Error Reporting <?>
> Capabilities: [140] Virtual Channel <?>
> Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00
> Kernel driver in use: ath9k
> Kernel modules: ath9k
>
>
> > -----Original Message-----
> > From: ath9k-devel-bounces at venema.h4ckr.net [mailto:ath9k-devel-
> > bounces at venema.h4ckr.net] On Behalf Of Sucheta ROY
> > Sent: Thursday, May 19, 2011 10:36 AM
> > To: Alex Hacker; ath9k-devel at venema.h4ckr.net
> > Subject: Re: [ath9k-devel] AR9380 MSI
> >
> > Hi,
> >
> > I believe you have AR9380 card installed in your PC?
> >
> > You have to build your kernel with CONFIG_PCI_MSI option enabled.
> > "CONFIG_PCI_MSI" Depends on: PCI [=y] && ARCH_SUPPORTS_MSI [=y].
> > Also you have to include int pci_enable_msi(struct pci_dev *dev)
> > function
> in
> > pci.c file of ath9k. This function should be called before the driver
> calls
> > request_irq().With a successful call the device will be switched from
> > pin- based legacy interrupt mode to MSI mode. The dev->irq number
> > will be changed to a new number which represents the message signaled
> interrupt.
> >
> > Also can you please let me know PCI Vendor Id/Device Id of this card
> > ie AR9380?
> >
> > Thanks in advance for your support.
> >
> > Regards,
> > Sucheta
> > -----Original Message-----
> > From: ath9k-devel-bounces at lists.ath9k.org [mailto:ath9k-devel-
> > bounces at lists.ath9k.org] On Behalf Of Alex Hacker
> > Sent: Thursday, May 19, 2011 11:32 AM
> > To: ath9k-devel at venema.h4ckr.net
> > Subject: Re: [ath9k-devel] AR9285 MSI
> >
> > I have one currently installed on my PC, but do not have much time to
> > experimenting with MSI. If you tell me exactly what I should do to
> > enable
> it
> > I'll report the results.
> >
> > On Thu, May 19, 2011 at 12:33:29PM +0800, Sucheta ROY wrote:
> > > Hi,
> > >
> > > I would like to know on what basis it is said AR9380 should work
> > > with
> MSI.I
> > am aware that ath9K Linux driver does not support MSI by default. As
> > you are suggesting that certain changes need to be incorporated in the
> driver.
> > What all suggestion I received in previous mail I incorporated but
> > could
> not
> > make AR9285 work, although it exposes MSI capability structure and cat
> > /proc/interrupts show pcie_msi interrupt in the table. So I am afraid
> whether
> > the same would happen for AR9380!
> > >
> > > If anybody is having that card, and can make a quick check by
> > > enabling
> > MSI,that will be of great help. I don't have the card at this moment.
> > If
> it is
> > ensured that the card works with MSI I will plan to buy one.
> > >
> > > Thanks and Regards,
> > > Sucheta
> > _______________________________________________
> > ath9k-devel mailing list
> > ath9k-devel at lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> > _______________________________________________
> > ath9k-devel mailing list
> > ath9k-devel at lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-05-19 12:16 ` Alex Hacker
@ 2011-05-20 9:30 ` Sucheta ROY
2011-05-20 10:15 ` Alex Hacker
0 siblings, 1 reply; 27+ messages in thread
From: Sucheta ROY @ 2011-05-20 9:30 UTC (permalink / raw)
To: ath9k-devel
Hi,
Whatever you have done looks OK to me. Can you please let me know:
1. #define AR_PCIE_MSI and #define AR_PCIE_MSI_ENABLE part in reg.h file.
2. lspci -xxx capture.
Also from PCI Vendor ID/Device Id, I see you have AR9300 in your PC instead of AR9380.
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, May 19, 2011 5:47 PM
To: ath9k-devel at venema.h4ckr.net
Subject: Re: [ath9k-devel] AR9380 MSI
On Thu, May 19, 2011 at 04:35:59PM +0800, Sucheta ROY wrote:
> Hi,
>
> I believe you have AR9380 card installed in your PC?
>
> You have to build your kernel with CONFIG_PCI_MSI option enabled. "CONFIG_PCI_MSI" Depends on: PCI [=y] && ARCH_SUPPORTS_MSI [=y]. Also you have to include
> int pci_enable_msi(struct pci_dev *dev) function in pci.c file of ath9k. This function should be called before the driver calls request_irq().With a successful call the device will be switched from pin-based legacy interrupt mode to MSI mode. The dev->irq number will be changed to a new number which represents the message signaled interrupt.
>
> Also can you please let me know PCI Vendor Id/Device Id of this card ie AR9380?
>
> Thanks in advance for your support.
>
> Regards,
> Sucheta
The results I got below. If I do something wrong advise me what I should do.
--- pci.c.old 2011-05-19 17:59:59.000000000 +0600
+++ pci.c 2011-05-19 18:00:14.000000000 +0600
@@ -221,6 +221,9 @@
/* Will be cleared in ath9k_start() */
sc->sc_flags |= SC_OP_INVALID;
+printk("pci_enable_msi=%d.\n",pci_enable_msi(pdev));
+printk("pdev->irq=%d.\n",pdev->irq);
+
ret = request_irq(pdev->irq, ath_isr, IRQF_SHARED, "ath9k", sc);
if (ret) {
# cat /proc/interrupts
dev_err(&pdev->dev, "request_irq failed\n");
CPU0 CPU1
0: 393 2628 IO-APIC-edge timer
1: 35884 676360 IO-APIC-edge i8042
4: 45 262178 IO-APIC-edge serial
8: 1 0 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
14: 0 0 IO-APIC-edge ata_piix
15: 0 0 IO-APIC-edge ata_piix
16: 30197 110785854 IO-APIC-fasteoi uhci_hcd:usb5
18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
19: 173216 10744489 IO-APIC-fasteoi ata_piix, uhci_hcd:usb3
20: 191379417 133 IO-APIC-fasteoi eth0
23: 776135 27633305 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
42: 0 0 PCI-MSI-edge ath9k
NMI: 0 0 Non-maskable interrupts
LOC: 527052638 535023710 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
IWI: 0 0 IRQ work interrupts
RES: 3026801 3065734 Rescheduling interrupts
CAL: 14585 15117 Function call interrupts
TLB: 78368 128713 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 2981 2981 Machine check polls
ERR: 1
MIS: 0
# lspci -vvn
02:00.0 Class 0280: 168c:0030 (rev 01)
Subsystem: 168c:3112
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, cache line size 08
Interrupt: pin A routed to IRQ 42
Region 0: Memory at feae0000 (64-bit, non-prefetchable) [size=128K]
Expansion ROM@fead0000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/2 Enable+
Address: 00000000fee0300c Data: 4179
Capabilities: [70] #10 [0002]
# modprobe ath9k
# iw dev wlan0 set freq 5240
# iw dev wlan0 set monitor none
# ifconfig wlan0 up
# dmesg
May 19 17:51:00 hacker kernel: ath9k 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
May 19 17:51:00 hacker kernel: ath9k 0000:02:00.0: setting latency timer to 64
May 19 17:51:00 hacker kernel: ath9k 0000:02:00.0: irq 42 for MSI/MSI-X
May 19 17:51:00 hacker kernel: pci_enable_msi=0.
May 19 17:51:00 hacker kernel: pdev->irq=42.
May 19 17:51:00 hacker kernel: ath: EEPROM regdomain: 0x0
May 19 17:51:00 hacker kernel: ath: EEPROM indicates default country code should be used
May 19 17:51:00 hacker kernel: ath: doing EEPROM country->regdmn map search
May 19 17:51:00 hacker kernel: ath: country maps to regdmn code: 0x3a
May 19 17:51:00 hacker kernel: ath: Country alpha2 being used: US
May 19 17:51:00 hacker kernel: ath: Regpair used: 0x3a
May 19 17:51:00 hacker kernel: ieee80211 phy1: Selected rate control algorithm 'ath9k_rate_control'
May 19 17:51:00 hacker kernel: Registered led device: ath9k-phy1::radio
May 19 17:51:00 hacker kernel: Registered led device: ath9k-phy1::assoc
May 19 17:51:00 hacker kernel: Registered led device: ath9k-phy1::tx
May 19 17:51:00 hacker kernel: Registered led device: ath9k-phy1::rx
May 19 17:51:00 hacker kernel: ieee80211 phy1: Atheros AR9300 Rev:3 mem=0xf8640000, irq=42
May 19 17:53:59 hacker kernel: do_IRQ: 0.120 No irq handler for vector (irq -1)
May 19 17:53:59 hacker kernel: do_IRQ: 1.120 No irq handler for vector (irq -1)
May 19 17:53:59 hacker kernel: do_IRQ: 1.120 No irq handler for vector (irq -1)
May 19 17:54:06 hacker kernel: device wlan0 entered promiscuous mode
Does not work.
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-05-20 9:30 ` Sucheta ROY
@ 2011-05-20 10:15 ` Alex Hacker
0 siblings, 0 replies; 27+ messages in thread
From: Alex Hacker @ 2011-05-20 10:15 UTC (permalink / raw)
To: ath9k-devel
Hello,
On Fri, May 20, 2011 at 05:30:27PM +0800, Sucheta ROY wrote:
> Hi,
>
> Whatever you have done looks OK to me. Can you please let me know:
> 1. #define AR_PCIE_MSI and #define AR_PCIE_MSI_ENABLE part in reg.h file.
#define AR_PCIE_MSI (AR_SREV_9300_20_OR_LATER(ah) ? 0x40a4 : 0x4094)
#define AR_PCIE_MSI_ENABLE 0x00000001
The kernel version is 2.6.38.4.
> 2. lspci -xxx capture.
02:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN adaptor (rev 01)
00: 8c 16 30 00 03 04 10 00 01 00 80 02 08 00 00 00
10: 04 00 ae fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 8c 16 12 31
30: 00 00 ad fe 40 00 00 00 00 00 00 00 0a 01 00 00
40: 01 50 c3 5b 00 00 00 00 00 00 00 00 00 00 00 00
50: 05 70 85 01 0c 30 e0 fe 00 00 00 00 79 41 00 00
60: 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 10 00 02 00 00 87 28 00 10 20 09 00 11 5c 03 00
80: 40 00 11 10 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Also from PCI Vendor ID/Device Id, I see you have AR9300 in your PC instead of AR9380.
In my imagination it the same. Actually AR9380 Rev 2.2 is the first
commercially available MIMO 3x3 chip. Or I'm be quite wrong?
By the way, after loading the modified driver I reverse changes and install
original driver module, but it does not work with same error. MSI in PCI
is still enabled and I should to reboot my PC to have it back again.
> Regards,
> Sucheta
With best regards to you too,
Alex.
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] setting AR_NAV register
2011-05-17 14:27 ` [ath9k-devel] setting AR_NAV register Mohammed Shafi
@ 2011-08-09 12:37 ` Manuel Sáez
0 siblings, 0 replies; 27+ messages in thread
From: Manuel Sáez @ 2011-08-09 12:37 UTC (permalink / raw)
To: ath9k-devel
El d?a 17 de mayo de 2011 16:27, Mohammed Shafi
<shafi.wireless@gmail.com> escribi?:
> 2011/5/17 Andr?s Garc?a Saavedra <andres.garcia.saavedra@gmail.com>:
>> Dear all,
>>
>> I would like to set the NAV value from software in mac80211/ath9k. Is it
>> possible to change this value, e.g., using the AR_NAV?
>
> AFAIK,
> this register is hardware/software Read/Write
> bits 0:25 for Current NAV value in micro seconds
> good idea is to see the dump value of this register in ath9k debugfs
I have just test this and works quite fine. In case this helps someone:
REG_WRITE(ah, AR_NAV, TU_TO_USEC(value_tu));
Afterwards the hardware start decrementing the value until it reaches
0. During this time it stops the queues.
Thank you!
>
>>
>> Thank you for your help,
>> Andr?s
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-07-01 9:38 ` Sucheta ROY
@ 2011-07-01 10:18 ` Matevz Langus
0 siblings, 0 replies; 27+ messages in thread
From: Matevz Langus @ 2011-07-01 10:18 UTC (permalink / raw)
To: ath9k-devel
Hi,
I can also give back some info, might be interesting for someone. I tried AR9382 and enabled MSI and got some results of WiFi scan (but not all networks were found). The number of interrupts per scan in the same environment was much smaller than the number when using legacy INTa over PCIE. So my conclusion is MSI works but not good enough. I believe there should be some setting required in the chip to switch to MSI or something like that.
Regards,
Matevz
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-06-30 4:50 Alex Hacker
@ 2011-07-01 9:38 ` Sucheta ROY
2011-07-01 10:18 ` Matevz Langus
0 siblings, 1 reply; 27+ messages in thread
From: Sucheta ROY @ 2011-07-01 9:38 UTC (permalink / raw)
To: ath9k-devel
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
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
@ 2011-06-30 4:50 Alex Hacker
2011-07-01 9:38 ` Sucheta ROY
0 siblings, 1 reply; 27+ messages in thread
From: Alex Hacker @ 2011-06-30 4:50 UTC (permalink / raw)
To: ath9k-devel
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
^ permalink raw reply [flat|nested] 27+ messages in thread
* [ath9k-devel] AR9380 MSI
2011-06-29 17:15 ` Adrian Chadd
@ 2011-06-29 18:56 ` Matevz Langus
0 siblings, 0 replies; 27+ messages in thread
From: Matevz Langus @ 2011-06-29 18:56 UTC (permalink / raw)
To: ath9k-devel
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
^ permalink raw reply [flat|nested] 27+ messages in thread
end of thread, other threads:[~2011-08-09 12:37 UTC | newest]
Thread overview: 27+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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-06-30 4:50 Alex Hacker
2011-07-01 9:38 ` Sucheta ROY
2011-07-01 10:18 ` Matevz Langus
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.