diff options
author | Alexey Starikovskiy <astarikovskiy@suse.de> | 2007-09-30 22:39:36 +0400 |
---|---|---|
committer | Len Brown <len.brown@intel.com> | 2007-10-10 01:00:26 -0400 |
commit | d30dc9abb4aacfd4df3f486f22bcbc0531b73283 (patch) | |
tree | cb2d69e1b5fc00ad7a6691f362e814ddd6af61fa /include/acpi | |
parent | bbf25010f1a6b761914430f5fca081ec8c7accd1 (diff) |
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>
Diffstat (limited to 'include/acpi')
-rw-r--r-- | include/acpi/achware.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/include/acpi/achware.h b/include/acpi/achware.h index 9df275cf7bc1..4053df943453 100644 --- a/include/acpi/achware.h +++ b/include/acpi/achware.h @@ -71,9 +71,9 @@ u32 acpi_hw_get_mode(void); struct acpi_bit_register_info *acpi_hw_get_bit_register_info(u32 register_id); acpi_status -acpi_hw_register_read(u8 use_lock, u32 register_id, u32 * return_value); +acpi_hw_register_read(u32 register_id, u32 * return_value); -acpi_status acpi_hw_register_write(u8 use_lock, u32 register_id, u32 value); +acpi_status acpi_hw_register_write(u32 register_id, u32 value); acpi_status acpi_hw_low_level_read(u32 width, |