From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Daniel Scally <djrscally@gmail.com>
Cc: linux-media@vger.kernel.org, libcamera-devel@lists.libcamera.org,
sakari.ailus@linux.intel.com, hanlinchen@chromium.org,
tfiga@chromium.org, hdegoede@redhat.com,
kieran.bingham@ideasonboard.com, hpa@redhat.com
Subject: Re: [PATCH 5/5] media: v4l2-async: Create links during v4l2_async_match_notify()
Date: Wed, 15 Dec 2021 00:22:08 +0200 [thread overview]
Message-ID: <YbkZEDKHP2gyKjqd@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20211213232849.40071-6-djrscally@gmail.com>
Hi Daniel,
Thank you for the patch.
On Mon, Dec 13, 2021 at 11:28:49PM +0000, Daniel Scally wrote:
> Upon an async fwnode match, there's some typical behaviour that the
> notifier and matching subdev will want to do. For example, a notifier
> representing a sensor matching to an async subdev representing its
> VCM will want to create an ancillary link to expose that relationship
> to userspace.
>
> To avoid lots of code in individual drivers, try to build these links
> within v4l2 core.
>
> Signed-off-by: Daniel Scally <djrscally@gmail.com>
> ---
> Changes since the rfc:
>
> - None
>
> drivers/media/v4l2-core/v4l2-async.c | 51 ++++++++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
>
> diff --git a/drivers/media/v4l2-core/v4l2-async.c b/drivers/media/v4l2-core/v4l2-async.c
> index 0404267f1ae4..6575b1cbe95f 100644
> --- a/drivers/media/v4l2-core/v4l2-async.c
> +++ b/drivers/media/v4l2-core/v4l2-async.c
> @@ -275,6 +275,45 @@ v4l2_async_nf_try_complete(struct v4l2_async_notifier *notifier)
> static int
> v4l2_async_nf_try_all_subdevs(struct v4l2_async_notifier *notifier);
>
> +static int
> +__v4l2_async_create_ancillary_link(struct v4l2_async_notifier *notifier,
> + struct v4l2_subdev *sd)
> +{
> + struct media_link *link;
> +
> + if (sd->entity.function != MEDIA_ENT_F_LENS &&
> + sd->entity.function != MEDIA_ENT_F_FLASH)
> + return -EINVAL;
> +
> + link = media_create_ancillary_link(¬ifier->sd->entity, &sd->entity,
Is there a guarantee at this point that notifier->sd->entity has already
been registered with the media_device ? That's done by
media_device_register_entity() called from
v4l2_device_register_subdev().
> + MEDIA_LNK_FL_ENABLED |
> + MEDIA_LNK_FL_IMMUTABLE);
> +
> + return IS_ERR(link) ? PTR_ERR(link) : 0;
> +}
> +
> +/*
> + * Setup links on behalf of the notifier and subdev, where it's obvious what
s/Setup/Create/ ("link setup" refers to another operation, enabling and
disabling links at runtime)
> + * should be done. At the moment, we only support cases where the notifier
> + * is a sensor and the subdev is a lens.
s/sensor/camera sensor/
s/lens/lens controller/
> + *
> + * TODO: Setup pad links if the notifier's function is MEDIA_ENT_F_VID_IF_BRIDGE
> + * and the subdev's is MEDIA_ENT_F_CAM_SENSOR
> + */
> +static int v4l2_async_try_create_links(struct v4l2_async_notifier *notifier,
> + struct v4l2_subdev *sd)
> +{
> + if (!notifier->sd)
> + return 0;
> +
> + switch (notifier->sd->entity.function) {
> + case MEDIA_ENT_F_CAM_SENSOR:
> + return __v4l2_async_create_ancillary_link(notifier, sd);
> + default:
> + return 0;
> + }
> +}
> +
> static int v4l2_async_match_notify(struct v4l2_async_notifier *notifier,
> struct v4l2_device *v4l2_dev,
> struct v4l2_subdev *sd,
> @@ -293,6 +332,18 @@ static int v4l2_async_match_notify(struct v4l2_async_notifier *notifier,
> return ret;
> }
>
> + /*
> + * Depending of the function of the entities involved, we may want to
> + * create links between them (for example between a sensor and its lens
> + * or between a sensor's source pad and the connected device's sink
> + * pad)
s/)/)./
> + */
> + ret = v4l2_async_try_create_links(notifier, sd);
> + if (ret) {
> + v4l2_device_unregister_subdev(sd);
> + return ret;
> + }
> +
> /* Remove from the waiting list */
> list_del(&asd->list);
> sd->asd = asd;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2021-12-14 22:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 23:28 [PATCH 0/5] Introduce ancillary links Daniel Scally
2021-12-13 23:28 ` [PATCH 1/5] media: media.h: Add new media link type Daniel Scally
2021-12-14 21:50 ` Laurent Pinchart
2021-12-14 21:52 ` Daniel Scally
2021-12-13 23:28 ` [PATCH 2/5] media: entity: Add link_type() helper Daniel Scally
2021-12-14 21:54 ` Laurent Pinchart
2021-12-14 21:57 ` Daniel Scally
2021-12-13 23:28 ` [PATCH 3/5] media: entity: Skip non-data links in graph iteration Daniel Scally
2021-12-14 15:01 ` Sakari Ailus
2021-12-14 16:14 ` Daniel Scally
2021-12-14 21:22 ` Sakari Ailus
2021-12-14 21:37 ` Daniel Scally
2021-12-14 22:05 ` Laurent Pinchart
2021-12-13 23:28 ` [PATCH 4/5] media: entity: Add support for ancillary links Daniel Scally
2021-12-14 4:06 ` kernel test robot
2021-12-14 21:25 ` Sakari Ailus
2021-12-14 21:54 ` Daniel Scally
2021-12-14 22:14 ` Laurent Pinchart
2022-01-16 23:52 ` Daniel Scally
2021-12-13 23:28 ` [PATCH 5/5] media: v4l2-async: Create links during v4l2_async_match_notify() Daniel Scally
2021-12-14 22:22 ` Laurent Pinchart [this message]
2021-12-14 22:36 ` Daniel Scally
2021-12-14 23:01 ` Laurent Pinchart
2021-12-14 23:41 ` Daniel Scally
2021-12-15 9:04 ` Laurent Pinchart
2021-12-15 9:44 ` Sakari Ailus
2021-12-15 9:55 ` Laurent Pinchart
2021-12-15 23:10 ` Daniel Scally
2021-12-15 23:14 ` Laurent Pinchart
2022-01-16 0:01 ` Daniel Scally
2021-12-16 11:10 ` kernel test robot
2021-12-16 11:14 ` Daniel Scally
2021-12-15 9:25 ` [PATCH 0/5] Introduce ancillary links Mauro Carvalho Chehab
2021-12-15 9:36 ` Daniel Scally
2021-12-15 9:52 ` Laurent Pinchart
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=YbkZEDKHP2gyKjqd@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=djrscally@gmail.com \
--cc=hanlinchen@chromium.org \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=libcamera-devel@lists.libcamera.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox