qca99x0 don't work with MSI-X supported/enabled

qca99x0 don't work with MSI-X supported/enabled

[Janusz Dziedzic]

Hello,

Seems in case of qca99x0 we request

.msi_assign_ce_max              = 12

Next in case PC support MSI-X we fail when registering CE interrupts
with error msg:
ath10k_pci 0000:04:00.0: failed to request MSI-X ce irq 50: -22


Seems my linux limit max MSI-X to 8, so we should not request irq per CE?
BTW are CE8 .. CE11 used by the driver ? Or we can setup msi_assign_ce_max = 7?

Works fine when single MSI-X or legacy interrupt forced.

BR
Janusz

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: qca99x0 don't work with MSI-X supported/enabled

[Vasanthakumar Thiagarajan]

On Wednesday 16 September 2015 01:24 PM, Janusz Dziedzic wrote:
> Hello,
>
> Seems in case of qca99x0 we request
>
> .msi_assign_ce_max              = 12
>
> Next in case PC support MSI-X we fail when registering CE interrupts
> with error msg:
> ath10k_pci 0000:04:00.0: failed to request MSI-X ce irq 50: -22
>
>
> Seems my linux limit max MSI-X to 8, so we should not request irq per CE?
> BTW are CE8 .. CE11 used by the driver ? Or we can setup msi_assign_ce_max = 7?

CE8 is used by the driver to get pktlog information. Currently we are using
7 CEs actively. When copy engine fast path to skip htc layer is added, CE5
will also be used, so it is going to be 8 active CEs. If this would fail
for MSI-X, may be we need to disable MSI-X for qca99x0?.

Vasanth

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k