Oddly FRAMOS's pages for the IMX455 are giving me a 404 error, although they are listed if you search for them.
Summary appears to be "Sony Starvis CMOS Rolling shutter 61.04 MP, 9568 x 6380, 2.7 inch, 3.76 x 3.76 µm, RGB, 21 fps, SLVS-EC,"
FRAMOS would be the best people to approach for an answer.
They seem to prefer NVidia platforms, and those don't use standard V4L2 drivers for image sensors. Converting shouldn't be a big issue though.
The main reason Sony switched to SLVS-EC was bandwidth.
Looking at https://www.sony-semicon.com/files/62/f ... _Flyer.pdf, readout mode 0 as 9568 (H) × 6380 (V) approx. 61.04 M pixels 21.33fps 10bpp works out at 13Gbit/s if I've got the numbers right. Pi5 with 4 lane MIPI at 1.5Gbit/s gives a max of 6Gbit/s. I seem to recall that the Camera Front End (CFE) is limited over the max number of MPix/s it can process, but you can write the image data directly to memory instead.
libcamera itself doesn't worry about drivers, it just enumerates what the kernel advertises through Media Controller.
Adding a bridge driver to the kernel isn't that difficult if you have all the required information from it. Again FRAMOS would be best to advise. If they want assistance on the Pi side then they are free to approach us (applications@<domain> is probably the best, or just ask here on the forums).
Summary appears to be "Sony Starvis CMOS Rolling shutter 61.04 MP, 9568 x 6380, 2.7 inch, 3.76 x 3.76 µm, RGB, 21 fps, SLVS-EC,"
FRAMOS would be the best people to approach for an answer.
They seem to prefer NVidia platforms, and those don't use standard V4L2 drivers for image sensors. Converting shouldn't be a big issue though.
The main reason Sony switched to SLVS-EC was bandwidth.
Looking at https://www.sony-semicon.com/files/62/f ... _Flyer.pdf, readout mode 0 as 9568 (H) × 6380 (V) approx. 61.04 M pixels 21.33fps 10bpp works out at 13Gbit/s if I've got the numbers right. Pi5 with 4 lane MIPI at 1.5Gbit/s gives a max of 6Gbit/s. I seem to recall that the Camera Front End (CFE) is limited over the max number of MPix/s it can process, but you can write the image data directly to memory instead.
libcamera itself doesn't worry about drivers, it just enumerates what the kernel advertises through Media Controller.
Adding a bridge driver to the kernel isn't that difficult if you have all the required information from it. Again FRAMOS would be best to advise. If they want assistance on the Pi side then they are free to approach us (applications@<domain> is probably the best, or just ask here on the forums).
Statistics: Posted by 6by9 — Fri Jul 19, 2024 8:55 am