From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 2/8] [media] v4l2-async: call registered_async after subdev registration
Date: Thu, 11 Aug 2016 12:14:01 -0400 [thread overview]
Message-ID: <7c4b87b3-38e9-6b4e-730e-d65b0d72dd1d@osg.samsung.com> (raw)
In-Reply-To: <20160811111817.GS3182@valkosipuli.retiisi.org.uk>
Hello Sakari,
Thanks a lot for your feedback.
On 08/11/2016 07:18 AM, Sakari Ailus wrote:
> On Thu, Aug 11, 2016 at 02:10:43PM +0300, Sakari Ailus wrote:
[snip]
>>>
>>> + ret = v4l2_subdev_call(sd, core, registered_async);
>>> + if (ret < 0) {
>>> + if (notifier->unbind)
>>> + notifier->unbind(notifier, sd, asd);
>>> + return ret;
>>> + }
>>> +
>>> if (list_empty(¬ifier->waiting) && notifier->complete)
>>> return notifier->complete(notifier);
>>
>> I noticed this just now but what do you need this and the next patch for?
>>
>> We already have a callback for the same purpose: it's
>> v4l2_subdev_ops.internal_ops.registered(). And there's similar
>> unregistered() callback as well.
>>
Oh, I missed we already had those calls. When adding the connector
support, I looked at struct v4l2_subdev_core_ops and didn't find a
callback that fit but didn't notice we already had a .registered()
in struct struct v4l2_subdev_internal_ops. Sorry about that...
>> Could you use these callbacks instead?
Yes, those can be used indeed. I'll post patches using that instead
and removing the .registered_async callback since as you said isn't
really needed.
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2016-08-11 16:14 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 ` [PATCH 1/8] [media] v4l2-subdev: add registered_async subdev core operation Javier Martinez Canillas
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 [this message]
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=7c4b87b3-38e9-6b4e-730e-d65b0d72dd1d@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 \
--cc=sakari.ailus@iki.fi \
/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®