diff options
| author | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2012-12-04 12:55:18 (GMT) |
|---|---|---|
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2012-12-07 14:55:03 (GMT) |
| commit | b41deecbda70067b26a3a7704fdf967a7940935b (patch) | |
| tree | 5d609dc0469c58a29f18cd8e3eb427e427e9cca3 /lib/kobject_uevent.c | |
| parent | 636f4e1b45c6204c6912cefa2bdbe22e00784a43 (diff) | |
| download | linux-b41deecbda70067b26a3a7704fdf967a7940935b.tar.xz | |
OMAPFB: simplify locking
Kernel lock verification code has lately detected possible circular
locking in omapfb. The exact problem is unclear, but omapfb's current
locking seems to be overly complex.
This patch simplifies the locking in the following ways:
- Remove explicit omapfb mem region locking. I couldn't figure out the
need for this, as long as we take care to take omapfb lock.
- Get omapfb lock always, even if the operation is possibly only related
to one fb_info. Better safe than sorry, and normally there's only one
user for the fb so this shouldn't matter.
- Make sure fb_info lock is taken first, then omapfb lock.
With this patch the warnings about possible circular locking does not
happen anymore.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Diffstat (limited to 'lib/kobject_uevent.c')
0 files changed, 0 insertions, 0 deletions