From: bnvandana@gmail.com (Vandana BN)
Subject: [Linux-kernel-mentees] [PATCH v3 0/2] vivid: Metadata output support
Date: Fri, 4 Oct 2019 17:38:35 +0530 [thread overview]
Message-ID: <20191004120837.31614-1-bnvandana@gmail.com> (raw)
Message-ID: <20191004120835.YRaYyYatoFJxjjuytMnZs_xBTun0qK2XF6rkXfxyats@z> (raw)
In-Reply-To: <787ff1cb-dde3-800a-9dde-68f1db5e4897@xs4all.nl>
This patch adds metadata output support in vivid driver.
New metadata format V4L2_META_FMT_VIVID is added,
which is used to set brightness, contrast, sturation and hue.
V2 has changes in metadata output structure and metadata format define.
V3 addresses review comments.
Regards,
Vandana.
Vandana BN (2):
v4l2-core: Add new metadata format
vivid: Add metadata output support
drivers/media/platform/vivid/Makefile | 2 +-
drivers/media/platform/vivid/vivid-core.c | 98 +++++++++-
drivers/media/platform/vivid/vivid-core.h | 10 +
drivers/media/platform/vivid/vivid-ctrls.c | 12 +-
.../media/platform/vivid/vivid-kthread-out.c | 50 ++++-
drivers/media/platform/vivid/vivid-meta-out.c | 174 ++++++++++++++++++
drivers/media/platform/vivid/vivid-meta-out.h | 25 +++
drivers/media/platform/vivid/vivid-vid-out.c | 5 +-
drivers/media/v4l2-core/v4l2-ioctl.c | 1 +
include/uapi/linux/videodev2.h | 1 +
10 files changed, 367 insertions(+), 11 deletions(-)
create mode 100644 drivers/media/platform/vivid/vivid-meta-out.c
create mode 100644 drivers/media/platform/vivid/vivid-meta-out.h
--
2.17.1
next prev parent reply other threads:[~2019-10-04 12:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 7:18 [Linux-kernel-mentees] [PATCH 0/2] vivid: Metadata output support bnvandana
2019-10-03 7:18 ` Vandana BN
2019-10-03 7:18 ` [Linux-kernel-mentees] [PATCH 1/2] v4l2-core: Add new metadata format bnvandana
2019-10-03 7:18 ` Vandana BN
2019-10-03 7:23 ` hverkuil
2019-10-03 7:23 ` Hans Verkuil
2019-10-03 7:24 ` hverkuil
2019-10-03 7:24 ` Hans Verkuil
2019-10-03 11:08 ` [Linux-kernel-mentees] [PATCH v2 0/2] vivid: Metadata output support bnvandana
2019-10-03 11:08 ` Vandana BN
2019-10-03 11:08 ` [Linux-kernel-mentees] [PATCH v2 1/2] v4l2-core: Add new metadata format bnvandana
2019-10-03 11:08 ` Vandana BN
2019-10-03 12:58 ` hverkuil
2019-10-03 12:58 ` Hans Verkuil
2019-10-03 16:22 ` skhan
2019-10-03 16:22 ` Shuah Khan
2019-10-03 11:08 ` [Linux-kernel-mentees] [PATCH v2 2/2] vivid: Add metadata output support bnvandana
2019-10-03 11:08 ` Vandana BN
2019-10-03 13:06 ` hverkuil
2019-10-03 13:06 ` Hans Verkuil
2019-10-03 17:38 ` skhan
2019-10-03 17:38 ` Shuah Khan
2019-10-04 9:55 ` hverkuil
2019-10-04 9:55 ` Hans Verkuil
2019-10-04 12:08 ` bnvandana [this message]
2019-10-04 12:08 ` [Linux-kernel-mentees] [PATCH v3 0/2] vivid: Metadata " Vandana BN
2019-10-04 12:08 ` [Linux-kernel-mentees] [PATCH v3 1/2] v4l2-core: Add new metadata format bnvandana
2019-10-04 12:08 ` Vandana BN
2019-10-04 12:08 ` [Linux-kernel-mentees] [PATCH v3 2/2] vivid: Add metadata output support bnvandana
2019-10-04 12:08 ` Vandana BN
2019-10-07 14:26 ` hverkuil
2019-10-07 14:26 ` Hans Verkuil
2019-10-03 7:18 ` [Linux-kernel-mentees] [PATCH " bnvandana
2019-10-03 7:18 ` Vandana BN
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=20191004120837.31614-1-bnvandana@gmail.com \
--to=bnvandana@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;
as well as URLs for NNTP newsgroup(s).