samsung-sm8650/android_kernel_samsung_sm8650-modules
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

video: driver: fix buffer tracking logic at reverse path

Browse Source 
fw sent FBD with RO and host didn't requeue same buffer again,
but firmware still holds RO reference. In that case, if stop
cmd issued at output port, firmware will FBD once again w/o
RO. So at that time wrong buffer will be picked from list, if
tracking is based on index.

To handle that special case, for decoder alone using device
addr & data_offset for identifying the node in reverse path.

Change-Id: I3d8cb0b4b100fd44be30e576ae602950650747a4
Signed-off-by: Govindaraj Rajagopal <grajagop@codeaurora.org>
This commit is contained in:
Govindaraj Rajagopal
2021-04-09 11:38:25 +05:30
parent 1b42ed0a67
commit 58ce6211a7
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
driver/vidc/src/venus_hfi_response.c
View File

@@ -613,10 +613,14 @@ static int handle_output_buffer(struct msm_vidc_inst *inst,
found = false;
list_for_each_entry(buf, &buffers->list, list) {
if (buf->index == buffer->index) {
found = true;
if (is_decode_session(inst))
found = (buf->device_addr == buffer->base_address &&
buf->data_offset == buffer->data_offset);
else
found = (buf->index == buffer->index);
if (found)
break;
}
}
if (!found) {
i_vpr_e(inst, "%s: invalid idx %d daddr %#x data_offset %d\n",