Paul Mundt f50bf2b2f5 video: sm501fb: Early initialization of mm_lock mutex.
Commit 537a1bf059fa312355696fa6db80726e655e7f17 (fbdev: add mutex for
fb_mmap locking) introduces a ->mm_lock mutex for protecting smem
assignments. Unfortunately in the case of sm501fb these happen quite
early in the initialization code, well before the mutex_init() that takes
place in register_framebuffer(), leading to:

   Badness at kernel/mutex.c:207

   Pid : 1, Comm:          swapper
   CPU : 0                 Not tainted  (2.6.31-rc1-00284-g529ba0d-dirty #2273)

   PC is at __mutex_lock_slowpath+0x72/0x1bc
   PR is at __mutex_lock_slowpath+0x66/0x1bc
   ...

matroxfb appears to have the same issue and has solved it with an early
mutex_init(), so we do the same for sm501fb.

Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Cc: Krzysztof Helt <krzysztof.h1@wp.pl>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-07-04 10:39:06 -07:00
..
2009-06-30 18:56:01 -07:00
2009-06-30 18:56:00 -07:00
2009-06-30 18:56:00 -07:00
2009-06-30 18:56:00 -07:00
2009-05-12 14:11:35 -07:00
2009-04-01 08:59:31 -07:00
2009-06-16 19:47:59 -07:00
2009-04-01 08:59:32 -07:00
2009-06-30 18:56:00 -07:00
2009-01-12 20:56:32 +01:00
2009-06-16 19:47:58 -07:00
2009-05-06 16:36:10 -07:00
2009-06-30 18:56:00 -07:00
2009-03-27 14:51:15 +01:00
2009-06-30 18:56:00 -07:00
2009-03-17 09:30:36 +09:00
2009-06-30 18:56:00 -07:00
2009-04-01 08:59:31 -07:00
2009-04-01 08:59:31 -07:00
2009-06-12 21:46:59 +09:30
2009-06-30 18:56:00 -07:00