msm: camera: isp: Remove bubble re-apply recovery mechanism
If a request has been applied the buffer addresses have been configured, and if a frame bubbles buf done is expected on the same frame or in the worse case on the next frame. SW should not try adding a bubbled request back to pending list without a buf done for that request. CRs-Fixed: 2729789 Change-Id: I9a2f45c58d39b659cd7a12747dc738c43cf5e0ad Signed-off-by: Karthik Anantha Ram <kartanan@codeaurora.org>
This commit is contained in:
@@ -226,7 +226,6 @@ struct cam_isp_context_event_record {
|
||||
* @substate_actiavted: Current substate for the activated state.
|
||||
* @process_bubble: Atomic variable to check if ctx is still
|
||||
* processing bubble.
|
||||
* @bubble_frame_cnt: Count number of frames since the req is in bubble
|
||||
* @substate_machine: ISP substate machine for external interface
|
||||
* @substate_machine_irq: ISP substate machine for irq handling
|
||||
* @req_base: Common request object storage
|
||||
@@ -267,7 +266,6 @@ struct cam_isp_context {
|
||||
uint32_t frame_id_meta;
|
||||
uint32_t substate_activated;
|
||||
atomic_t process_bubble;
|
||||
uint32_t bubble_frame_cnt;
|
||||
struct cam_ctx_ops *substate_machine;
|
||||
struct cam_isp_ctx_irq_ops *substate_machine_irq;
|
||||
|
||||
|
Reference in New Issue
Block a user