media: staging: media: use relevant lock

The data protected is video_out2 and the lock that is released is
&video_out2->dma_queue_lock, so it seems that that lock should be
taken as well.

Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Signed-off-by: Hans Verkuil <hansverk@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>

diff --git a/drivers/staging/media/davinci_vpfe/dm365_resizer.c b/drivers/staging/media/davinci_vpfe/dm365_resizer.c
index df6d55e9554d51b3bb18c1c7762641d6eb120fa0..2b797474a34463d9743ed1a148f7a004c56c6a62 100644 (file)
--- a/drivers/staging/media/davinci_vpfe/dm365_resizer.c
+++ b/drivers/staging/media/davinci_vpfe/dm365_resizer.c
@@ -1060,7 +1060,7 @@ static void resizer_ss_isr(struct vpfe_resizer_device *resizer)
        /* If resizer B is enabled */
        if (pipe->output_num > 1 && resizer->resizer_b.output ==
            RESIZER_OUTPUT_MEMORY) {
-               spin_lock(&video_out->dma_queue_lock);
+               spin_lock(&video_out2->dma_queue_lock);
                vpfe_video_process_buffer_complete(video_out2);
                video_out2->state = VPFE_VIDEO_BUFFER_NOT_QUEUED;
                vpfe_video_schedule_next_buffer(video_out2);