From: Hans Verkuil <hverkuil@xs4all.nl>
To: Dean Anderson <linux-dev@sensoray.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] s2255drv: file handle cleanup
Date: Wed, 05 Feb 2014 08:16:59 +0100 [thread overview]
Message-ID: <52F1E56B.50602@xs4all.nl> (raw)
In-Reply-To: <13a909e44a406b9b9e54c6941d853e7f@sensoray.com>
On 02/05/2014 12:10 AM, Dean Anderson wrote:
> Hi Hans,
>
> Please ignore and reject this patch. videobuf_queue_vmalloc_init needs
> to be in probe, not in open.
>
> Let me know your thoughts on doing videobuf2 before s2255_fh removal so
> we don't have to work around or fix videobuf version one's deficiencies.
What I have done in the past w.r.t. vb2 conversions is to move fields
out of the fh struct where it is possible without breaking videobuf, then
when I do the final vb2 conversion I drop the fh struct completely.
As you mentioned before, the resources field can't really be dropped
until the vb2 conversion, but it simplifies matters if the rest is moved
out first. The end result of a vb2 conversion is great, but the actual
patch is a pain to review :-)
Now that I am adding streaming tests in v4l2-compliance I am hoping that
it will be easier to verify correctness in the future, something that
really hasn't been possible.
Regards,
Hans
>
> Thanks,
>
>
>
>
> On 2014-02-04 16:36, Dean Anderson wrote:
>> Removes most parameters from s2255_fh. These elements belong in
>> s2255_ch.
>> In the future, s2255_fh will be removed when videobuf2 is used.
>> videobuf2
>> has convenient and safe functions for locking streaming resources.
>>
>> The removal of s2255_fh (and s2255_fh->resources) was not done now to
>> avoid using videobuf_queue_is_busy.
>>
>> videobuf_queue_is busy may be unsafe as noted by the following comment
>> in videobuf-core.c:
>> "/* Locking: Only usage in bttv unsafe find way to remove */"
>>
>> Signed-off-by: Dean Anderson <linux-dev@sensoray.com>
>> ---
next prev parent reply other threads:[~2014-02-05 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 22:36 [PATCH] s2255drv: file handle cleanup Dean Anderson
2014-02-04 23:10 ` Dean Anderson
2014-02-05 7:16 ` Hans Verkuil [this message]
2014-02-05 7:10 ` Hans Verkuil
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=52F1E56B.50602@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-dev@sensoray.com \
--cc=linux-media@vger.kernel.org \
/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