XISP : Creating new Pipeline Handler for AMD/Xilinx HLS-based ISP

[Kieran Bingham]

Quoting Mario Bergeron (2025-01-16 22:04:06)
> Hello,
> 
> I have made some progress on my XISP pipeline handler.
> 
> I am able to enumerate the four (4) cameras in my system:
> 
> # cam -l
> ...
> Available cameras:
> 1: 'imx219' (/base/pl-bus/i2c at 80040000/sensor at 10)
> 2: 'imx708_wide' (/base/pl-bus/i2c at 80070000/sensor at 10)
> 3: 'imx500' (/base/pl-bus/i2c at 80090000/sensor at 1a)
> 4: 'imx477' (/base/pl-bus/i2c at 800b0000/sensor at 1a)
> 
> 
> When I attempt to capture one frame, I get the following error message when
> queueing buffers:
> 
> # cam -c1 -C1
> ...
> Using camera /base/pl-bus/i2c at 80040000/sensor at 10 as cam0
> [51:33:28.743843521] [53606]  INFO Camera camera.cpp:1202 configuring
> streams: (0) 640x480-RBG888
> cam0: Capture 1 frames
> [51:33:28.782733421] [53607] ERROR V4L2 v4l2_videodevice.cpp:1777
> /dev/video0[16:cap]: Failed to queue buffer 0: Invalid argument

This is quite often a failure to conifgure the pipeline correctly and
propagate formats through from the camera to the ISP for all of the link
validations.

I usually make sure I enable all v4l2 debug at this stage on the
subdevices and video devices to be sure all dbg prints come out from the
kernel - and check to see what's failing.

Happy bug hunting!
--
Kieran