ACPI: EC: Rearrange the loop in acpi_ec_event_handler()

It is not necessary to check ec->nr_pending_queries against 0 in the
while () loop in acpi_ec_event_handler(), because that loop terminates
when ec->nr_pending_queries is 0 and the code depending on that can be
run after the loop has ended.

Modify the code accordingly and while at it rewrite the comment
regarding that code to make it clearer.

No intentional functional impact.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
index 07506afa1fdab29de4160931d1673592fdbde589..7582ef59b81f5d6e48d4a6900a09ec2a6c45f243 100644 (file)
--- a/drivers/acpi/ec.c
+++ b/drivers/acpi/ec.c
@@ -1230,18 +1230,17 @@ static void acpi_ec_event_handler(struct work_struct *work)
 
                spin_lock_irqsave(&ec->lock, flags);
                ec->nr_pending_queries--;
-               /*
-                * Before exit, make sure that this work item can be
-                * scheduled again. There might be QR_EC failures, leaving
-                * EC_FLAGS_QUERY_PENDING uncleared and preventing this work
-                * item from being scheduled again.
-                */
-               if (!ec->nr_pending_queries) {
-                       if (ec_event_clearing == ACPI_EC_EVT_TIMING_STATUS ||
-                           ec_event_clearing == ACPI_EC_EVT_TIMING_QUERY)
-                               acpi_ec_complete_query(ec);
-               }
        }
+
+       /*
+        * Before exit, make sure that the it will be possible to queue up the
+        * event handling work again regardless of whether or not the query
+        * queued up above is processed successfully.
+        */
+       if (ec_event_clearing == ACPI_EC_EVT_TIMING_STATUS ||
+           ec_event_clearing == ACPI_EC_EVT_TIMING_QUERY)
+               acpi_ec_complete_query(ec);
+
        spin_unlock_irqrestore(&ec->lock, flags);
 
        ec_dbg_evt("Event stopped");