From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, hverkuil@xs4all.nl
Subject: Re: [PATCH v3 1/3] v4l: Add test pattern colour component controls
Date: Thu, 29 May 2014 16:47:40 +0200 [thread overview]
Message-ID: <48325310.Ydj7bxFi9C@avalon> (raw)
In-Reply-To: <1401374448-30411-2-git-send-email-sakari.ailus@linux.intel.com>
Hi Sakari,
Thank you for the patch.
On Thursday 29 May 2014 17:40:46 Sakari Ailus wrote:
> In many cases the test pattern has selectable values for each colour
> component. Implement controls for raw bayer components. Additional controls
> should be defined for colour components that are not covered by these
> controls.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> Documentation/DocBook/media/v4l/controls.xml | 34 +++++++++++++++++++++++++
> drivers/media/v4l2-core/v4l2-ctrls.c | 4 ++++
> include/uapi/linux/v4l2-controls.h | 4 ++++
> 3 files changed, 42 insertions(+)
>
> diff --git a/Documentation/DocBook/media/v4l/controls.xml
> b/Documentation/DocBook/media/v4l/controls.xml index 47198ee..bf23994
> 100644
> --- a/Documentation/DocBook/media/v4l/controls.xml
> +++ b/Documentation/DocBook/media/v4l/controls.xml
> @@ -4677,6 +4677,40 @@ interface and may change in the future.</para>
> conversion.
> </entry>
> </row>
> + <row>
> + <entry
> spanname="id"><constant>V4L2_CID_TEST_PATTERN_RED</constant></entry> +
> <entry>integer</entry>
> + </row>
> + <row>
> + <entry spanname="descr">Test pattern red colour component.
> + </entry>
> + </row>
> + <row>
> + <entry
> spanname="id"><constant>V4L2_CID_TEST_PATTERN_GREENR</constant></entry>
> + <entry>integer</entry>
> + </row>
> + <row>
> + <entry spanname="descr">Test pattern green (next to red)
> + colour component.
What about non-Bayer RGB sensors ? Should they use the GREENR or the GREENB
control for the green component ? Or a different control ?
I'm wondering whether we shouldn't have a single test pattern color control
and create a color type using Hans' complex controls API.
> + </entry>
> + </row>
> + <row>
> + <entry
> spanname="id"><constant>V4L2_CID_TEST_PATTERN_BLUE</constant></entry> +
> <entry>integer</entry>
> + </row>
> + <row>
> + <entry spanname="descr">Test pattern blue colour component.
> + </entry>
> + </row>
> + <row>
> + <entry
> spanname="id"><constant>V4L2_CID_TEST_PATTERN_GREENB</constant></entry> +
> <entry>integer</entry>
> + </row>
> + <row>
> + <entry spanname="descr">Test pattern green (next to blue)
> + colour component.
> + </entry>
> + </row>
> <row><entry></entry></row>
> </tbody>
> </tgroup>
> diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c
> b/drivers/media/v4l2-core/v4l2-ctrls.c index 55c6832..a4104a7 100644
> --- a/drivers/media/v4l2-core/v4l2-ctrls.c
> +++ b/drivers/media/v4l2-core/v4l2-ctrls.c
> @@ -839,6 +839,10 @@ const char *v4l2_ctrl_get_name(u32 id)
> case V4L2_CID_VBLANK: return "Vertical Blanking";
> case V4L2_CID_HBLANK: return "Horizontal Blanking";
> case V4L2_CID_ANALOGUE_GAIN: return "Analogue Gain";
> + case V4L2_CID_TEST_PATTERN_RED: return "Red Pixel Value";
> + case V4L2_CID_TEST_PATTERN_GREENR: return "Green (Red) Pixel Value";
> + case V4L2_CID_TEST_PATTERN_BLUE: return "Blue Pixel Value";
> + case V4L2_CID_TEST_PATTERN_GREENB: return "Green (Blue) Pixel Value";
>
> /* Image processing controls */
> case V4L2_CID_IMAGE_PROC_CLASS: return "Image Processing Controls";
> diff --git a/include/uapi/linux/v4l2-controls.h
> b/include/uapi/linux/v4l2-controls.h index 2ac5597..5c55a19 100644
> --- a/include/uapi/linux/v4l2-controls.h
> +++ b/include/uapi/linux/v4l2-controls.h
> @@ -855,6 +855,10 @@ enum v4l2_jpeg_chroma_subsampling {
> #define V4L2_CID_VBLANK (V4L2_CID_IMAGE_SOURCE_CLASS_BASE + 1)
> #define V4L2_CID_HBLANK (V4L2_CID_IMAGE_SOURCE_CLASS_BASE + 2)
> #define V4L2_CID_ANALOGUE_GAIN (V4L2_CID_IMAGE_SOURCE_CLASS_BASE
+ 3)
> +#define V4L2_CID_TEST_PATTERN_RED (V4L2_CID_IMAGE_SOURCE_CLASS_BASE +
4)
> +#define V4L2_CID_TEST_PATTERN_GREENR (V4L2_CID_IMAGE_SOURCE_CLASS_BASE
+
> 5) +#define V4L2_CID_TEST_PATTERN_BLUE (V4L2_CID_IMAGE_SOURCE_CLASS_BASE
+
> 6) +#define V4L2_CID_TEST_PATTERN_GREENB
(V4L2_CID_IMAGE_SOURCE_CLASS_BASE
> + 7)
>
>
> /* Image processing controls */
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-05-29 14:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 14:40 [PATCH v3 0/3] smiapp test pattern support Sakari Ailus
2014-05-29 14:40 ` [PATCH v3 1/3] v4l: Add test pattern colour component controls Sakari Ailus
2014-05-29 14:47 ` Laurent Pinchart [this message]
2014-05-29 14:58 ` Sakari Ailus
2014-05-29 15:01 ` Laurent Pinchart
2014-05-30 12:28 ` Hans Verkuil
2014-06-03 12:21 ` Laurent Pinchart
2014-06-03 12:27 ` Sakari Ailus
2014-06-03 12:42 ` Hans Verkuil
2014-06-10 12:15 ` Hans Verkuil
2014-05-29 14:40 ` [PATCH v3 2/3] smiapp: Add driver-specific test pattern menu item definitions Sakari Ailus
2014-05-29 14:48 ` Laurent Pinchart
2014-05-29 15:08 ` Sakari Ailus
2014-06-10 12:16 ` Hans Verkuil
2014-06-10 15:57 ` Prabhakar Lad
2014-06-11 6:34 ` Sakari Ailus
2014-06-11 6:36 ` [PATCH v3.1 2/4] " Sakari Ailus
2014-06-11 7:58 ` Prabhakar Lad
2014-05-29 14:40 ` [PATCH v3 3/3] smiapp: Implement the test pattern control Sakari Ailus
2014-05-29 14:54 ` Laurent Pinchart
2014-05-29 15:01 ` Sakari Ailus
2014-05-29 15:14 ` Sakari Ailus
2014-05-29 15:16 ` [PATCH v3.1 " Sakari Ailus
2014-07-10 14:16 ` 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=48325310.Ydj7bxFi9C@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--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