From: "Sebastian Süsens" <su@mycable.de>
To: linux-media@vger.kernel.org
Subject: v4l controls API
Date: Mon, 3 Dec 2018 09:02:21 +0100 (CET) [thread overview]
Message-ID: <927806392.2404.1543824141142.JavaMail.zimbra@mycable.de> (raw)
Hello,
I don't know how to get access to the v4l controls on a I2C camera sensor.
My driver structure looks following:
bridge driver -> csi-driver -> sensor driver (includes controls)
register-async-notifer for csi driver register-async-notifer for sensor driver
register video device
The v4l2 API say:
When a sub-device is registered with a V4L2 driver by calling v4l2_device_register_subdev() and the ctrl_handler fields of both v4l2_subdev and v4l2_device are set, then the controls of the subdev will become automatically available in the V4L2 driver as well. If the subdev driver contains controls that already exist in the V4L2 driver, then those will be skipped (so a V4L2 driver can always override a subdev control).
But how can I get access to the controls by asynchronous registration, because the controls are not added to the video device automatically?
Normally I can use:
v4l2-ctl -l -d /dev/video0
I don't know if this forum is the right place for this question, so please answer with a private e-mail su@mycable.de
------------------------------------------------------------------------
Sebastian Süsens Tel. +49 4321 559 56-27
mycable GmbH Fax +49 4321 559 56-10
Gartenstrasse 10
24534 Neumuenster, Germany Email su@mycable.de
------------------------------------------------------------------------
mycable GmbH, Managing Director: Michael Carstens-Behrens
USt-IdNr: DE 214 231 199, Amtsgericht Kiel, HRB 1797 NM
------------------------------------------------------------------------
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. If you have received this e-mail in error,
please notify the sender and delete all copies from your system.
------------------------------------------------------------------------
next reply other threads:[~2018-12-03 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 8:02 Sebastian Süsens [this message]
2018-12-03 8:29 ` v4l controls API Hans Verkuil
2018-12-03 10:03 ` Sebastian Süsens
2018-12-03 10:06 ` Hans Verkuil
2018-12-03 11:26 ` Sebastian Süsens
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=927806392.2404.1543824141142.JavaMail.zimbra@mycable.de \
--to=su@mycable.de \
--cc=linux-media@vger.kernel.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 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.