From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-media@vger.kernel.org, hverkuil@xs4all.nl,
kyungmin.park@samsung.com, pawel@osciak.com,
javier.martin@vista-silicon.com, m.szyprowski@samsung.com,
shaik.ameer@samsung.com, arun.kk@samsung.com,
k.debski@samsung.com, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH RFC 2/7] mem2mem_testdev: Use mem-to-mem ioctl and vb2 helpers
Date: Sun, 15 Sep 2013 22:58:09 +0200 [thread overview]
Message-ID: <52361F61.8050207@gmail.com> (raw)
In-Reply-To: <1379077699.4396.16.camel@pizza.hi.pengutronix.de>
Hi Philipp,
On 09/13/2013 03:08 PM, Philipp Zabel wrote:
> Am Freitag, den 13.09.2013, 14:56 +0200 schrieb Sylwester Nawrocki:
[...]
>> @@ -865,6 +793,7 @@ static int queue_init(void *priv, struct vb2_queue *src_vq, struct vb2_queue *ds
>> dst_vq->ops =&m2mtest_qops;
>> dst_vq->mem_ops =&vb2_vmalloc_memops;
>> dst_vq->timestamp_type = V4L2_BUF_FLAG_TIMESTAMP_COPY;
>> + dst_vq->lock =&ctx->dev->dev_mutex;
>>
>> return vb2_queue_init(dst_vq);
>> }
>> @@ -945,6 +874,7 @@ static int m2mtest_open(struct file *file)
>> kfree(ctx);
>> goto open_unlock;
>> }
>> + ctx->fh.m2m_ctx = ctx->m2m_ctx;
>
> Since you added m2m_ctx to v4l2_fh, why not drop ctx->m2m_ctx altogether
> and always use ctx->fh.m2m_ctx instead?
Yes, that might make it a bit cleaner. I guess I wanted to minimize
the necessary changes. I'll amend that in all drivers in this series
for the next iteration, as they all look very similar. Thanks for the
suggestion.
--
Regards,
Sylwester
next prev parent reply other threads:[~2013-09-15 20:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 12:56 [PATCH RFC 0/7] V4L2 mem-to-mem ioctl helpers Sylwester Nawrocki
2013-09-13 12:56 ` [PATCH RFC 1/7] V4L: Add mem2mem ioctl and file operation helpers Sylwester Nawrocki
2013-09-13 13:13 ` Philipp Zabel
2013-09-15 21:11 ` Sylwester Nawrocki
2013-09-30 9:41 ` Hans Verkuil
2013-10-12 11:02 ` Sylwester Nawrocki
2013-09-13 12:56 ` [PATCH RFC 2/7] mem2mem_testdev: Use mem-to-mem ioctl and vb2 helpers Sylwester Nawrocki
2013-09-13 13:08 ` Philipp Zabel
2013-09-15 20:58 ` Sylwester Nawrocki [this message]
2013-09-16 7:24 ` Philipp Zabel
2013-09-30 9:43 ` Hans Verkuil
2013-09-13 12:56 ` [PATCH RFC 3/7] exynos4-is: Use mem-to-mem ioctl helpers Sylwester Nawrocki
2013-09-30 9:44 ` Hans Verkuil
2013-09-13 12:56 ` [PATCH RFC 4/7] s5p-jpeg: " Sylwester Nawrocki
2013-09-30 9:45 ` Hans Verkuil
2013-09-13 12:56 ` [PATCH RFC 5/7] mx2-emmaprp: " Sylwester Nawrocki
2013-09-30 9:47 ` Hans Verkuil
2013-10-12 11:11 ` Sylwester Nawrocki
2013-09-13 12:56 ` [PATCH RFC 6/7] exynos-gsc: " Sylwester Nawrocki
2013-09-13 14:12 ` Shaik Ameer Basha
2013-09-15 21:40 ` Sylwester Nawrocki
2013-09-30 9:50 ` Hans Verkuil
2013-10-12 11:20 ` Sylwester Nawrocki
2013-09-13 12:56 ` [PATCH RFC 7/7] s5p-g2d: " Sylwester Nawrocki
2013-09-30 9:49 ` 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=52361F61.8050207@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=arun.kk@samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=javier.martin@vista-silicon.com \
--cc=k.debski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=pawel@osciak.com \
--cc=s.nawrocki@samsung.com \
--cc=shaik.ameer@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;
as well as URLs for NNTP newsgroup(s).