Blame SOURCES/0099-synaptics-Fix-problem-after-match-is-failed.patch

73b847
From 55f1d4b575cd881f61f6e0cc20e468a16ae276f9 Mon Sep 17 00:00:00 2001
73b847
From: Vincent Huang <vincent.huang@tw.synaptics.com>
73b847
Date: Mon, 9 Dec 2019 14:12:54 +0800
73b847
Subject: [PATCH 099/181] synaptics: Fix problem after match is failed
73b847
73b847
This fixes the the problem that the sensor becomes unresponsive after
73b847
pressing the wrong fingerprint. We fix the problem by making sure that
73b847
the non-match report is delayed until the finger is removed. With this
73b847
we cannot run into the situation that the next match request fails
73b847
immediately as the finger is still present.
73b847
73b847
Fixes: #208
73b847
---
73b847
 libfprint/drivers/synaptics/synaptics.c | 2 +-
73b847
 1 file changed, 1 insertion(+), 1 deletion(-)
73b847
73b847
diff --git a/libfprint/drivers/synaptics/synaptics.c b/libfprint/drivers/synaptics/synaptics.c
73b847
index 247b658..6ed6791 100644
73b847
--- a/libfprint/drivers/synaptics/synaptics.c
73b847
+++ b/libfprint/drivers/synaptics/synaptics.c
73b847
@@ -168,7 +168,7 @@ cmd_recieve_cb (FpiUsbTransfer *transfer,
73b847
    * depending on resp.complete. */
73b847
   if (self->cmd_pending_transfer)
73b847
     fpi_ssm_jump_to_state (transfer->ssm, SYNAPTICS_CMD_SEND_PENDING);
73b847
-  else if (!resp.complete)
73b847
+  else if (!resp.complete || self->cmd_complete_on_removal)
73b847
     fpi_ssm_next_state (transfer->ssm);             /* SYNAPTICS_CMD_WAIT_INTERRUPT */
73b847
   else
73b847
     fpi_ssm_mark_completed (transfer->ssm);
73b847
-- 
73b847
2.24.1
73b847