From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, ismael.luceno@corp.bluecherry.net,
pete@sensoray.com, sylvester.nawrocki@gmail.com,
sakari.ailus@iki.fi, Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [RFCv2 PATCH 09/10] DocBook: document the new v4l2 matrix ioctls.
Date: Thu, 22 Aug 2013 12:34:56 +0200 [thread overview]
Message-ID: <2389202.KPmZT6iCB5@avalon> (raw)
In-Reply-To: <5215B600.8000009@xs4all.nl>
Hi Hans,
On Thursday 22 August 2013 08:56:00 Hans Verkuil wrote:
> On 08/21/2013 11:58 PM, Laurent Pinchart wrote:
> > On Monday 12 August 2013 12:58:32 Hans Verkuil wrote:
> >> From: Hans Verkuil <hans.verkuil@cisco.com>
> >>
> >> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> >> ---
> >>
> >> Documentation/DocBook/media/v4l/v4l2.xml | 2 +
> >> .../DocBook/media/v4l/vidioc-g-matrix.xml | 115 +++++++++++++
> >> .../DocBook/media/v4l/vidioc-query-matrix.xml | 178 +++++++++++++++
> >> 3 files changed, 295 insertions(+)
> >> create mode 100644 Documentation/DocBook/media/v4l/vidioc-g-matrix.xml
> >> create mode 100644
> >> Documentation/DocBook/media/v4l/vidioc-query-matrix.xml
> >
> > [snip]
> >
> >> diff --git a/Documentation/DocBook/media/v4l/vidioc-query-matrix.xml
> >> b/Documentation/DocBook/media/v4l/vidioc-query-matrix.xml new file mode
> >> 100644
> >> index 0000000..c2845c7
> >> --- /dev/null
> >> +++ b/Documentation/DocBook/media/v4l/vidioc-query-matrix.xml
[snip]
> >> + <table pgwide="1" frame="none" id="v4l2-matrix-type">
> >> + <title>Matrix Types</title>
> >> + <tgroup cols="2" align="left">
> >> + <colspec colwidth="30*" />
> >> + <colspec colwidth="55*" />
> >> + <thead>
> >> + <row>
> >> + <entry>Type</entry>
> >> + <entry>Description</entry>
> >> + </row>
> >> + </thead>
> >> + <tbody valign="top">
> >> + <row>
> >> + <entry><constant>V4L2_MATRIX_T_MD_REGION</constant></entry>
> >> + <entry>Hardware motion detection often divides the image into
> >> several
> >> + regions, and each region can have its own motion detection
> >> thresholds.
> >> + This matrix assigns a region number to each element. Each element
> >> is
> >> a __u8.
> >> + Generally each element refers to a block of pixels in the image.
> >
> > From the description I have trouble understanding what the matrix type is
> > for. Do you think we could make the explanation more detailed ?
>
> How about this:
>
> Hardware motion detection divides the image up into cells. If the image
> resolution is WxH and the matrix size is COLSxROWS, then each cell is a
> rectangle of (W/COLS)x(H/ROWS) pixels (approximately as there may be some
> rounding involved). Depending on the hardware each cell can have its own
> properties. This matrix type sets the 'region' property which is a __u8.
> Each region will typically have its own set of motion detection parameters
> such as a threshold that determines the motion detection sensitivity. By
> assigning each cell a region you can create regions with lower and regions
> with higher motion sensitivity.
That sounds good to me. One more question, however: if the hardware divides
the sub-sampled image into regions, how do you configure per-region thresholds
? The V4L2_MATRIX_T_MD_THRESHOLD matrix only configures per-cell thresholds.
> > > + </entry>
> > > + </row>
> > > + <row>
> > > + <entry><constant>V4L2_MATRIX_T_MD_THRESHOLD</constant></entry>
> > > + <entry>Hardware motion detection can assign motion detection
> > > threshold + values to each element of an image. Each element is a
> > > __u16. + Generally each element refers to a block of pixels in
> > > the image.
> This would be improved as well along the same lines:
>
> Hardware motion detection divides the image up into cells. If the image
> resolution is WxH and the matrix size is COLSxROWS, then each cell is a
> rectangle of (W/COLS)x(H/ROWS) pixels (approximately as there may be some
> rounding involved). Depending on the hardware each cell can have its own
> motion detection sensitivity threshold. This matrix type sets the motion
> detection threshold property which is a __u16.
> > > + </entry>
> > > + </row>
> > > + </tbody>
> > > + </tgroup>
> > > + </table>
> > > +
> > > + </refsect1>
> > > + <refsect1>
> > > + &return-value;
> > > + </refsect1>
> > > +</refentry>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-08-22 10:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 10:58 [RFCv2 PATCH 00/10] Matrix and Motion Detection support Hans Verkuil
2013-08-12 10:58 ` [RFCv2 PATCH 01/10] v4l2-controls: add motion detection controls Hans Verkuil
2013-08-21 21:36 ` Laurent Pinchart
2013-08-22 6:32 ` Hans Verkuil
2013-08-12 10:58 ` [RFCv2 PATCH 02/10] v4l2: add matrix support Hans Verkuil
2013-08-14 14:33 ` Sakari Ailus
2013-08-15 6:35 ` Hans Verkuil
2013-08-15 8:23 ` Sakari Ailus
2013-08-12 10:58 ` [RFCv2 PATCH 03/10] v4l2-compat-ioctl32: add g/s_matrix support Hans Verkuil
2013-08-21 22:02 ` Laurent Pinchart
2013-08-22 6:41 ` Hans Verkuil
2013-08-12 10:58 ` [RFCv2 PATCH 04/10] solo: implement the new matrix ioctls instead of the custom ones Hans Verkuil
2013-08-12 10:58 ` [RFCv2 PATCH 05/10] v4l2: add a motion detection event Hans Verkuil
2013-08-12 10:58 ` [RFCv2 PATCH 06/10] solo6x10: implement motion detection events and controls Hans Verkuil
2013-08-12 10:58 ` [RFCv2 PATCH 07/10] DocBook: add the new v4l detection class controls Hans Verkuil
2013-08-12 10:58 ` [RFCv2 PATCH 08/10] DocBook: document new v4l motion detection event Hans Verkuil
2013-08-21 21:41 ` Laurent Pinchart
2013-08-22 6:38 ` Hans Verkuil
2013-08-22 10:35 ` Laurent Pinchart
2013-08-12 10:58 ` [RFCv2 PATCH 09/10] DocBook: document the new v4l2 matrix ioctls Hans Verkuil
2013-08-21 21:58 ` Laurent Pinchart
2013-08-22 6:56 ` Hans Verkuil
2013-08-22 10:34 ` Laurent Pinchart [this message]
2013-08-22 10:42 ` Hans Verkuil
2013-08-12 10:58 ` [RFCv2 PATCH 10/10] go7007: add motion detection support 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=2389202.KPmZT6iCB5@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=ismael.luceno@corp.bluecherry.net \
--cc=linux-media@vger.kernel.org \
--cc=pete@sensoray.com \
--cc=sakari.ailus@iki.fi \
--cc=sylvester.nawrocki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.