OMAP: hwmod: separate list locking and hwmod hardware locking

Browse source

Currently omap_hwmod_mutex is being used to protect both the list
access/modification and concurrent access to hwmod functions.  This
patch separates these two types of locking.

First, omap_hwmod_mutex is used only to protect access and
modification of omap_hwmod_list.  Also cleaned up some comments
referring to this mutex that are no longer needed.

Then, for protecting concurrent access to hwmod functions, use a
per-hwmod mutex.  This protects concurrent access to a single hwmod,
but would allow concurrent access to different hwmods.

Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
[paul@pwsan.com: added structure documentation; changed mutex variable
 name]
Signed-off-by: Paul Walmsley <paul@pwsan.com>

...

This commit is contained in:

Kevin Hilman 2010-09-21 10:34:09 -06:00 • committed by Paul Walmsley

parent ff4d3e186b

commit 12b1fdb45c

2 changed files with 33 additions and 32 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

62

arch/arm/mach-omap2/omap_hwmod.c

View file

3

arch/arm/plat-omap/include/plat/omap_hwmod.h

View file