Why is there no support for 1920x1080 at 60fps for IMX477?
Is there a specific technical reason for it? It seems that pixelrate-wise it is ~20% smaller than the supported custom mode of 1332x990@120.
I looked at the kernel driver, and all of the 3 supported modes are hardcoded with a huge bunch of obscure register writes w/o any explanation. From reading posts here and elsewhere I get an impression that IMX477 interface is under an overly strict NDA to the point that even having access to register maps docs would be useless, as the register values are provided by Sony directly by request for specific modes only.
Turns out, however, that some other company, RidgeRun, had worked with Sony and was able to get an 1080p60 mode registers. Luckily, this code is public, under GPL, and can be found in e.g. Nvidia Jetpack 4.5 sources archive here: https://developer.nvidia.com/embedded/j ... 45-archive in a file called `Linux_for_Tegra/source/public/kernel/nvidia/drivers/media/i2c/imx477_mode_tbls.h` (would need to also unpack `kernel_src.tbz2` first). The rest of the sensor driver is seems completely unrelated to and fairly different from Raspberry Pi driver.
It is not currently on my immediate list of things to do, but I wonder if that register list is or can be made compatible with the RPi driver to add 1080p60 support here too. This question probably can't be answered directly as well, due to NDA reasons. But I wonder if Yes/No answer to "Should I bother to try to patch it in directly?" is something I could ask.
I know about h264 encoder not being able to do 1080p60 (w/o overclock), but I also empirically know that JPEG encoder can do +20% pixelrate of 1332x976@120 fairly easily, which should be fine for my purposes.
Is there a specific technical reason for it? It seems that pixelrate-wise it is ~20% smaller than the supported custom mode of 1332x990@120.
I looked at the kernel driver, and all of the 3 supported modes are hardcoded with a huge bunch of obscure register writes w/o any explanation. From reading posts here and elsewhere I get an impression that IMX477 interface is under an overly strict NDA to the point that even having access to register maps docs would be useless, as the register values are provided by Sony directly by request for specific modes only.
Turns out, however, that some other company, RidgeRun, had worked with Sony and was able to get an 1080p60 mode registers. Luckily, this code is public, under GPL, and can be found in e.g. Nvidia Jetpack 4.5 sources archive here: https://developer.nvidia.com/embedded/j ... 45-archive in a file called `Linux_for_Tegra/source/public/kernel/nvidia/drivers/media/i2c/imx477_mode_tbls.h` (would need to also unpack `kernel_src.tbz2` first). The rest of the sensor driver is seems completely unrelated to and fairly different from Raspberry Pi driver.
It is not currently on my immediate list of things to do, but I wonder if that register list is or can be made compatible with the RPi driver to add 1080p60 support here too. This question probably can't be answered directly as well, due to NDA reasons. But I wonder if Yes/No answer to "Should I bother to try to patch it in directly?" is something I could ask.
I know about h264 encoder not being able to do 1080p60 (w/o overclock), but I also empirically know that JPEG encoder can do +20% pixelrate of 1332x976@120 fairly easily, which should be fine for my purposes.
Statistics: Posted by provod — Wed Feb 28, 2024 10:50 pm — Replies 0 — Views 19