[PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline
slongerbeam at gmail.com
Thu Mar 2 15:48:39 PST 2017
On 03/02/2017 08:02 AM, Sakari Ailus wrote:
> Hi Steve,
> On Wed, Feb 15, 2017 at 06:19:16PM -0800, Steve Longerbeam wrote:
>> v4l2_pipeline_inherit_controls() will add the v4l2 controls from
>> all subdev entities in a pipeline to a given video device.
>> Signed-off-by: Steve Longerbeam <steve_longerbeam at mentor.com>
>> drivers/media/v4l2-core/v4l2-mc.c | 48 +++++++++++++++++++++++++++++++++++++++
>> include/media/v4l2-mc.h | 25 ++++++++++++++++++++
>> 2 files changed, 73 insertions(+)
>> diff --git a/drivers/media/v4l2-core/v4l2-mc.c b/drivers/media/v4l2-core/v4l2-mc.c
>> index 303980b..09d4d97 100644
>> --- a/drivers/media/v4l2-core/v4l2-mc.c
>> +++ b/drivers/media/v4l2-core/v4l2-mc.c
>> @@ -22,6 +22,7 @@
>> #include <linux/usb.h>
>> #include <media/media-device.h>
>> #include <media/media-entity.h>
>> +#include <media/v4l2-ctrls.h>
>> #include <media/v4l2-fh.h>
>> #include <media/v4l2-mc.h>
>> #include <media/v4l2-subdev.h>
>> @@ -238,6 +239,53 @@ int v4l_vb2q_enable_media_source(struct vb2_queue *q)
>> +int __v4l2_pipeline_inherit_controls(struct video_device *vfd,
>> + struct media_entity *start_entity)
> I have a few concerns / questions:
> - What's the purpose of this patch? Why not to access the sub-device node
I don't really understand what you are trying to say. That's exactly
what this function is doing, accessing every subdevice in a pipeline
directly, in one convenient function call.
> - This implementation is only workable as long as you do not modify the
> pipeline. Once you disable a link along the pipeline, a device where the
> control was inherited from may no longer be a part of the pipeline.
That's correct. It's up to the media driver to clear the video device's
inherited controls whenever the pipeline is modified, and then call this
function again if need be.
In imx-media driver, the function is called in link_setup when the link
from a source pad that is attached to a capture video node is enabled.
This is the last link that must be made to define the pipeline, so it
is at this time that a complete list of subdevice controls can be
gathered by walking the pipeline.
> Depending on the hardware, it could be a part of another pipeline, in
> which case it certainly must not be accessible through an unrelated video
> node. As the function is added to the framework, I would expect it to
> handle such a case correctly.
The function will not inherit controls from a device that is not
reachable from the given starting subdevice, so I don't understand
you're point here.
> - I assume it is the responsibility of the caller of this function to ensure
> the device in question will not be powered off whilst the video node is
> used as another user space interface to such a sub-device. If the driver
> uses the generic PM functions in the same file, this works, but it still
> has to be documented.
I guess I'm missing something. Why are you bringing up the subject of
power? What does this function have to do with whether a subdevice is
powered or not? The function makes use of v4l2_ctrl_add_handler(), and
the latter has no requirements about whether the device's owning the
control handlers are powered or not.
More information about the linux-arm-kernel