From: Hans Verkuil <hansverk@cisco.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Antti Palosaari <crope@iki.fi>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media/v4l2-ctrls: Always run s_ctrl on volatile ctrls
Date: Tue, 17 Feb 2015 12:17:44 +0100 [thread overview]
Message-ID: <54E32358.8010303@cisco.com> (raw)
In-Reply-To: <1424170934-18619-1-git-send-email-ricardo.ribalda@gmail.com>
Hi Ricardo,
On 02/17/15 12:02, Ricardo Ribalda Delgado wrote:
> Volatile controls can change their value outside the v4l-ctrl framework.
>
> We should ignore the cached written value of the ctrl when evaluating if
> we should run s_ctrl.
>
> Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
> ---
>
> I have a control that tells the user when there has been a external trigger
> overrun. (Trigger while processing old image). This is a volatile control.
Does the application just read the control to check whether the trigger happened?
Or is the control perhaps changed by an interrupt handler?
> The user writes 0 to the control, to ack the error condition, and clear the
> hardware flag.
Would it be an idea to automatically ack the error condition when reading the
control?
Or, alternatively, have a separate button control to clear the condition.
>
> Unfortunately, it only works one time, because the next time the user writes
> a zero to the control cluster_changed returns false.
>
> I think on volatile controls it is safer to run s_ctrl twice than missing a
> valid s_ctrl.
>
> I know I am abusing a bit the API for this :P, but I also believe that the
> semantic here is a bit confusing.
The reason for that is that I have yet to see a convincing argument for
allowing s_ctrl for a volatile control.
Regards,
Hans
>
> drivers/media/v4l2-core/v4l2-ctrls.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c b/drivers/media/v4l2-core/v4l2-ctrls.c
> index 45c5b47..3d0c7f4 100644
> --- a/drivers/media/v4l2-core/v4l2-ctrls.c
> +++ b/drivers/media/v4l2-core/v4l2-ctrls.c
> @@ -1605,7 +1605,7 @@ static int cluster_changed(struct v4l2_ctrl *master)
>
> for (i = 0; i < master->ncontrols; i++) {
> struct v4l2_ctrl *ctrl = master->cluster[i];
> - bool ctrl_changed = false;
> + bool ctrl_changed = ctrl->flags & V4L2_CTRL_FLAG_VOLATILE;
>
> if (ctrl == NULL)
> continue;
>
next prev parent reply other threads:[~2015-02-17 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 11:02 [PATCH] media/v4l2-ctrls: Always run s_ctrl on volatile ctrls Ricardo Ribalda Delgado
2015-02-17 11:17 ` Hans Verkuil [this message]
2015-02-17 11:29 ` Ricardo Ribalda Delgado
2015-02-17 11:32 ` Sakari Ailus
2015-02-17 13:53 ` Jacek Anaszewski
2015-02-17 14:06 ` Sakari Ailus
2015-02-17 14:22 ` Jacek Anaszewski
2015-02-17 14:35 ` Sakari Ailus
2015-02-17 15:14 ` Jacek Anaszewski
2015-02-17 12:03 ` Hans Verkuil
2015-02-17 12:21 ` Ricardo Ribalda Delgado
2015-02-17 12:23 ` Hans Verkuil
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=54E32358.8010303@cisco.com \
--to=hansverk@cisco.com \
--cc=crope@iki.fi \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=ricardo.ribalda@gmail.com \
--cc=s.nawrocki@samsung.com \
--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