From: Hans Verkuil <hverkuil@xs4all.nl>
To: Andrey Utkin <andrey.krieger.utkin@gmail.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org
Cc: ismael.luceno@corp.bluecherry.net, m.chehab@samsung.com
Subject: Re: [PATCH 4/4] [media] solo6x10: don't turn off/on encoder interrupt in processing loop
Date: Mon, 03 Nov 2014 16:15:49 +0100 [thread overview]
Message-ID: <54579C25.5060705@xs4all.nl> (raw)
In-Reply-To: <1414598634-13446-4-git-send-email-andrey.krieger.utkin@gmail.com>
Hi Andrey,
On 10/29/2014 05:03 PM, Andrey Utkin wrote:
> The used approach actually cannot prevent new encoder interrupt to
> appear, because interrupt handler can execute in different thread, and
> in current implementation there is still race condition regarding this.
I don't understand what you mean with 'interrupt handler can execute in
different thread'. Can you elaborate?
Note that I do think that this change makes sense, but I do like to have a
better explanation.
Regards,
Hans
> Also from practice the code with this change seems to work as stable as
> before.
>
> Signed-off-by: Andrey Utkin <andrey.krieger.utkin@gmail.com>
> ---
> drivers/media/pci/solo6x10/solo6x10-v4l2-enc.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/media/pci/solo6x10/solo6x10-v4l2-enc.c b/drivers/media/pci/solo6x10/solo6x10-v4l2-enc.c
> index b9b61b9..30e09d9 100644
> --- a/drivers/media/pci/solo6x10/solo6x10-v4l2-enc.c
> +++ b/drivers/media/pci/solo6x10/solo6x10-v4l2-enc.c
> @@ -703,9 +703,7 @@ static int solo_ring_thread(void *data)
>
> if (timeout == -ERESTARTSYS || kthread_should_stop())
> break;
> - solo_irq_off(solo_dev, SOLO_IRQ_ENCODER);
> solo_handle_ring(solo_dev);
> - solo_irq_on(solo_dev, SOLO_IRQ_ENCODER);
> try_to_freeze();
> }
>
>
next prev parent reply other threads:[~2014-11-03 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 16:03 [PATCH 1/4] [media] solo6x10: free vb2 buffers on stop_streaming Andrey Utkin
2014-10-29 16:03 ` [PATCH 2/4] [media] solo6x10: free DMA allocation when releasing encoder Andrey Utkin
2014-10-29 16:03 ` [PATCH 3/4] [media] solo6x10: bind start & stop of encoded frames processing thread to device (de)init Andrey Utkin
2014-10-29 16:03 ` [PATCH 4/4] [media] solo6x10: don't turn off/on encoder interrupt in processing loop Andrey Utkin
2014-11-03 15:15 ` Hans Verkuil [this message]
2014-11-04 17:55 ` Andrey Utkin
2014-11-06 14:58 ` [PATCH 1/4] [media] solo6x10: free vb2 buffers on stop_streaming Dan Carpenter
2014-11-06 21:06 ` [PATCH v2 1/4] [media] solo6x10: clean up properly in stop_streaming Andrey Utkin
2014-11-07 6:30 ` Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54579C25.5060705@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=andrey.krieger.utkin@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=ismael.luceno@corp.bluecherry.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.