Re: [PATCH/RFC v8 04/14] v4l2-async: change custom.match callback argument type

From: Jacek Anaszewski
Date: Mon Dec 01 2014 - 04:35:42 EST

Hi Laurent,

On 11/29/2014 05:38 PM, Laurent Pinchart wrote:
Hi Jacek,

Thank you for the patch.

On Friday 28 November 2014 10:17:56 Jacek Anaszewski wrote:
It is useful to have an access to the async sub-device
being matched, not only to the related struct device.
Change match callback argument from struct device
to struct v4l2_subdev. It will allow e.g. for matching
a sub-device by its "name" property.

In principle I agree. However, we will need to reimplement v4l2-async based on
the component (drivers/base/component.c) framework at some point. As the
component framework is based on struct device, will it still be possible to
match on subdev name in that case ? If not, we might need to try to find
another approach to the issue.

There were reservations raised [1] concerning the way of matching
by name, as the labels are not guaranteed to be globally unique across
Device Tree. I admit, this issue has to be solved in a different way.
Especially in view of prospective transition to using

I propose to add a new structure:

struct v4l2_asd_match{
bool (*match)(struct v4l2_async_subdev *, void *);
void *priv;

and a function:
v4l2_async_register_subdev_with_match(struct v4l2_subdev *sd, struct v4l2_asd_match*).

This way we could pass DT sub-node related to a sub-led in a priv
field of v4l2_asd_match upon registration.

This is similar approach as in case of drivers/base/component.c.

Best Regards,
Jacek Anaszewski

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at