From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, mchehab@redhat.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 1/2] v4l: Add new alpha component control
Date: Wed, 14 Dec 2011 14:34:14 +0100 [thread overview]
Message-ID: <4EE8A5D6.4030408@samsung.com> (raw)
In-Reply-To: <201112131318.54709.hverkuil@xs4all.nl>
Hi Hans,
On 12/13/2011 01:18 PM, Hans Verkuil wrote:
>> are you going to carry on with the control range update patches ?
>> I'd like to push the alpha colour control for v3.3 but it depends
>> on the controls framework updates now.
>
> Good question. I am not sure whether this is something we actually want. It
> would make applications much harder to write if the range of a control can
> suddenly change.
>
> On the other hand, it might be a good solution for a harder problem which is
> as yet unsolved: if you have multiple inputs, and each input has a different
> set of controls (e.g. one input is a SDTV receiver, the other is a HDTV
> receiver), then you can have the situation where e.g. the contrast control is
> present for both inputs, but with a different range. Switching inputs would
> then generate a control event telling the app that the range changed.
>
> But this may still be overkill...
Hmm, it doesn't look like an overkill to me. I'm certain there will be use
cases where control range update is needed. Maybe we could specify in
the API in what circumstances the control range update is allowed for drivers.
So not all applications need to handle the related events.
Nevertheless I won't be pushing on this, not to mess around in the whole
API because of some embedded systems requirements.
So I'm going to update the range for alpha control manually in the driver
for the time being.
>
> In other words, I don't know. Not helpful, I agree.
That was helpful anyway :-) Thanks.
--
Regards,
Sylwester
next prev parent reply other threads:[~2011-12-14 13:34 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 [this message]
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
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=4EE8A5D6.4030408@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.