OMAP2+: clockdomain: Add per clkdm lock to prevent concurrent state programming

Browse source

Since the clkdm state programming is now done from within the hwmod
framework (which uses a per-hwmod lock) instead of the being done
from the clock framework (which used a global lock), there is now a
need to have per-clkdm locking to prevent races between different
hwmods/modules belonging to the same clock domain concurrently
programming the clkdm state.

Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Signed-off-by: Benoit Cousson <b-cousson@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Paul Walmsley <paul@pwsan.com>

...

This commit is contained in:

Rajendra Nayak 2011-07-10 05:56:55 -06:00 • committed by Paul Walmsley

parent b86cfb52a1

commit 555e74ea08

4 changed files with 50 additions and 18 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

47

arch/arm/mach-omap2/clockdomain.c

View file

2

arch/arm/mach-omap2/clockdomain.h

View file

6

arch/arm/mach-omap2/clockdomain2xxx_3xxx.c

View file

13

arch/arm/mach-omap2/clockdomain44xx.c

View file