From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-media@vger.kernel.org, kyungmin.park@samsung.com,
p.osciak@samsung.com, s.nawrocki@samsung.com
Subject: Re: [PATCH 7/8] v4l: Add EBUSY error description for VIDIOC_STREAMON
Date: Fri, 22 Oct 2010 22:18:04 -0200 [thread overview]
Message-ID: <4CC229BC.90000@redhat.com> (raw)
In-Reply-To: <1283756030-28634-8-git-send-email-m.szyprowski@samsung.com>
Em 06-09-2010 03:53, Marek Szyprowski escreveu:
> From: Pawel Osciak <p.osciak@samsung.com>
>
> VIDIOC_STREAMON should return EBUSY if streaming is already active.
>
> Signed-off-by: Pawel Osciak <p.osciak@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> Documentation/DocBook/v4l/vidioc-streamon.xml | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/DocBook/v4l/vidioc-streamon.xml b/Documentation/DocBook/v4l/vidioc-streamon.xml
> index e42bff1..fdbd8d8 100644
> --- a/Documentation/DocBook/v4l/vidioc-streamon.xml
> +++ b/Documentation/DocBook/v4l/vidioc-streamon.xml
> @@ -93,6 +93,13 @@ synchronize with other events.</para>
> been allocated (memory mapping) or enqueued (output) yet.</para>
> </listitem>
> </varlistentry>
> + <varlistentry>
> + <term><errorcode>EBUSY</errorcode></term>
> + <listitem>
> + <para><constant>VIDIOC_STREAMON</constant> called, but
> + streaming I/O already active.</para>
> + </listitem>
> + </varlistentry>
> </variablelist>
> </refsect1>
> </refentry>
I'm in doubt about this patch. I don't see any problem on just return 0 if
stream is active.
Actually, I think that this patch may break some applications, as there are
some cases where stream may start even without streamon (like via read() method).
Cheers,
Mauro
next prev parent reply other threads:[~2010-10-23 0:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 6:53 [PATCH] various bugfixes for 2.6.36-rc3 Marek Szyprowski
2010-09-06 6:53 ` [PATCH 1/8] v4l: s5p-fimc: Fix return value on probe() failure Marek Szyprowski
2010-09-06 6:53 ` [PATCH 2/8] v4l: s5p-fimc: Fix 3-planar formats handling and pixel offset error on S5PV210 SoCs Marek Szyprowski
2010-09-06 6:53 ` [PATCH 3/8] v4l: s5p-fimc: Register definition cleanup Marek Szyprowski
2010-09-06 6:53 ` [PATCH 4/8] v4l: videobuf: Fail streamon on an output device when no buffers queued Marek Szyprowski
2010-09-06 6:53 ` [PATCH 5/8] v4l: videobuf: prevent passing a NULL to dma_free_coherent() Marek Szyprowski
2010-09-06 6:53 ` [PATCH 6/8] v4l: videobuf: remove unused is_userptr variable Marek Szyprowski
2010-09-06 6:53 ` [PATCH 7/8] v4l: Add EBUSY error description for VIDIOC_STREAMON Marek Szyprowski
2010-10-23 0:18 ` Mauro Carvalho Chehab [this message]
2010-10-24 16:52 ` Pawel Osciak
2010-10-24 19:50 ` Laurent Pinchart
2010-10-24 20:14 ` Devin Heitmueller
2010-09-06 6:53 ` [PATCH 8/8] v4l: radio: si470x: fix unneeded free_irq() call Marek Szyprowski
2010-09-06 7:12 ` Jean Delvare
2010-09-06 7:14 ` Joonyoung Shim
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=4CC229BC.90000@redhat.com \
--to=mchehab@redhat.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=p.osciak@samsung.com \
--cc=s.nawrocki@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox