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>
This commit is contained in:
committed by
Len Brown
parent
bbf25010f1
commit
d30dc9abb4
@@ -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,
|
||||
|
Reference in New Issue
Block a user