From: Daniel Scally <djrscally@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
hanlinchen@chromium.org, tfiga@chromium.org, hdegoede@redhat.com,
kieran.bingham@ideasonboard.com
Subject: Re: [RFC PATCH 0/2] Introduce ancillary links
Date: Fri, 26 Nov 2021 07:58:46 +0000 [thread overview]
Message-ID: <de31fd62-b6f9-e042-9d26-6c3feb3faaa4@gmail.com> (raw)
In-Reply-To: <YaBNlpcr+i6s5rng@pendragon.ideasonboard.com>
On 26/11/2021 02:59, Laurent Pinchart wrote:
> On Fri, Nov 26, 2021 at 12:16:01AM +0000, Daniel Scally wrote:
>> Hello all
>>
>> This series is not yet ready to merge, but I wanted to share it as I know some
>> other folks are working in similar areas at the moment (and I am including the
>> libcamera devel list for the same reason)
> Seems you forgot to CC libcamera-devel :-) Let's fix that on v2.
Argh! Sorry, will do
>> At present there's no means in the kernel of describing the supporting
>> relationship between subdevices that work together to form an effective single
>> unit - the type example in this case being a camera sensor and its
>> corresponding vcm. To attempt to solve that, this series adds a new type of
>> media link called MEDIA_LNK_FL_ANCILLARY_LINK, which connects two instances of
>> struct media_entity. Further work would be needed to document it properly, and
>> there may be ramifications within the v4l2-core which I have not yet discovered
>> (a lot of places seem to assume that media_entity->links means pad-2-pad links,
>> so some extra work might be needed to validate the link type before doing any
>> thing to them).
>>
>> The mechanism of connection I have modelled as a notifier and async subdev,
>> which seemed the best route since sensor drivers already typically will call
>> v4l2_async_register_subdev_sensor() on probe, and that function already looks
>> for a reference to a firmware node with the reference named "lens-focus". To
>> avoid boilerplate in the sensor drivers, I added some new functions in
>> v4l2-async that are called in v4l2_async_match_notify() to create the ancillary
>> links - checking the entity.function of both notifier and subdev to make sure
>> that's appropriate. I haven't gone further than that yet, but I suspect we could
>> cut down on code elsewhere by, for example, also creating pad-to-pad links in
>> the same place.
>>
>> Thoughts and comments very welcome :)
>>
>> Dan
>>
>> Daniel Scally (2):
>> media: entity: Add support for ancillary links
>> media: v4l2-async: Create links during v4l2_async_match_notify()
>>
>> drivers/media/mc/mc-entity.c | 30 ++++++++++++++++
>> drivers/media/v4l2-core/v4l2-async.c | 51 ++++++++++++++++++++++++++++
>> include/media/media-entity.h | 30 ++++++++++++++++
>> include/uapi/linux/media.h | 1 +
>> 4 files changed, 112 insertions(+)
>>
next prev parent reply other threads:[~2021-11-26 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 0:16 [RFC PATCH 0/2] Introduce ancillary links Daniel Scally
2021-11-26 0:16 ` [RFC PATCH 1/2] media: entity: Add support for " Daniel Scally
2021-11-26 2:50 ` kernel test robot
2021-11-26 2:56 ` Laurent Pinchart
2021-11-26 7:58 ` Daniel Scally
2021-11-26 3:41 ` kernel test robot
2021-11-26 3:41 ` kernel test robot
2021-11-26 0:16 ` [RFC PATCH 2/2] media: v4l2-async: Create links during v4l2_async_match_notify() Daniel Scally
2021-11-26 13:10 ` kernel test robot
2021-11-26 2:59 ` [RFC PATCH 0/2] Introduce ancillary links Laurent Pinchart
2021-11-26 7:58 ` Daniel Scally [this message]
2021-11-26 9:41 ` Hans de Goede
2021-11-26 9:46 ` Daniel Scally
2021-11-26 9:53 ` Kate Hsuan
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=de31fd62-b6f9-e042-9d26-6c3feb3faaa4@gmail.com \
--to=djrscally@gmail.com \
--cc=hanlinchen@chromium.org \
--cc=hdegoede@redhat.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.