ACPICA: hw: remove use_lock flag from acpi_hw_register_{read, write}

use_lock flag is used once for acpi_hw_register_read, and never for
acpi_hw_register_write. It will greatly simplify understanding of
locking if we just drop this use_lock altogether, and wrap the only call
to ..._read in lock/unlock.

Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de>
Signed-off-by: Len Brown <len.brown@intel.com>

1 files changed, 2 insertions, 4 deletions

diff --git a/drivers/acpi/events/evevent.c b/drivers/acpi/events/evevent.c
index a1f87b5def2a..e41287815ea1 100644
--- a/drivers/acpi/events/evevent.c
+++ b/drivers/acpi/events/evevent.c
@@ -239,10 +239,8 @@ u32 acpi_ev_fixed_event_detect(void)
          * Read the fixed feature status and enable registers, as all the cases
          * depend on their values.  Ignore errors here.
          */
-        (void)acpi_hw_register_read(ACPI_MTX_DO_NOT_LOCK,
-                                    ACPI_REGISTER_PM1_STATUS, &fixed_status);
-        (void)acpi_hw_register_read(ACPI_MTX_DO_NOT_LOCK,
-                                    ACPI_REGISTER_PM1_ENABLE, &fixed_enable);
+        (void)acpi_hw_register_read(ACPI_REGISTER_PM1_STATUS, &fixed_status);
+        (void)acpi_hw_register_read(ACPI_REGISTER_PM1_ENABLE, &fixed_enable);
 
         ACPI_DEBUG_PRINT((ACPI_DB_INTERRUPTS,
                           "Fixed Event Block: Enable %08X Status %08X\n",