mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	linux-media@vger.kernel.org,
	Javier Martinez Canillas <javier@osg.samsung.com>
Subject: [PATCH 1/8] [media] v4l2-subdev: add registered_async subdev core operation
Date: Fri,  5 Feb 2016 16:09:51 -0300	[thread overview]
Message-ID: <1454699398-8581-2-git-send-email-javier@osg.samsung.com> (raw)
In-Reply-To: <1454699398-8581-1-git-send-email-javier@osg.samsung.com>

V4L2 sub-devices that are registered asynchronously have no way to know
when they have been registration with a V4L2 device but they might need
to take some action after this.

So let's add a callback that can be executed by the V4L2 async core to
allow sub-devices drivers to do any needed initialization that depends
on the registration.

Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
---

 include/media/v4l2-subdev.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/include/media/v4l2-subdev.h b/include/media/v4l2-subdev.h
index b273cf9ac047..11e2dfec0198 100644
--- a/include/media/v4l2-subdev.h
+++ b/include/media/v4l2-subdev.h
@@ -179,6 +179,8 @@ struct v4l2_subdev_io_pin_config {
  *		     for it to be warned when the value of a control changes.
  *
  * @unsubscribe_event: remove event subscription from the control framework.
+ *
+ * @registered_async: the subdevice has been registered async.
  */
 struct v4l2_subdev_core_ops {
 	int (*log_status)(struct v4l2_subdev *sd);
@@ -211,6 +213,7 @@ struct v4l2_subdev_core_ops {
 			       struct v4l2_event_subscription *sub);
 	int (*unsubscribe_event)(struct v4l2_subdev *sd, struct v4l2_fh *fh,
 				 struct v4l2_event_subscription *sub);
+	int (*registered_async)(struct v4l2_subdev *sd);
 };
 
 /**
-- 
2.5.0

  reply	other threads:[~2016-02-05 19:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 19:09 [PATCH 0/8] [media] tvp5150: add HW input connectors support Javier Martinez Canillas
2016-02-05 19:09 ` Javier Martinez Canillas [this message]
2016-02-05 19:09 ` [PATCH 2/8] [media] v4l2-async: call registered_async after subdev registration Javier Martinez Canillas
2016-08-11 11:10   ` Sakari Ailus
2016-08-11 11:18     ` Sakari Ailus
2016-08-11 16:14       ` Javier Martinez Canillas
2016-08-11 19:28         ` Sakari Ailus
2016-02-05 19:09 ` [PATCH 3/8] [media] tvp5150: put endpoint node on error Javier Martinez Canillas
2016-02-05 19:09 ` [PATCH 4/8] [media] tvp5150: store dev id and rom version Javier Martinez Canillas
2016-02-05 19:09 ` [PATCH 5/8] [media] tvp5150: add internal signal generator to HW input list Javier Martinez Canillas
2016-02-05 19:09 ` [PATCH 6/8] [media] tvp5150: move input definition header to dt-bindings Javier Martinez Canillas
2016-02-05 19:09 ` [PATCH 7/8] [media] tvp5150: document input connectors DT bindings Javier Martinez Canillas
2016-02-08 18:23   ` Javier Martinez Canillas
2016-02-05 19:09 ` [PATCH 8/8] [media] tvp5150: add HW input connectors support Javier Martinez Canillas

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=1454699398-8581-2-git-send-email-javier@osg.samsung.com \
    --to=javier@osg.samsung.com \
    --cc=hans.verkuil@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®