From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, vinod.govindapillai@intel.com
Subject: Re: [PATCH 1/1] v4l: Add frame end event
Date: Mon, 11 Nov 2013 19:27:57 +0200 [thread overview]
Message-ID: <5281139D.1050801@linux.intel.com> (raw)
In-Reply-To: <5280CA88.8030207@xs4all.nl>
Hi Hans,
Thanks for your comments.
Hans Verkuil wrote:
...
> I have no objections to this patch. You do need to adapt drivers/media/platform/omap3isp/ispccdc.c
> a bit since it is using the FRAME_SYNC event and so it should check the id field.
Good point.
> But will you also be upstreaming a driver that uses the SYNC_END?
>
> I don't really want to merge this if nobody is using it.
I agree --- I can't say right now when there could be an upstreamable
driver using that event. Let's keep it out of the tree for now.
Especially that after giving some thought to the multi stream use cases
--- now arguing against my own proposal ;-) --- the "id" field would be
better used to make a difference between different streams, especially
for the frame start event. We're not exactly running out of possible
values for the type field.
So I'd now prefer an entirely separate event to tell about the frame
end, and perhaps add an alias for the frame sync event (FRAME_START).
(This again is a proof of why things that are not going to get used
pretty much immediately should almost never be merged.) I can send a
patch on that as well, and, should someone else need it, that one can be
merged, naturally after a review.
--
Kind regards,
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2013-11-11 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 13:10 [PATCH 1/1] v4l: Add frame end event Sakari Ailus
2013-11-11 12:16 ` Hans Verkuil
2013-11-11 17:27 ` Sakari Ailus [this message]
2013-11-12 13:47 ` [PATCH v2 " Sakari Ailus
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=5281139D.1050801@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=vinod.govindapillai@intel.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).