Clock control indirectly requires access to MFC device, so call it only
if we are sure that the device exists in s5p_mfc_release function.
s5p_mfc_remove() calls s5p_mfc_final_pm(), which releases all PM related
resources, including clocks, so any call to clocks related functions
is not valid after s5p_mfc_final_pm().

Fixes: d695c12 ("[media] media: s5p-mfc fix invalid memory access from
s5p_mfc_release()")

Signed-off-by: Marek Szyprowski <[email protected]>
---
 drivers/media/platform/s5p-mfc/s5p_mfc.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc.c 
b/drivers/media/platform/s5p-mfc/s5p_mfc.c
index 0c8a4616e827..a0a29194ccd1 100644
--- a/drivers/media/platform/s5p-mfc/s5p_mfc.c
+++ b/drivers/media/platform/s5p-mfc/s5p_mfc.c
@@ -940,10 +940,11 @@ static int s5p_mfc_release(struct file *file)
        mfc_debug_enter();
        if (dev)
                mutex_lock(&dev->mfc_mutex);
-       s5p_mfc_clock_on();
        vb2_queue_release(&ctx->vq_src);
        vb2_queue_release(&ctx->vq_dst);
        if (dev) {
+               s5p_mfc_clock_on();
+
                /* Mark context as idle */
                clear_work_bit_irqsave(ctx);
                /*
@@ -965,9 +966,9 @@ static int s5p_mfc_release(struct file *file)
                        if (s5p_mfc_power_off() < 0)
                                mfc_err("Power off failed\n");
                }
+               mfc_debug(2, "Shutting down clock\n");
+               s5p_mfc_clock_off();
        }
-       mfc_debug(2, "Shutting down clock\n");
-       s5p_mfc_clock_off();
        if (dev)
                dev->ctx[ctx->num] = NULL;
        s5p_mfc_dec_ctrls_delete(ctx);
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to