summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBob Moore <robert.moore@intel.com>2007-02-02 19:48:21 +0300
committerLen Brown <len.brown@intel.com>2007-02-02 21:14:26 -0500
commitf70a5e7b6c28e0b08f721204f4b98c5d1cfb44d9 (patch)
treede514a441fdc075ae2f89ca8ecc014481459a333
parent310a7f7fee489b7dadd27b0d8487bd0ce66281e7 (diff)
downloadblackbird-op-linux-f70a5e7b6c28e0b08f721204f4b98c5d1cfb44d9.tar.gz
blackbird-op-linux-f70a5e7b6c28e0b08f721204f4b98c5d1cfb44d9.zip
ACPICA: On AML mutex force-release, set depth to zero (was 1).
Signed-off-by: Alexey Starikovskiy <alexey.y.starikovskiy@intel.com> Signed-off-by: Len Brown <len.brown@intel.com>
-rw-r--r--drivers/acpi/executer/exmutex.c8
1 files changed, 7 insertions, 1 deletions
diff --git a/drivers/acpi/executer/exmutex.c b/drivers/acpi/executer/exmutex.c
index f1dd1b07d482..b0be2f46d249 100644
--- a/drivers/acpi/executer/exmutex.c
+++ b/drivers/acpi/executer/exmutex.c
@@ -329,6 +329,12 @@ acpi_ex_release_mutex(union acpi_operand_object *obj_desc,
*
* DESCRIPTION: Release all mutexes held by this thread
*
+ * NOTE: This function is called as the thread is exiting the interpreter.
+ * Mutexes are not released when an individual control method is exited, but
+ * only when the parent thread actually exits the interpreter. This allows one
+ * method to acquire a mutex, and a different method to release it, as long as
+ * this is performed underneath a single parent control method.
+ *
******************************************************************************/
void acpi_ex_release_all_mutexes(struct acpi_thread_state *thread)
@@ -346,7 +352,7 @@ void acpi_ex_release_all_mutexes(struct acpi_thread_state *thread)
obj_desc->mutex.prev = NULL;
obj_desc->mutex.next = NULL;
- obj_desc->mutex.acquisition_depth = 1;
+ obj_desc->mutex.acquisition_depth = 0;
/* Release the mutex, special case for Global Lock */
OpenPOWER on IntegriCloud