Thanks for info ![:)]( "Smile")
Meanwhile we have backported both MAX drivers (stripped down for our use case). We obviously did not use new API. Everything is working perfectly with the same devicetree bindings.
We have launched a kickstarted campaign with our devices and will soon release those drivers under GPL license. I don't think that anyone would merge this to upstream as these drivers have some hardware specficic hardcoded values (for simplicity). In addition, if we were to develop a proper driver for both maxes, there is still one in mainline which I suppose would cause some conflicts.
One thing we had to add is a metadata pad support. Mainline driver has a single sink and source for both serializer and deserializer. We had to add additional pad to make things work. For cameras that do not use metadata pad (eg. rpi cam1) there is a bool value which disables it.
Meanwhile we have backported both MAX drivers (stripped down for our use case). We obviously did not use new API. Everything is working perfectly with the same devicetree bindings.
We have launched a kickstarted campaign with our devices and will soon release those drivers under GPL license. I don't think that anyone would merge this to upstream as these drivers have some hardware specficic hardcoded values (for simplicity). In addition, if we were to develop a proper driver for both maxes, there is still one in mainline which I suppose would cause some conflicts.
One thing we had to add is a metadata pad support. Mainline driver has a single sink and source for both serializer and deserializer. We had to add additional pad to make things work. For cameras that do not use metadata pad (eg. rpi cam1) there is a bool value which disables it.
Statistics: Posted by jakos — Tue Feb 04, 2025 6:57 pm