diff options
| author | Juan Gutierrez <jgutierrez@ti.com> | 2012-05-17 12:53:34 -0500 |
|---|---|---|
| committer | Ziyann <jaraidaniel@gmail.com> | 2014-10-01 12:58:34 +0200 |
| commit | ddc6bd7c2d35549b3646550766a7180924e83a75 (patch) | |
| tree | bd9d498ff3addb620f0b4ce7eb9999aeae6b064e /drivers/dio | |
| parent | c7e125a47230d09537f4939fa6308f802b55f5a7 (diff) | |
| download | kernel_samsung_tuna-ddc6bd7c2d35549b3646550766a7180924e83a75.zip kernel_samsung_tuna-ddc6bd7c2d35549b3646550766a7180924e83a75.tar.gz kernel_samsung_tuna-ddc6bd7c2d35549b3646550766a7180924e83a75.tar.bz2 | |
rpmsg: omx: initialize completion event in rpmsg_omx_open
An omx object is created when opening the rpmsg-omx device. However
the "reply_arrived" completion event is not initialized until the
connection message is sent across.
When the rpmsg_omx driver is removed (like in recovery), all pending
threads waiting on the "reply_arrived" are unblocked by a complete_all
call, however, if the rpmsg-omx device was only opened, such event is
not initialized yet, so the complete_all call will dereference a null
object causing a panic.
This patch moves the initialization of the "reply_arrived" completion
event to the open call, after the allocation of the omx object.
Change-Id: I92cf9cf5ac748456cb43bedc88fe1a8d80addd6c
Signed-off-by: Juan Gutierrez <jgutierrez@ti.com>
Diffstat (limited to 'drivers/dio')
0 files changed, 0 insertions, 0 deletions