From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, mchehab@redhat.com,
laurent.pinchart@ideasonboard.com, m.szyprowski@samsung.com,
jonghun.han@samsung.com, riverful.kim@samsung.com,
sw0312.kim@samsung.com, Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2 2/2] s5p-fimc: Add support for alpha component configuration
Date: Mon, 28 Nov 2011 13:17:06 +0100 [thread overview]
Message-ID: <4ED37BC2.60205@samsung.com> (raw)
In-Reply-To: <201111281242.17246.hverkuil@xs4all.nl>
On 11/28/2011 12:42 PM, Hans Verkuil wrote:
> On Friday 25 November 2011 16:39:32 Sylwester Nawrocki wrote:
>> On Exynos SoCs the FIMC IP allows to configure globally the alpha
>> component of all pixels for V4L2_PIX_FMT_RGB32, V4L2_PIX_FMT_RGB555
>> and V4L2_PIX_FMT_RGB444 image formats. This patch adds a v4l2 control
>> in order to let the applications control the alpha component value.
>>
>> The alpha value range depends on the pixel format, for RGB32 it's
>> 0..255 (8-bits), for RGB555 - 0..1 (1-bit) and for RGB444 - 0..15
>> (4-bits). The v4l2 control range is always 0..255 and the alpha
>> component data width is determined by currently set format on the
>> V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE buffer queue. The applications
>> need to match the alpha channel data width and the pixel format
>> since the driver will ignore the alpha component bits that are not
>> applicable to the configured pixel format.
>
> Will the driver ignore the least significant bits or the most significant
> bits?
Most significant bits will be ignored, i.e. depending on fourcc the valid
alpha bits are:
V4L2_PIX_FMT_RGB555 - [0]
V4L2_PIX_FMT_RGB444 - [3:0]
V4L2_PIX_FMT_RGB32 - [7:0]
--
Regards,
Sylwester
prev parent reply other threads:[~2011-11-28 12:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 15:39 [PATCH/RFC v2] Add new V4L2_CID_ALPHA_COMPONENT control Sylwester Nawrocki
2011-11-25 15:39 ` [PATCH v2 1/2] v4l: Add new alpha component control Sylwester Nawrocki
2011-11-28 11:09 ` Laurent Pinchart
2011-11-28 11:38 ` Hans Verkuil
2011-11-28 12:13 ` Sylwester Nawrocki
2011-11-28 12:39 ` Hans Verkuil
2011-11-28 13:02 ` Sylwester Nawrocki
2011-11-29 11:08 ` Hans Verkuil
2011-11-29 16:40 ` Sylwester Nawrocki
2011-11-29 18:10 ` Laurent Pinchart
2011-11-29 18:30 ` Hans Verkuil
2011-11-29 18:58 ` Laurent Pinchart
2011-12-08 9:30 ` Sylwester Nawrocki
2011-12-08 10:30 ` Laurent Pinchart
2011-12-08 12:30 ` Sylwester Nawrocki
2011-12-13 12:18 ` Hans Verkuil
2011-12-14 13:34 ` Sylwester Nawrocki
2011-12-14 14:42 ` [PATCH/RFC v4 0/2] Add new V4L2_CID_ALPHA_COMPONENT control Sylwester Nawrocki
2011-12-14 14:42 ` [PATCH v4 1/2] v4l: Add new alpha component control Sylwester Nawrocki
2011-12-14 14:42 ` [PATCH v4 2/2] s5p-fimc: Add support for alpha component configuration Sylwester Nawrocki
2011-12-14 14:53 ` [PATCH v2 1/2] v4l: Add new alpha component control Hans Verkuil
2011-11-29 19:39 ` Sylwester Nawrocki
2011-11-30 1:40 ` Laurent Pinchart
2011-11-25 15:39 ` [PATCH v2 2/2] s5p-fimc: Add support for alpha component configuration Sylwester Nawrocki
2011-11-28 11:42 ` Hans Verkuil
2011-11-28 12:17 ` Sylwester Nawrocki [this message]
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=4ED37BC2.60205@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=jonghun.han@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@redhat.com \
--cc=riverful.kim@samsung.com \
--cc=sw0312.kim@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.