Hi all, i'm trying to debug camss driver and imx412 hack for imx 576 camera. Someone have already work on it ? It's for sm6350-mainline. Thanks a lot bryanodonoghue: ^^ electro575 cphy or dphy ? msm_csiphy do you have a downstream tree pointer ? i have done this https://debian-facile.org/paste-20AEF16161-a5201fe4b66b1ecb70bfa2b91809de06 https://debian-facile.org/paste-3E8F7BC866-440f8ad88599f99da0be6ac33f1d70e9 https://debian-facile.org/paste-F3D304C17F-5df1eb885a9eb63b3eb95cde5cd1f17b [Jeu Mai 2 17:36:53 2024] camcc_ife_0_clk status stuck at 'off' there's your first problem clock isn't on camcc gdsc is probably not setup right check the power domains in your dtsi then check the declarations of the gdsc in camcc okey, thanks a lot i will check this do you know which version of csid and vfe you are supporting here ? not really, i have the source code but , ... https://debian-facile.org/paste-8067C6B0BB-c4a4cff32982418658854ee00d281d59 do you know a downstream tag for 6350 ? something like LA.UM.9.16.r1-09800-MANNAR.QSSI12.0 humm, it's not really android similar tags for the Linux embedded LE.stuff O, sorry, it's not for LE LE.UM.4.3.3.r1-01400 postmarketos I get you but - what is the source you are working from ? https://github.com/sm6350-mainline/linux/tree/sm6350-6.9-wip-camera with a beginning work from another person specially for power domains https://github.com/sm6350-mainline/linux/blob/sm6350-6.9-wip-camera/drivers/clk/qcom/camcc-sm6350.c fp4 - ping z3ntu He has a tree I believe already done, but he doesn't arrived to get data from camera full media tree https://debian-facile.org/images/file-Rc0e5e8df8ab6edd1812f4be9187b1ad3 i work with his/her on this camera part right so VFE 1.xx is correct https://github.com/torvalds/linux/commit/d8d71cb0d37e01307bf8ca485e284e64f46609ea but IDK that VFE 170 is correct but if its fp4 then surely the android release tags are public .. let's offline from IRC about this - sync with Luca sorry, what exactly mean "but if its fp4 then surely the android release tags are public" ? https://code.fairphone.com/projects/fairphone-4/kernel.html I haven't fetched this yet but the qcom release tags will be there just need to match the tag to the camera-kernel release and then go through the PHY, IFE, CSID - get the version numbers CLO tag of target tree is LA.QSSI.11.0.R1.11.00.00.668.170.00 I believe nice i don't understand :/ lol haaaa clo = codelinaro.org where Qualcomm publishes open source code when qcom releases an android/kernel stack - any android system really - is done on repo an xml file which points to git repos with git tags techpacks are releases of say video core or camera core outside of the main android kernel which contain those tags parse the repo, find the git tag, find the version of code that matches your silicon simples i will try I'll do this https://code.fairphone.com/projects/fairphone-4/build-instructions.html to have what ? this version ? LA.QSSI.11.0.R1.11.00.00.668.170.00 just for fun :) parse the repo, find the git tag, find the version of code that matches your silicon => What repo exactly ? this ? repo init -u ssh://gerrit-public.fairphone.software:29418/manifest -b int/13/fp4 this is this repo ? Yeah we need to find a tag in that repo that matches in some way one of the tags here https://git.codelinaro.org/clo/la/platform/vendor/opensource/camera-kernel.git that's the CPHY/CSID/IFE version to target i.e. know which CSIPHY init sequence to use - if we can reuse an upstream CSID/IFE - and get the reg offsets right ok, i will check https://debian-facile.org/paste-AA8EC1AFB3-bdfae7d31f035d9223810439e9ab7f87 MAX_CSIPHY_REG_ARRAY 70 MAX_CSIPHY_CMN_REG_ARRAY 5 for sure ife 17x INSTALL usr//camera/drivers/cam_isp/isp_hw_mgr/isp_hw/vfe_hw/vfe17x/ (7 files)