Anyone seeing tx-credits 'hang'?

Michal Kazior michal.kazior at
Wed Jan 14 01:45:14 PST 2015

On 13 January 2015 at 20:07, Ben Greear <greearb at> wrote:
> I managed to get some better debug out of the firmware.
> I am having a hell of a time figuring out how the code flows through all
> of the callbacks (in both firmware and driver), but it appears this is what happened:
> (I have instrumented transfer-id in both firmware and driver)
> firmware sent wmi message with transfer-id of 72.
> kernel received this transfer-id
> firmware's last send-callback transfer ID is 71.
> So, it seems that either ath10k did not do the transfer-complete logic,
> did it incorrectly, or the firmware did not notice it was done.
> I cannot find where the transfer complete code that should be updating
> firmware is at.  If you know, can you point me to it?

I think the send-callback should be called when CE is simply done
doing it's stuff. There's no need for the other side to ack anything
explicitly (it just needs to have a free buffer on it's side so CE can
copy it over).

Or maybe it is the HOST_IS_COPY_COMPLETE_MASK? Not really sure.


More information about the ath10k mailing list