fcc220e1c2
Due to the scheduling delay, We are seeing back to back two top half for buff done for 2 different requests but we were expecting the bottom half after 1st top half. We update the last consumed address in the bottom half so we have 2nd req buffer address in last consumed reg as we received 2nd req top half before 1st req bottom half. We increment num_ack variable of 2nd request in case of 1st req buff-done as it had 2nd buffer address in last consumed address. Ack is going beyond during the 2nd req buff-done. This check will prevent duplicate acknowledgment increment. CRs-Fixed: 3165255 Change-Id: I9ea3bca2a782bae6017565f30162484adf2fc789 Signed-off-by: Chandan Kumar Jha <quic_cjha@quicinc.com>