[libcamera-devel] New warnings for pixel formats on Raspberry Pi platforms
Kieran Bingham
kieran.bingham at ideasonboard.com
Mon Aug 8 10:11:54 CEST 2022
Quoting Jacopo Mondi via libcamera-devel (2022-08-08 08:42:07)
> Hi Naush
>
> On Fri, Aug 05, 2022 at 03:26:16PM +0100, Naushir Patuck via libcamera-devel wrote:
> > Hi,
> >
> > A recent change (commit f25ad4a2b16b libcamera: formats: Reimplement V4L2
> > PixelFormatInfo::info()) has started throwing WARN messages on the
> > Raspberry Pi platform:
> >
> > [24:06:09.085738817] [8392] INFO Camera camera_manager.cpp:293 libcamera
> > v0.0.0
> > [24:06:09.196596920] [8408] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported
> > V4L2 pixel format SENS
> > [24:06:09.196729049] [8408] WARN Formats formats.cpp:838 Unsupported pixel
> > format 0x00000000
> > [24:06:09.198112797] [8408] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported
> > V4L2 pixel format BSTA
> > [24:06:09.198203814] [8408] WARN Formats formats.cpp:838 Unsupported pixel
> > format 0x00000000
> > [24:06:09.199839579] [8408] INFO RPI raspberrypi.cpp:1374 Registered
> > camera /base/soc/i2c0mux/i2c at 1/imx477 at 1a to Unicam device /dev/media0 and
> > ISP device /dev/media3
>
> Could you kindly point me to the caller site in your pipeline handler
> ?
>
> >
> > This is because our meta formats for statistics and embedded data do not
> > have defined types in libcamera::formats::PixelFormat. The reason for this
> > is that they are metadata formats used exclusively internally in the
> > pipeline handler, and can never be selected by the application.
> >
>
> I would be interested to see the caller as in my head, if those
> formats are not application visibile, there's no reason to convert
> them to libcamera::formats (ie, they could be managed as V4L2
> formats).
FYI: This is happening on IPU3 too.
kbingham at Jupiter:~$ cam --list
[0:01:55.607533003] [3760] INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3813-fa20fd23
[0:01:55.621621933] [3764] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported V4L2 pixel format ip3G
[0:01:55.621728733] [3764] WARN Formats formats.cpp:838 Unsupported pixel format 0x00000000
[0:01:55.622204108] [3764] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported V4L2 pixel format ip3p
[0:01:55.622273358] [3764] WARN Formats formats.cpp:838 Unsupported pixel format 0x00000000
[0:01:55.622399044] [3764] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported V4L2 pixel format ip3s
[0:01:55.622433003] [3764] WARN Formats formats.cpp:838 Unsupported pixel format 0x00000000
[0:01:55.622765279] [3764] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported V4L2 pixel format ip3G
[0:01:55.622798961] [3764] WARN Formats formats.cpp:838 Unsupported pixel format 0x00000000
[0:01:55.623113998] [3764] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported V4L2 pixel format ip3p
[0:01:55.623142207] [3764] WARN Formats formats.cpp:838 Unsupported pixel format 0x00000000
[0:01:55.623266568] [3764] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported V4L2 pixel format ip3s
[0:01:55.623291940] [3764] WARN Formats formats.cpp:838 Unsupported pixel format 0x00000000
[0:01:55.628131922] [3764] WARN V4L2 v4l2_pixelformat.cpp:301 Unsupported V4L2 pixel format ip3G
[0:01:55.628184502] [3764] WARN Formats formats.cpp:838 Unsupported pixel format 0x00000000
--
Kieran
> > I'm not sure how to fix this. Do I need to add entries in formats.yaml to
> > generate types in libcamera::formats::PixelFormat, meaning I also have to
> > add new 4CCs in the drm headers... :-( Given these are metadata formats,
> > and not user selectable, is this the right thing to do?
> >
> > Naush
More information about the libcamera-devel
mailing list