From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: linux-media@vger.kernel.org
Cc: Vandana BN <bnvandana@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [PATCHv4 0/3] v4l2-core: Add metadata type to vfl_devnode_type
Date: Tue, 17 Sep 2019 15:36:44 +0200 [thread overview]
Message-ID: <20190917133647.17533-1-hverkuil-cisco@xs4all.nl> (raw)
This is a follow-up series from Vandana's "[v3] v4l2-core: Add metadata type to
vfl_devnode_type" patch: https://patchwork.linuxtv.org/patch/58755/
While testing that v3 patch with a patched version of vivid that has metadata
capture support, I realized that metadata should be treated the same way as
vbi in determine_valid_ioctls(). That makes sense since vbi *is* effectively
metadata. So I changed Vandana's patch (hence my Co-Developed-by tag) to
correctly validate the ioctls for metadata.
I also added two follow-up patches to simplify the SDR code in that function,
and to fix the code for v4l-touch devices (too many ioctls were enabled for
such devices). I think the final code is easier to read as well.
Regards,
Hans
Hans Verkuil (2):
v4l2-dev: simplify the SDR checks
v4l2-dev: fix is_tch checks
Vandana BN (1):
v4l2-core: Add metadata type to vfl_devnode_type
drivers/media/v4l2-core/v4l2-dev.c | 97 ++++++++++++++++------------
drivers/media/v4l2-core/v4l2-ioctl.c | 5 +-
include/media/v4l2-dev.h | 2 +
3 files changed, 61 insertions(+), 43 deletions(-)
--
2.20.1
next reply other threads:[~2019-09-17 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 13:36 Hans Verkuil [this message]
2019-09-17 13:36 ` [PATCHv4 1/3] v4l2-core: Add metadata type to vfl_devnode_type Hans Verkuil
2019-09-17 13:36 ` [PATCHv4 2/3] v4l2-dev: simplify the SDR checks Hans Verkuil
2019-09-17 13:36 ` [PATCHv4 3/3] v4l2-dev: fix is_tch checks Hans Verkuil
2019-09-20 23:48 ` [PATCHv4 0/3] v4l2-core: Add metadata type to vfl_devnode_type Laurent Pinchart
2019-09-23 8:11 ` Hans Verkuil
2019-09-23 8:17 ` Sakari Ailus
2019-09-23 8:47 ` Hans Verkuil
2019-09-23 8:54 ` 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=20190917133647.17533-1-hverkuil-cisco@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=bnvandana@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.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).