Re: [PATCH] v4l2-async: add subnotifier registration for subdevices
Hej Sakari,
Tack för dina kommentarer.
On 2017-05-03 22:51:46 +0300, Sakari Ailus wrote:
> Hejssan!
>
> On Fri, Apr 28, 2017 at 01:47:48PM +0200, Niklas Söderlund wrote:
> > On 2017-04-28 13:28:17 +0300, Sakari Ailus wrote:
> > > Hi Niklas,
> > >
> > > Thank you for the patch.
> > >
> > > Do you happen to have a driver that would use this, to see some example of
> > > how the code is to be used?
> >
> > Yes, the latest R-Car CSI-2 series make use of this, see:
> >
> > https://www.spinics.net/lists/linux-renesas-soc/msg13693.html
>
> Ah, thanks. I'll take a look at that --- which should do for other reasons
> as well...
>
> ...
>
> > > > +
> > > > + /*
> > > > +* This function can be called recursively so the list
> > > > +* might be modified in a recursive call. Start from the
> > > > +* top of the list each iteration.
> > > > +*/
> > > > + found = 1;
> > > > + while (found) {
> > > > + found = 0;
> > > >
> > > > - list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> > > > - int ret;
> > > > + list_for_each_entry_safe(sd, tmp, &subdev_list,
> > > > async_list) {
> > > > + int ret;
> > > >
> > > > - asd = v4l2_async_belongs(notifier, sd);
> > > > - if (!asd)
> > > > - continue;
> > > > + asd = v4l2_async_belongs(notifier, sd);
> > > > + if (!asd)
> > > > + continue;
> > > >
> > > > - ret = v4l2_async_test_notify(notifier, sd, asd);
> > > > - if (ret < 0) {
> > > > - mutex_unlock(&list_lock);
> > > > - return ret;
> > > > + ret = v4l2_async_test_notify(notifier, sd, asd);
> > > > + if (ret < 0) {
> > > > + if (!subnotifier)
> > > > + mutex_unlock(&list_lock);
> > > > + return ret;
> > > > + }
> > > > +
> > > > + found = 1;
> > > > + break;
> > > > }
> > > > }
> > > >
> > > > /* Keep also completed notifiers on the list */
> > > > list_add(¬ifier->list, ¬ifier_list);
> > > >
> > > > - mutex_unlock(&list_lock);
> > > > + if (!subnotifier)
> > > > + mutex_unlock(&list_lock);
> > > >
> > > > return 0;
> > > > }
> > > > +
> > > > +int v4l2_async_subnotifier_register(struct v4l2_subdev *sd,
> > > > + struct v4l2_async_notifier
> > > > *notifier)
> > > > +{
> > > > + if (!sd->v4l2_dev) {
> > > > + dev_err(sd->dev ? sd->dev : NULL,
>
> sd->dev is enough.
Thanks, but I think i will drop the dev_err() all together and just
return -EINVAL once i move this to what will be called
v4l2_async_do_notifier_register() as you suggest bellow.
>
> > > > + "Can't register subnotifier for without
> > > > v4l2_dev\n");
> > > > + return -EINVAL;
> > >
> > > When did this start happening? :-)
> >
> > What do you mean? I'm not sure I understand this comment.
>
> Uh, right. So the caller simply needs to specify v4l2_dev? The same applies
> to v4l2_async_notifier_register() which does not test that --- but it
> should.
>
> How about adding this change in a separate patch to what will be called
> v4l2_async_do_notifier_register()?
I agree, I will do this in a separate patch before I add the
v4l2_async_subnotifier_register().
>
> >
> > >
> > > > + }
> > > > +
> > > > + return v4l2_async_do_notifier_register(sd->v4l2_dev, notifier,
> > > > true);
> > > > +}
> > > > +EXPORT_SYMBOL(v4l2_async_subnotifier_register);
> > > > +
> > > > +int v4l2_async_notifier_register(struct v4l2_device *v4l2_dev,
> > > > +struct v4l2_async_notifier *notifier)
> > > > +{
> > > > + return v4l2_async_do_notifier_register(v4l2_dev, notifier,
> > > > false);
> > > > +}
> > > > EXPORT_SYMBOL(v4l2_async_notifier_register);
> > > >
> > > > -void v4l2_async_notifier_unregister(struct v4l2_async_notifier
> > > > *notifier)
> > > > +static void
> > > > +v4l2_async_do_notifier_unregister(struct v4l2_async_notifier *notifier,
> > > > + bool subnotifier)
> > > > {
> > > > struct v4l2_subdev *sd, *tmp;
> > > > unsigned int notif_n_subdev = notifier->num_subdevs;
> > > > @@ -210,7 +248,8 @@ void v4l2_async_notifier_unregister(struct
> > > > v4l2_async_notifier *notifier)
> > > > "Failed to allocate device cache!\n");
> > > > }
> > > >
> > > > - mutex_lock(&list_lock);
> > > > + if (!subnotifier)
> > > > + mutex_lock(&list_lock);
> > > >
> > > > list_del(¬ifier->list);
> > > >
Re: [PATCH] v4l2-async: add subnotifier registration for subdevices
Hi Kieran,
Thanks for your feedback.
On 2017-05-03 18:07:47 +0100, Kieran Bingham wrote:
> Hi Niklas,
>
> Small thing to ponder discovered below:
>
> On 27/04/17 23:30, Niklas Söderlund wrote:
> > When registered() of v4l2_subdev_internal_ops is called the subdevice
> > have access to the master devices v4l2_dev and it's called with the
> > async frameworks list_lock held. In this context the subdevice can
> > register its own notifiers to allow for incremental discovery of
> > subdevices.
> >
> > The master device registers the subdevices closest to itself in its
> > notifier while the subdevice(s) themself register notifiers for there
> > closest neighboring devices when they are registered. Using this
> > incremental approach two problems can be solved.
> >
> > 1. The master device no longer have to care how many subdevices exist in
> >the pipeline. It only needs to care about its closest subdevice and
> >arbitrary long pipelines can be created without having to adapt the
> >master device for each case.
> >
> > 2. Subdevices which are represented as a single DT node but register
> >more then one subdevice can use this to further the pipeline
> >discovery. Since the subdevice driver is the only one who knows which
> >of its subdevices is linked with which subdevice of a neighboring DT
> >node.
> >
> > To enable subdevices to register/unregister notifiers from the
> > registered()/unregistered() callback v4l2_async_subnotifier_register()
> > and v4l2_async_subnotifier_unregister() are added. These new notifier
> > register functions are similar to the master device equivalent functions
> > but run without taking the v4l2-async list_lock which already are held
> > when he registered()/unregistered() callbacks are called.
> >
> > Signed-off-by: Niklas Söderlund
> > ---
> > drivers/media/v4l2-core/v4l2-async.c | 91
> > +---
> > include/media/v4l2-async.h | 22 +
> > 2 files changed, 95 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/media/v4l2-core/v4l2-async.c
> > b/drivers/media/v4l2-core/v4l2-async.c
> > index 96cc733f35ef72b0..d4a676a2935eb058 100644
> > --- a/drivers/media/v4l2-core/v4l2-async.c
> > +++ b/drivers/media/v4l2-core/v4l2-async.c
> > @@ -136,12 +136,13 @@ static void v4l2_async_cleanup(struct v4l2_subdev *sd)
> > sd->dev = NULL;
> > }
> >
> > -int v4l2_async_notifier_register(struct v4l2_device *v4l2_dev,
> > -struct v4l2_async_notifier *notifier)
> > +static int v4l2_async_do_notifier_register(struct v4l2_device *v4l2_dev,
> > + struct v4l2_async_notifier *notifier,
> > + bool subnotifier)
> > {
> > struct v4l2_subdev *sd, *tmp;
> > struct v4l2_async_subdev *asd;
> > - int i;
> > + int found, i;
> >
> > if (!notifier->num_subdevs || notifier->num_subdevs > V4L2_MAX_SUBDEVS)
> > return -EINVAL;
> > @@ -168,32 +169,69 @@ int v4l2_async_notifier_register(struct v4l2_device
> > *v4l2_dev,
> > list_add_tail(&asd->list, ¬ifier->waiting);
> > }
> >
> > - mutex_lock(&list_lock);
> > + if (!subnotifier)
> > + mutex_lock(&list_lock);
> > +
> > + /*
> > +* This function can be called recursively so the list
> > +* might be modified in a recursive call. Start from the
> > +* top of the list each iteration.
> > +*/
> > + found = 1;
> > + while (found) {
> > + found = 0;
> >
> > - list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> > - int ret;
> > + list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> > + int ret;
> >
> > - asd = v4l2_async_belongs(notifier, sd);
> > - if (!asd)
> > - continue;
> > + asd = v4l2_async_belongs(notifier, sd);
> > + if (!asd)
> > + continue;
> >
> > - ret = v4l2_async_test_notify(notifier, sd, asd);
> > - if (ret < 0) {
> > - mutex_unlock(&list_lock);
> > - return ret;
> > + ret = v4l2_async_test_notify(notifier, sd, asd);
> > + if (ret < 0) {
> > + if (!subnotifier)
> > + mutex_unlock(&list_lock);
> > + return ret;
> > + }
> > +
> > + found = 1;
> > + break;
> > }
> > }
> >
> > /* Keep also completed notifiers on the list */
> > list_add(¬ifier->list, ¬ifier_list);
> >
> > - mutex_unlock(&list_lock);
> > + if (!subnotifier)
> > + mutex_unlock(&list_lock);
> >
> > return 0;
> > }
> > +
> > +int v4l2_async_subnotifier_register(struct v4l2_subdev *sd,
> > + struct v4l2_async_notifier *notifier)
> > +{
Re: [PATCH] v4l2-async: add subnotifier registration for subdevices
Hejssan!
On Fri, Apr 28, 2017 at 01:47:48PM +0200, Niklas Söderlund wrote:
> On 2017-04-28 13:28:17 +0300, Sakari Ailus wrote:
> > Hi Niklas,
> >
> > Thank you for the patch.
> >
> > Do you happen to have a driver that would use this, to see some example of
> > how the code is to be used?
>
> Yes, the latest R-Car CSI-2 series make use of this, see:
>
> https://www.spinics.net/lists/linux-renesas-soc/msg13693.html
Ah, thanks. I'll take a look at that --- which should do for other reasons
as well...
...
> > > +
> > > + /*
> > > + * This function can be called recursively so the list
> > > + * might be modified in a recursive call. Start from the
> > > + * top of the list each iteration.
> > > + */
> > > + found = 1;
> > > + while (found) {
> > > + found = 0;
> > >
> > > - list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> > > - int ret;
> > > + list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> > > + int ret;
> > >
> > > - asd = v4l2_async_belongs(notifier, sd);
> > > - if (!asd)
> > > - continue;
> > > + asd = v4l2_async_belongs(notifier, sd);
> > > + if (!asd)
> > > + continue;
> > >
> > > - ret = v4l2_async_test_notify(notifier, sd, asd);
> > > - if (ret < 0) {
> > > - mutex_unlock(&list_lock);
> > > - return ret;
> > > + ret = v4l2_async_test_notify(notifier, sd, asd);
> > > + if (ret < 0) {
> > > + if (!subnotifier)
> > > + mutex_unlock(&list_lock);
> > > + return ret;
> > > + }
> > > +
> > > + found = 1;
> > > + break;
> > > }
> > > }
> > >
> > > /* Keep also completed notifiers on the list */
> > > list_add(¬ifier->list, ¬ifier_list);
> > >
> > > - mutex_unlock(&list_lock);
> > > + if (!subnotifier)
> > > + mutex_unlock(&list_lock);
> > >
> > > return 0;
> > > }
> > > +
> > > +int v4l2_async_subnotifier_register(struct v4l2_subdev *sd,
> > > + struct v4l2_async_notifier *notifier)
> > > +{
> > > + if (!sd->v4l2_dev) {
> > > + dev_err(sd->dev ? sd->dev : NULL,
sd->dev is enough.
> > > + "Can't register subnotifier for without v4l2_dev\n");
> > > + return -EINVAL;
> >
> > When did this start happening? :-)
>
> What do you mean? I'm not sure I understand this comment.
Uh, right. So the caller simply needs to specify v4l2_dev? The same applies
to v4l2_async_notifier_register() which does not test that --- but it
should.
How about adding this change in a separate patch to what will be called
v4l2_async_do_notifier_register()?
>
> >
> > > + }
> > > +
> > > + return v4l2_async_do_notifier_register(sd->v4l2_dev, notifier, true);
> > > +}
> > > +EXPORT_SYMBOL(v4l2_async_subnotifier_register);
> > > +
> > > +int v4l2_async_notifier_register(struct v4l2_device *v4l2_dev,
> > > + struct v4l2_async_notifier *notifier)
> > > +{
> > > + return v4l2_async_do_notifier_register(v4l2_dev, notifier, false);
> > > +}
> > > EXPORT_SYMBOL(v4l2_async_notifier_register);
> > >
> > > -void v4l2_async_notifier_unregister(struct v4l2_async_notifier *notifier)
> > > +static void
> > > +v4l2_async_do_notifier_unregister(struct v4l2_async_notifier *notifier,
> > > + bool subnotifier)
> > > {
> > > struct v4l2_subdev *sd, *tmp;
> > > unsigned int notif_n_subdev = notifier->num_subdevs;
> > > @@ -210,7 +248,8 @@ void v4l2_async_notifier_unregister(struct
> > > v4l2_async_notifier *notifier)
> > > "Failed to allocate device cache!\n");
> > > }
> > >
> > > - mutex_lock(&list_lock);
> > > + if (!subnotifier)
> > > + mutex_lock(&list_lock);
> > >
> > > list_del(¬ifier->list);
> > >
> > > @@ -237,15 +276,20 @@ void v4l2_async_notifier_unregister(struct
> > > v4l2_async_notifier *notifier)
> > > put_device(d);
> > > }
> > >
> > > - mutex_unlock(&list_lock);
> > > + if (!subnotifier)
> > > + mutex_unlock(&list_lock);
> > >
> > > /*
> > >* Call device_attach() to reprobe devices
> > >*
> > >* NOTE: If dev allocation fails, i is 0, and the whole loop won't be
> > >* executed.
> > > + * TODO: If we are unregistering a subdevice notifier we can't reprobe
> > > + * since the lock_list is held by the master device and attaching that
> > > + * device would call v4l2_async_register_subdev() and end in a deadlock
> > > + * on list_lock.
> > >*/
> > > - while (i--) {
> > > + while (i-- && !subnotifier) {
> >
> > Why is this not done for sub-notifiers?
> >
> > That said, the code here looks really dubious. But that's out of scope of
> > the patchset.
>
> I try to explain this in the comment above :-)
>
> If this is called
Re: [PATCH] v4l2-async: add subnotifier registration for subdevices
Hi Niklas,
Small thing to ponder discovered below:
On 27/04/17 23:30, Niklas Söderlund wrote:
> When registered() of v4l2_subdev_internal_ops is called the subdevice
> have access to the master devices v4l2_dev and it's called with the
> async frameworks list_lock held. In this context the subdevice can
> register its own notifiers to allow for incremental discovery of
> subdevices.
>
> The master device registers the subdevices closest to itself in its
> notifier while the subdevice(s) themself register notifiers for there
> closest neighboring devices when they are registered. Using this
> incremental approach two problems can be solved.
>
> 1. The master device no longer have to care how many subdevices exist in
>the pipeline. It only needs to care about its closest subdevice and
>arbitrary long pipelines can be created without having to adapt the
>master device for each case.
>
> 2. Subdevices which are represented as a single DT node but register
>more then one subdevice can use this to further the pipeline
>discovery. Since the subdevice driver is the only one who knows which
>of its subdevices is linked with which subdevice of a neighboring DT
>node.
>
> To enable subdevices to register/unregister notifiers from the
> registered()/unregistered() callback v4l2_async_subnotifier_register()
> and v4l2_async_subnotifier_unregister() are added. These new notifier
> register functions are similar to the master device equivalent functions
> but run without taking the v4l2-async list_lock which already are held
> when he registered()/unregistered() callbacks are called.
>
> Signed-off-by: Niklas Söderlund
> ---
> drivers/media/v4l2-core/v4l2-async.c | 91
> +---
> include/media/v4l2-async.h | 22 +
> 2 files changed, 95 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/media/v4l2-core/v4l2-async.c
> b/drivers/media/v4l2-core/v4l2-async.c
> index 96cc733f35ef72b0..d4a676a2935eb058 100644
> --- a/drivers/media/v4l2-core/v4l2-async.c
> +++ b/drivers/media/v4l2-core/v4l2-async.c
> @@ -136,12 +136,13 @@ static void v4l2_async_cleanup(struct v4l2_subdev *sd)
> sd->dev = NULL;
> }
>
> -int v4l2_async_notifier_register(struct v4l2_device *v4l2_dev,
> - struct v4l2_async_notifier *notifier)
> +static int v4l2_async_do_notifier_register(struct v4l2_device *v4l2_dev,
> +struct v4l2_async_notifier *notifier,
> +bool subnotifier)
> {
> struct v4l2_subdev *sd, *tmp;
> struct v4l2_async_subdev *asd;
> - int i;
> + int found, i;
>
> if (!notifier->num_subdevs || notifier->num_subdevs > V4L2_MAX_SUBDEVS)
> return -EINVAL;
> @@ -168,32 +169,69 @@ int v4l2_async_notifier_register(struct v4l2_device
> *v4l2_dev,
> list_add_tail(&asd->list, ¬ifier->waiting);
> }
>
> - mutex_lock(&list_lock);
> + if (!subnotifier)
> + mutex_lock(&list_lock);
> +
> + /*
> + * This function can be called recursively so the list
> + * might be modified in a recursive call. Start from the
> + * top of the list each iteration.
> + */
> + found = 1;
> + while (found) {
> + found = 0;
>
> - list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> - int ret;
> + list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> + int ret;
>
> - asd = v4l2_async_belongs(notifier, sd);
> - if (!asd)
> - continue;
> + asd = v4l2_async_belongs(notifier, sd);
> + if (!asd)
> + continue;
>
> - ret = v4l2_async_test_notify(notifier, sd, asd);
> - if (ret < 0) {
> - mutex_unlock(&list_lock);
> - return ret;
> + ret = v4l2_async_test_notify(notifier, sd, asd);
> + if (ret < 0) {
> + if (!subnotifier)
> + mutex_unlock(&list_lock);
> + return ret;
> + }
> +
> + found = 1;
> + break;
> }
> }
>
> /* Keep also completed notifiers on the list */
> list_add(¬ifier->list, ¬ifier_list);
>
> - mutex_unlock(&list_lock);
> + if (!subnotifier)
> + mutex_unlock(&list_lock);
>
> return 0;
> }
> +
> +int v4l2_async_subnotifier_register(struct v4l2_subdev *sd,
> + struct v4l2_async_notifier *notifier)
> +{
> + if (!sd->v4l2_dev) {
> + dev_err(sd->dev ? sd->dev : NULL,
Just came across this, and it seems a bit 'extraneous'
'If sd->dev is not null, use sd->dev, otherwise use NULL'
--
KB
> +
Re: [PATCH] v4l2-async: add subnotifier registration for subdevices
Hi Sakari,
Thanks for your feedback.
On 2017-04-28 13:28:17 +0300, Sakari Ailus wrote:
> Hi Niklas,
>
> Thank you for the patch.
>
> Do you happen to have a driver that would use this, to see some example of
> how the code is to be used?
Yes, the latest R-Car CSI-2 series make use of this, see:
https://www.spinics.net/lists/linux-renesas-soc/msg13693.html
>
> Could you update the documentation in
> Documentation/media/kapi/v4l2-subdev.rst, too?
Yes will do so for the next version, thanks for reminding me.
>
> On Fri, Apr 28, 2017 at 12:30:35AM +0200, Niklas Söderlund wrote:
> > When registered() of v4l2_subdev_internal_ops is called the subdevice
> > have access to the master devices v4l2_dev and it's called with the
> > async frameworks list_lock held. In this context the subdevice can
> > register its own notifiers to allow for incremental discovery of
> > subdevices.
> >
> > The master device registers the subdevices closest to itself in its
> > notifier while the subdevice(s) themself register notifiers for there
> > closest neighboring devices when they are registered. Using this
> > incremental approach two problems can be solved.
> >
> > 1. The master device no longer have to care how many subdevices exist in
>
> s/subdevices/devices/ ?
>
> A single sub-device driver can expose multiple sub-devices for a single
> device.
Thanks.
>
> >the pipeline. It only needs to care about its closest subdevice and
> >arbitrary long pipelines can be created without having to adapt the
> >master device for each case.
> >
> > 2. Subdevices which are represented as a single DT node but register
> >more then one subdevice can use this to further the pipeline
> >discovery. Since the subdevice driver is the only one who knows which
> >of its subdevices is linked with which subdevice of a neighboring DT
> >node.
> >
> > To enable subdevices to register/unregister notifiers from the
> > registered()/unregistered() callback v4l2_async_subnotifier_register()
> > and v4l2_async_subnotifier_unregister() are added. These new notifier
> > register functions are similar to the master device equivalent functions
> > but run without taking the v4l2-async list_lock which already are held
> > when he registered()/unregistered() callbacks are called.
> >
> > Signed-off-by: Niklas Söderlund
> > ---
> > drivers/media/v4l2-core/v4l2-async.c | 91
> > +---
> > include/media/v4l2-async.h | 22 +
> > 2 files changed, 95 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/media/v4l2-core/v4l2-async.c
> > b/drivers/media/v4l2-core/v4l2-async.c
> > index 96cc733f35ef72b0..d4a676a2935eb058 100644
> > --- a/drivers/media/v4l2-core/v4l2-async.c
> > +++ b/drivers/media/v4l2-core/v4l2-async.c
> > @@ -136,12 +136,13 @@ static void v4l2_async_cleanup(struct v4l2_subdev *sd)
> > sd->dev = NULL;
> > }
> >
> > -int v4l2_async_notifier_register(struct v4l2_device *v4l2_dev,
> > -struct v4l2_async_notifier *notifier)
> > +static int v4l2_async_do_notifier_register(struct v4l2_device *v4l2_dev,
> > + struct v4l2_async_notifier *notifier,
> > + bool subnotifier)
> > {
> > struct v4l2_subdev *sd, *tmp;
> > struct v4l2_async_subdev *asd;
> > - int i;
> > + int found, i;
>
> If you need a boolean value, you could use bool type.
Will update to use bool in next version.
>
> >
> > if (!notifier->num_subdevs || notifier->num_subdevs > V4L2_MAX_SUBDEVS)
> > return -EINVAL;
> > @@ -168,32 +169,69 @@ int v4l2_async_notifier_register(struct v4l2_device
> > *v4l2_dev,
> > list_add_tail(&asd->list, ¬ifier->waiting);
> > }
> >
> > - mutex_lock(&list_lock);
> > + if (!subnotifier)
> > + mutex_lock(&list_lock);
>
> Just to be sure, I'd verify the mutex is indeed acquired.
> lockdep_assert_held(mutex) ?
Neat, was not aware of this function. Will use in next version.
>
> > +
> > + /*
> > +* This function can be called recursively so the list
> > +* might be modified in a recursive call. Start from the
> > +* top of the list each iteration.
> > +*/
> > + found = 1;
> > + while (found) {
> > + found = 0;
> >
> > - list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> > - int ret;
> > + list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> > + int ret;
> >
> > - asd = v4l2_async_belongs(notifier, sd);
> > - if (!asd)
> > - continue;
> > + asd = v4l2_async_belongs(notifier, sd);
> > + if (!asd)
> > + continue;
> >
> > - ret = v4l2_async_test_notify(notifier, sd, asd);
> > - if (ret < 0) {
> > - mutex_unlock(&list_lock);
> > - return ret;
> >
Re: [PATCH] v4l2-async: add subnotifier registration for subdevices
Hi Niklas,
Thank you for the patch.
Do you happen to have a driver that would use this, to see some example of
how the code is to be used?
Could you update the documentation in
Documentation/media/kapi/v4l2-subdev.rst, too?
On Fri, Apr 28, 2017 at 12:30:35AM +0200, Niklas Söderlund wrote:
> When registered() of v4l2_subdev_internal_ops is called the subdevice
> have access to the master devices v4l2_dev and it's called with the
> async frameworks list_lock held. In this context the subdevice can
> register its own notifiers to allow for incremental discovery of
> subdevices.
>
> The master device registers the subdevices closest to itself in its
> notifier while the subdevice(s) themself register notifiers for there
> closest neighboring devices when they are registered. Using this
> incremental approach two problems can be solved.
>
> 1. The master device no longer have to care how many subdevices exist in
s/subdevices/devices/ ?
A single sub-device driver can expose multiple sub-devices for a single
device.
>the pipeline. It only needs to care about its closest subdevice and
>arbitrary long pipelines can be created without having to adapt the
>master device for each case.
>
> 2. Subdevices which are represented as a single DT node but register
>more then one subdevice can use this to further the pipeline
>discovery. Since the subdevice driver is the only one who knows which
>of its subdevices is linked with which subdevice of a neighboring DT
>node.
>
> To enable subdevices to register/unregister notifiers from the
> registered()/unregistered() callback v4l2_async_subnotifier_register()
> and v4l2_async_subnotifier_unregister() are added. These new notifier
> register functions are similar to the master device equivalent functions
> but run without taking the v4l2-async list_lock which already are held
> when he registered()/unregistered() callbacks are called.
>
> Signed-off-by: Niklas Söderlund
> ---
> drivers/media/v4l2-core/v4l2-async.c | 91
> +---
> include/media/v4l2-async.h | 22 +
> 2 files changed, 95 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/media/v4l2-core/v4l2-async.c
> b/drivers/media/v4l2-core/v4l2-async.c
> index 96cc733f35ef72b0..d4a676a2935eb058 100644
> --- a/drivers/media/v4l2-core/v4l2-async.c
> +++ b/drivers/media/v4l2-core/v4l2-async.c
> @@ -136,12 +136,13 @@ static void v4l2_async_cleanup(struct v4l2_subdev *sd)
> sd->dev = NULL;
> }
>
> -int v4l2_async_notifier_register(struct v4l2_device *v4l2_dev,
> - struct v4l2_async_notifier *notifier)
> +static int v4l2_async_do_notifier_register(struct v4l2_device *v4l2_dev,
> +struct v4l2_async_notifier *notifier,
> +bool subnotifier)
> {
> struct v4l2_subdev *sd, *tmp;
> struct v4l2_async_subdev *asd;
> - int i;
> + int found, i;
If you need a boolean value, you could use bool type.
>
> if (!notifier->num_subdevs || notifier->num_subdevs > V4L2_MAX_SUBDEVS)
> return -EINVAL;
> @@ -168,32 +169,69 @@ int v4l2_async_notifier_register(struct v4l2_device
> *v4l2_dev,
> list_add_tail(&asd->list, ¬ifier->waiting);
> }
>
> - mutex_lock(&list_lock);
> + if (!subnotifier)
> + mutex_lock(&list_lock);
Just to be sure, I'd verify the mutex is indeed acquired.
lockdep_assert_held(mutex) ?
> +
> + /*
> + * This function can be called recursively so the list
> + * might be modified in a recursive call. Start from the
> + * top of the list each iteration.
> + */
> + found = 1;
> + while (found) {
> + found = 0;
>
> - list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> - int ret;
> + list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
> + int ret;
>
> - asd = v4l2_async_belongs(notifier, sd);
> - if (!asd)
> - continue;
> + asd = v4l2_async_belongs(notifier, sd);
> + if (!asd)
> + continue;
>
> - ret = v4l2_async_test_notify(notifier, sd, asd);
> - if (ret < 0) {
> - mutex_unlock(&list_lock);
> - return ret;
> + ret = v4l2_async_test_notify(notifier, sd, asd);
> + if (ret < 0) {
> + if (!subnotifier)
> + mutex_unlock(&list_lock);
> + return ret;
> + }
> +
> + found = 1;
> + break;
> }
> }
>
> /* Keep also completed notifiers on the list */
> list_add(¬ifier->list, ¬ifier_list);
>
> - mutex_unlock(&list_lock);
> + if (!subn
[PATCH] v4l2-async: add subnotifier registration for subdevices
When registered() of v4l2_subdev_internal_ops is called the subdevice
have access to the master devices v4l2_dev and it's called with the
async frameworks list_lock held. In this context the subdevice can
register its own notifiers to allow for incremental discovery of
subdevices.
The master device registers the subdevices closest to itself in its
notifier while the subdevice(s) themself register notifiers for there
closest neighboring devices when they are registered. Using this
incremental approach two problems can be solved.
1. The master device no longer have to care how many subdevices exist in
the pipeline. It only needs to care about its closest subdevice and
arbitrary long pipelines can be created without having to adapt the
master device for each case.
2. Subdevices which are represented as a single DT node but register
more then one subdevice can use this to further the pipeline
discovery. Since the subdevice driver is the only one who knows which
of its subdevices is linked with which subdevice of a neighboring DT
node.
To enable subdevices to register/unregister notifiers from the
registered()/unregistered() callback v4l2_async_subnotifier_register()
and v4l2_async_subnotifier_unregister() are added. These new notifier
register functions are similar to the master device equivalent functions
but run without taking the v4l2-async list_lock which already are held
when he registered()/unregistered() callbacks are called.
Signed-off-by: Niklas Söderlund
---
drivers/media/v4l2-core/v4l2-async.c | 91 +---
include/media/v4l2-async.h | 22 +
2 files changed, 95 insertions(+), 18 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-async.c
b/drivers/media/v4l2-core/v4l2-async.c
index 96cc733f35ef72b0..d4a676a2935eb058 100644
--- a/drivers/media/v4l2-core/v4l2-async.c
+++ b/drivers/media/v4l2-core/v4l2-async.c
@@ -136,12 +136,13 @@ static void v4l2_async_cleanup(struct v4l2_subdev *sd)
sd->dev = NULL;
}
-int v4l2_async_notifier_register(struct v4l2_device *v4l2_dev,
-struct v4l2_async_notifier *notifier)
+static int v4l2_async_do_notifier_register(struct v4l2_device *v4l2_dev,
+ struct v4l2_async_notifier *notifier,
+ bool subnotifier)
{
struct v4l2_subdev *sd, *tmp;
struct v4l2_async_subdev *asd;
- int i;
+ int found, i;
if (!notifier->num_subdevs || notifier->num_subdevs > V4L2_MAX_SUBDEVS)
return -EINVAL;
@@ -168,32 +169,69 @@ int v4l2_async_notifier_register(struct v4l2_device
*v4l2_dev,
list_add_tail(&asd->list, ¬ifier->waiting);
}
- mutex_lock(&list_lock);
+ if (!subnotifier)
+ mutex_lock(&list_lock);
+
+ /*
+* This function can be called recursively so the list
+* might be modified in a recursive call. Start from the
+* top of the list each iteration.
+*/
+ found = 1;
+ while (found) {
+ found = 0;
- list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
- int ret;
+ list_for_each_entry_safe(sd, tmp, &subdev_list, async_list) {
+ int ret;
- asd = v4l2_async_belongs(notifier, sd);
- if (!asd)
- continue;
+ asd = v4l2_async_belongs(notifier, sd);
+ if (!asd)
+ continue;
- ret = v4l2_async_test_notify(notifier, sd, asd);
- if (ret < 0) {
- mutex_unlock(&list_lock);
- return ret;
+ ret = v4l2_async_test_notify(notifier, sd, asd);
+ if (ret < 0) {
+ if (!subnotifier)
+ mutex_unlock(&list_lock);
+ return ret;
+ }
+
+ found = 1;
+ break;
}
}
/* Keep also completed notifiers on the list */
list_add(¬ifier->list, ¬ifier_list);
- mutex_unlock(&list_lock);
+ if (!subnotifier)
+ mutex_unlock(&list_lock);
return 0;
}
+
+int v4l2_async_subnotifier_register(struct v4l2_subdev *sd,
+ struct v4l2_async_notifier *notifier)
+{
+ if (!sd->v4l2_dev) {
+ dev_err(sd->dev ? sd->dev : NULL,
+ "Can't register subnotifier for without v4l2_dev\n");
+ return -EINVAL;
+ }
+
+ return v4l2_async_do_notifier_register(sd->v4l2_dev, notifier, true);
+}
+EXPORT_SYMBOL(v4l2_async_subnotifier_register);
+
+int v4l2_async_notifier_register(struct v4l2_device *v4l2_dev,
+struct v4l2_async_n
