> -----Original Message-----
> From: Toke Høiland-Jørgensen <[email protected]>
> Sent: Wednesday, August 21, 2019 6:10 PM
> To: Wen Gong <[email protected]>; Wen Gong
> <[email protected]>; [email protected]
> Cc: [email protected]
> Subject: [EXT] RE: [PATCH 4/7] ath10k: disable TX complete indication of htt
> for sdio
>
> Wen Gong <[email protected]> writes:
>
> >> -----Original Message-----
> >> From: ath10k <[email protected]> On Behalf Of Toke
> >> Høiland-Jørgensen
> >> Sent: Tuesday, August 20, 2019 8:24 PM
> >> To: Wen Gong <[email protected]>; [email protected]
> >> Cc: [email protected]
> >> Subject: [EXT] Re: [PATCH 4/7] ath10k: disable TX complete indication of
> htt
> > When this patch applied, firmware will not indicate tx complete for tx
> > Data, it only indicate HTT_T2H_MSG_TYPE_TX_CREDIT_UPDATE_IND,
> > This htt msg will tell how many data tx complete without status(status
> maybe success/fail).
>
> Ah, so this is basically a counter of how much data is currently queued
> in the firmware?
Yes.
>
> >> And could you explain what the credits thing is for, please? :)
> > For high latency bus chip, all the tx data's content(include ip/udp/tcp
> header
> > and payload) will be transfer to firmware's memory via bus.
> > And firmware has limited memory for tx data, the tx data's content must
> > Saved in firmware memory before it tx complete, if ath10k transfer tx
> > data more than the limit, firmware will occur error. The credit is used
> > to avoid ath10k exceed the limit.
>
> What's a typical limit in the firmware?
It is 96 data packet in my test. It can changed in firmware code.
>
> -Toke
