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

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