Danct12 changed the topic of #msm8937-mainline to: Boot Linux on your MSM8917/37/40 and QM215 mobile! | GitHub: https://github.com/msm89x7-mainline | Logs: https://oftc.irclog.whitequark.org/msm8937-mainline | Bridged to #msm8937-mainline:kde.org on Matrix
<lanik123[m]> Sorry for the long wait. All changes are great
<barni2000[m]> ok i will reorder the commits and send them
<barni2000[m]> which cpr is used by msm8937? msm8916 has some wip stuff and cpr3, cpr4, cprh was sent to upstream
<barni2000[m]> btw cpufreq can be fixed with lk2nd
<Danct12[m]> i would recommend submitting the most basic device trees to lkml first until we got everything working
<lanik123[m]> barni2000[m]: Meh, I don't really like idea of fixing it outside the kernel layer when we can do it inside the kernel
<barni2000[m]> every other socs dot the same
<barni2000[m]> msm8939, msm8953 ...
<barni2000[m]> msm8937 is very similar to msm8939
<barni2000[m]> msm8956, msm8976
<barni2000[m]> * msm8956, msm8976 they have fixed by lk2nd
<barni2000[m]> * msm8956, msm8976 have fixed by lk2nd also
<barni2000[m]> difference between msm8956 and msm8937, msm8937 is booting on the little cluster
<lanik123[m]> lanik123[m]: But I never understood why they abandoned that commit in new mainline if it's a prettier solution than doing something via lk2nd...
<lanik123[m]> lanik123[m]: But that's just my opinion
<barni2000[m]> lanik123[m]: with lk2nd you can use standard drivers and almost every devices needed lk2nd because of panel selection
<lanik123[m]> barni2000[m]: I don't see any problem in writing a driver for panel selection inside the kernel
<barni2000[m]> but lk2nd already supported it and works fine it useless to wasting effort for that
<barni2000[m]> you want to save about 5s in boot time
<lanik123[m]> barni2000[m]: I want to save time spent porting and building lk2nd for new devices
<barni2000[m]> porting is 1 minute build will be done by CI
<barni2000[m]> pmbootstrap flasher flash_lk2nd is working fine
<barni2000[m]> lk2nd supports extlinux also so we can use dtb overlays for some fix
<lanik123[m]> barni2000[m]: Ok, ok... Then I don't see any more problems with lk2nd
<lanik123[m]> What are the current porting tasks? CPR, SMMU or something else?
<barni2000[m]> SMMU is working with commits from your branch idk what is missing from it.
<barni2000[m]> CPR should be checked yes
<barni2000[m]> we have working interconnect driver also so that could be applied and binded
<barni2000[m]> OPPs shold be corrected for iccc
<barni2000[m]> s/iccc/icc/
<barni2000[m]> this is my current working tree based on develop branch, i have fixed many schema errors and switched usb phy. https://github.com/barni2000/linux/tree/ugglite-6.9
<barni2000[m]> it contains stuffs from expriment branch also
<lanik123[m]> <barni2000[m]> "SMMU is working with commits..." <- Now in my commit is a very simple and incomplete(some stuff like 64bit addressing is broken) implementation of MMU from downstream kernel written by junak and with few of my changes. I don't think we can send this to upstream xdd. I will update this comit a bit later
<lanik123[m]> <barni2000[m]> "we have working interconnect..." <- Oh, that's cool. All icc clk's working?
<barni2000[m]> it seems
<lanik123[m]> <barni2000[m]> "this is my current working..." <- ty
<lanik123[m]> s/comit/commit/
<lanik123[m]> * Now in my commit is a very simple and incomplete(some stuff like 64bit addressing is broken) implementation of MMU from downstream kernel written by junak and with few of my changes. I don't think we can send this mess to upstream xdd. I will update this commit a bit later
ungeskriptet[m] has joined #msm8937-mainline
<barni2000[m]> I have sent it https://lore.kernel.org/dri-devel/20240623-dsi-v1-0-4ab560eb5bd9@gmail.com/ i hope I not messed up anything