diff options
author | Marian Cichy <m.cichy@pengutronix.de> | 2021-03-15 11:17:25 +0100 |
---|---|---|
committer | Laurent Pinchart <laurent.pinchart@ideasonboard.com> | 2021-03-16 02:03:37 +0200 |
commit | 4671911df040aeb3fdda07ae7cd2ce41eb6421cd (patch) | |
tree | c0add74c143c009512086b1fc1d0674aeb50658a /src/qcam/assets/feathericons/activity.svg | |
parent | 287e4f82bd0e94b936b2cbc420aa1fa5645d1503 (diff) |
pipeline: simple: Use breadth-first search to setup media pipeline
When the SimplePipeline is setting up its data and media pipeline in the
SimpleCameraData constructor, it merely tries to find the first valid
pad and link to the next entity, starting from the camera sensor.
Following this path may not always lead to a valid capture device and
therefore the setup will fail on some machines. This is for example an
issue when using the SimplePipeline on an i.MX-6Q with its i.MX IPU.
This commit implements a different approach to setup the media-pipeline
by finding the shortest path to a valid capture device, using the
breadth-first search algorithm. On i.MX6Q, the shortest path has a good
chance to be the path from the sensor to the CSI capture device, as
other paths may involve image converters, encoders or other IPU blocks
and will have therefore more nodes.
Signed-off-by: Marian Cichy <m.cichy@pengutronix.de>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Diffstat (limited to 'src/qcam/assets/feathericons/activity.svg')
0 files changed, 0 insertions, 0 deletions