input: goodix: Fix wrongly placed mutex unlock

Xiaomeme added a condition that can keep on iteration over modules
however left mutex unlock before it. This can cause premature mutex
unlock and double-unlock afterwards which leads to undefined behavior.

Mutex unlock should be called only when taking out path.

Signed-off-by: Andrzej Perczak <linux@andrzejperczak.com>
Signed-off-by: onettboots <blackcocopet@gmail.com>

Author: xNombre

drivers/input/touchscreen/goodix_driver_gt9886/goodix_ts_core.c

@@ -1757,13 +1757,14 @@ int goodix_ts_suspend(struct goodix_ts_core *core_data)
 				} else if (core_data->udfps_enabled) {
 					atomic_set(&core_data->suspend_stat, TP_GESTURE_FOD);
 				}
-				mutex_unlock(&goodix_modules.mutex);
 				ts_info("suspend_stat[%d]", atomic_read(&core_data->suspend_stat));
 				ts_info("Canceled by module:%s", ext_module->name);
-				if (!atomic_read(&core_data->suspend_stat))
+				if (!atomic_read(&core_data->suspend_stat)) {
 					ts_info("go suspend remaind work\n");
-				else
+				} else {
+					mutex_unlock(&goodix_modules.mutex);
 					goto out;
+				}
 			}
 		}
 	}