From: Sakari Ailus <sakari.ailus@iki.fi>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
Sylwester Nawrocki <snjw23@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [PATCH v2 0/2] Frame synchronisation events and support for them in the OMAP 3 ISP driver
Date: Tue, 02 Aug 2011 13:40:21 +0300 [thread overview]
Message-ID: <4E37D415.8060000@iki.fi> (raw)
Hi all,
This is the second version of the frame synchronisation patchset which
contains fixes based on the comments from Laurent. The patches are on
top of this tree which contains acked patches:
http://linuxtv.org/git/sailus/media_tree.git media-for-3.1-misc-1
Shortlog is available here:
<URL:http://git.linuxtv.org/sailus/media_tree.git/shortlog/refs/heads/media-for-3.1-misc-1>
Changes since the first one:
- Fixed the description of the second patch.
- Clarified the documentation.
- v4l2_event_frame_sync.buffer_sequence renamed to frame_sequence
Changes to the RFC:
- Renamed V4L2_EVENT_FRAME_START to V4L2_EVENT_FRAME_SYNC.
- Removed extra reference to V4L2_EVENT_FRAME_START in documentation; it
is mentioned in the same page struct v4l2_event_frame_sync is related to it.
- The OMAP 3 ISP driver check that the id field is zero in anticipation
of such events.
--
Sakari Ailus
sakari.ailus@iki.fi
next reply other threads:[~2011-08-02 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 10:40 Sakari Ailus [this message]
2011-08-02 10:40 ` [PATCH v2 1/2] v4l: events: Define V4L2_EVENT_FRAME_SYNC Sakari Ailus
2011-08-02 10:40 ` [PATCH v2 2/2] omap3isp: ccdc: Make frame start event generic Sakari Ailus
2011-08-02 13:44 ` [PATCH v2 0/2] Frame synchronisation events and support for them in the OMAP 3 ISP driver Laurent Pinchart
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=4E37D415.8060000@iki.fi \
--to=sakari.ailus@iki.fi \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=snjw23@gmail.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