public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: linux-media@vger.kernel.org, slongerbeam@gmail.com
Cc: Philippe De Muyter <phdm@macqel.be>
Subject: [PATCH v3 0/2] media: v4l2-subdev.h: allow V4L2_FRMIVAL_TYPE_CONTINUOUS & _STEPWISE
Date: Tue, 11 Sep 2018 19:06:31 +0200	[thread overview]
Message-ID: <1536685593-27512-1-git-send-email-phdm@macqel.be> (raw)
In-Reply-To: <linux-media@vger.kernel.org.slongerbeam@gmail.com>

add V4L2_FRMIVAL_TYPE_CONTINUOUS and V4L2_FRMIVAL_TYPE_STEPWISE for
subdev's frame intervals in addition to implicit existing
V4L2_FRMIVAL_TYPE_DISCRETE type.
--
v2:
	Add a 'type' field and a helper function, as asked by Hans
v3:
	Fix documentation (as asked by Hans)
	Convert a driver to use the new helper function (asked by Hans)
	Initialize 'which' to V4L2_SUBDEV_FORMAT_ACTIVE in helper

Philippe De Muyter (2):
  media: v4l2-subdev.h: allow V4L2_FRMIVAL_TYPE_CONTINUOUS & _STEPWISE
  media: imx: capture: use 'v4l2_fill_frmivalenum_from_subdev'

 .../uapi/v4l/vidioc-subdev-enum-frame-interval.rst | 69 +++++++++++++++++++++-
 drivers/media/v4l2-core/v4l2-common.c              | 32 ++++++++++
 drivers/staging/media/imx/imx-media-capture.c      | 18 +-----
 include/media/v4l2-common.h                        | 12 ++++
 include/uapi/linux/v4l2-subdev.h                   | 22 ++++++-
 5 files changed, 133 insertions(+), 20 deletions(-)

-- 
1.8.4

       reply	other threads:[~2018-09-11 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <linux-media@vger.kernel.org.slongerbeam@gmail.com>
2018-09-11 17:06 ` Philippe De Muyter [this message]
2018-09-11 17:06   ` [PATCH v3 1/2] media: v4l2-subdev.h: allow V4L2_FRMIVAL_TYPE_CONTINUOUS & _STEPWISE Philippe De Muyter
2018-09-20 14:11     ` Laurent Pinchart
2018-09-20 15:15       ` Philippe De Muyter
2018-09-11 17:06   ` [PATCH v3 2/2] media: imx: capture: use 'v4l2_fill_frmivalenum_from_subdev' Philippe De Muyter

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=1536685593-27512-1-git-send-email-phdm@macqel.be \
    --to=phdm@macqel.be \
    --cc=linux-media@vger.kernel.org \
    --cc=slongerbeam@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