From: Jacob Chen <jacob-chen@iotwrt.com>
To: linux-rockchip@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
heiko@sntech.de, robh+dt@kernel.org, mchehab@kernel.org,
linux-media@vger.kernel.org,
laurent.pinchart+renesas@ideasonboard.com,
hans.verkuil@cisco.com, s.nawrocki@samsung.com,
tfiga@chromium.org, nicolas@ndufresne.ca,
Jacob Chen <jacob-chen@iotwrt.com>
Subject: [PATCH v3 1/5] [media] v4l: add porter duff blend controls
Date: Mon, 31 Jul 2017 11:07:36 +0800 [thread overview]
Message-ID: <1501470460-12014-2-git-send-email-jacob-chen@iotwrt.com> (raw)
In-Reply-To: <1501470460-12014-1-git-send-email-jacob-chen@iotwrt.com>
At peresent, we don't have a control for Compositing and Blend.
All drivers are just doing copies while actually many hardwares
supports more functions.
So Adding V4L2 controls for Compositing and Blend, used for for
composting streams.
The values are based on porter duff operations.
Defined in below links.
https://developer.xamarin.com/api/type/Android.Graphics.PorterDuff+Mode/
Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
Suggested-by: Nicolas Dufresne <nicolas@ndufresne.ca>
---
drivers/media/v4l2-core/v4l2-ctrls.c | 20 +++++++++++++++++++-
include/uapi/linux/v4l2-controls.h | 16 +++++++++++++++-
2 files changed, 34 insertions(+), 2 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c b/drivers/media/v4l2-core/v4l2-ctrls.c
index b9e08e3..561d7d5 100644
--- a/drivers/media/v4l2-core/v4l2-ctrls.c
+++ b/drivers/media/v4l2-core/v4l2-ctrls.c
@@ -478,7 +478,21 @@ const char * const *v4l2_ctrl_get_menu(u32 id)
"Region Grid",
NULL,
};
-
+ static const char * const porter_duff_modes[] = {
+ "Source",
+ "Source Top",
+ "Source In",
+ "Source Out",
+ "Source Over",
+ "Destination",
+ "Destination Top",
+ "Destination In",
+ "Destination Out",
+ "Destination Over",
+ "Add",
+ "Clear",
+ NULL
+ };
switch (id) {
case V4L2_CID_MPEG_AUDIO_SAMPLING_FREQ:
@@ -564,6 +578,8 @@ const char * const *v4l2_ctrl_get_menu(u32 id)
return vpx_golden_frame_sel;
case V4L2_CID_JPEG_CHROMA_SUBSAMPLING:
return jpeg_chroma_subsampling;
+ case V4L2_CID_PORTER_DUFF_MODE:
+ return porter_duff_modes;
case V4L2_CID_DV_TX_MODE:
return dv_tx_mode;
case V4L2_CID_DV_TX_RGB_RANGE:
@@ -886,6 +902,7 @@ const char *v4l2_ctrl_get_name(u32 id)
case V4L2_CID_PIXEL_RATE: return "Pixel Rate";
case V4L2_CID_TEST_PATTERN: return "Test Pattern";
case V4L2_CID_DEINTERLACING_MODE: return "Deinterlacing Mode";
+ case V4L2_CID_PORTER_DUFF_MODE: return "PorterDuff Blend Modes";
/* DV controls */
/* Keep the order of the 'case's the same as in v4l2-controls.h! */
@@ -1060,6 +1077,7 @@ void v4l2_ctrl_fill(u32 id, const char **name, enum v4l2_ctrl_type *type,
case V4L2_CID_DV_RX_IT_CONTENT_TYPE:
case V4L2_CID_TEST_PATTERN:
case V4L2_CID_DEINTERLACING_MODE:
+ case V4L2_CID_PORTER_DUFF_MODE:
case V4L2_CID_TUNE_DEEMPHASIS:
case V4L2_CID_MPEG_VIDEO_VPX_GOLDEN_FRAME_SEL:
case V4L2_CID_DETECT_MD_MODE:
diff --git a/include/uapi/linux/v4l2-controls.h b/include/uapi/linux/v4l2-controls.h
index 0d2e1e0..9543b4b 100644
--- a/include/uapi/linux/v4l2-controls.h
+++ b/include/uapi/linux/v4l2-controls.h
@@ -893,7 +893,21 @@ enum v4l2_jpeg_chroma_subsampling {
#define V4L2_CID_PIXEL_RATE (V4L2_CID_IMAGE_PROC_CLASS_BASE + 2)
#define V4L2_CID_TEST_PATTERN (V4L2_CID_IMAGE_PROC_CLASS_BASE + 3)
#define V4L2_CID_DEINTERLACING_MODE (V4L2_CID_IMAGE_PROC_CLASS_BASE + 4)
-
+#define V4L2_CID_PORTER_DUFF_MODE (V4L2_CID_IMAGE_PROC_CLASS_BASE + 5)
+enum v4l2_porter_duff_mode {
+ V4L2_PORTER_DUFF_SRC = 0,
+ V4L2_PORTER_DUFF_SRCATOP = 1,
+ V4L2_PORTER_DUFF_SRCIN = 2,
+ V4L2_PORTER_DUFF_SRCOUT = 3,
+ V4L2_PORTER_DUFF_SRCOVER = 4,
+ V4L2_PORTER_DUFF_DST = 5,
+ V4L2_PORTER_DUFF_DSTATOP = 6,
+ V4L2_PORTER_DUFF_DSTIN = 7,
+ V4L2_PORTER_DUFF_DSTOUT = 8,
+ V4L2_PORTER_DUFF_DSTOVER = 9,
+ V4L2_PORTER_DUFF_ADD = 10,
+ V4L2_PORTER_DUFF_CLEAR = 11,
+};
/* DV-class control IDs defined by V4L2 */
#define V4L2_CID_DV_CLASS_BASE (V4L2_CTRL_CLASS_DV | 0x900)
--
2.7.4
next prev parent reply other threads:[~2017-07-31 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 3:07 [PATCH v3 0/5] Add Rockchip RGA V4l2 support Jacob Chen
2017-07-31 3:07 ` Jacob Chen [this message]
2017-07-31 8:12 ` [PATCH v3 1/5] [media] v4l: add porter duff blend controls Hans Verkuil
2017-07-31 3:07 ` [PATCH v3 2/5] [media]: rockchip/rga: v4l2 m2m support Jacob Chen
[not found] ` <1501470460-12014-3-git-send-email-jacob-chen-fyOeoxGR3m/QT0dZR+AlfA@public.gmane.org>
2017-07-31 8:38 ` Hans Verkuil
2017-07-31 14:25 ` Jacob Chen
2017-07-31 3:07 ` [PATCH v3 3/5] ARM: dts: rockchip: add RGA device node for RK3288 Jacob Chen
2017-07-31 3:07 ` [PATCH v3 4/5] ARM: dts: rockchip: add RGA device node for RK3399 Jacob Chen
2017-07-31 3:07 ` [PATCH v3 5/5] dt-bindings: Document the Rockchip RGA bindings Jacob Chen
[not found] ` <1501470460-12014-1-git-send-email-jacob-chen-fyOeoxGR3m/QT0dZR+AlfA@public.gmane.org>
2017-07-31 7:21 ` [PATCH v3 0/5] Add Rockchip RGA V4l2 support Jacob Chen
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=1501470460-12014-2-git-send-email-jacob-chen@iotwrt.com \
--to=jacob-chen@iotwrt.com \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=heiko@sntech.de \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tfiga@chromium.org \
/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).