Juan Gutierrez 93b465c2e1 hwspinlock/core: use a mutex to protect the radix tree ... Since we're using non-atomic radix tree allocations, we should be protecting the tree using a mutex and not a spinlock. Non-atomic allocations and process context locking is good enough, as the tree is manipulated only when locks are registered/ unregistered/requested/freed. The locks themselves are still protected by spinlocks of course, and mutexes are not involved in the locking/unlocking paths. Cc: <stable@kernel.org> Signed-off-by: Juan Gutierrez <jgutierrez@ti.com> [ohad@wizery.com: rewrite the commit log, #include mutex.h, add minor commentary] [ohad@wizery.com: update register/unregister parts in hwspinlock.txt] Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>		2011-09-21 19:45:32 +03:00
..
hwspinlock_core.c	hwspinlock/core: use a mutex to protect the radix tree	2011-09-21 19:45:32 +03:00
hwspinlock_internal.h	hwspinlock/core: simplify 'owner' handling	2011-09-21 19:45:32 +03:00
Kconfig	hwspinlock/core: simplify Kconfig	2011-09-21 19:45:32 +03:00
Makefile
omap_hwspinlock.c	hwspinlock/core/omap: fix id issues on multiple hwspinlock devices	2011-09-21 19:45:32 +03:00