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
z3ntu1 has joined #msm8937-mainline
<z3ntu1> Hi, is there already some work done for sdm429 or sdm429w (Snapdragon Wear 4100+)? Anybody have any info about these chips?
<Danct12[m]> maybe lanik123 has
<lanik123[m]> <hacker420[m]> "lanik123: why did you disable..." <- It doesn't work properly without IPA, so we can disable it temporarily
<lanik123[m]> <z3ntu1> "Hi, is there already some work..." <- Hello, I am working on support for the sdm439(sdm429 but with additional cluster). It has already booted but without display.
<lanik123[m]> Btw I have fixed second cluster on 8937 (but I'm not sure)
<z3ntu1> lanik123: Cool! Do you have some links which source repo, etc?
<z3ntu1> Something where I can get USB to work on a device
<lanik123[m]> <z3ntu1> "Something where I can get USB to..." <- Bad news for you, sdm439 will not get usb support soon because we don't have charger driver in mainline
<lanik123[m]> * you, sdm439/sdm429 will
<lanik123[m]> Or you device use custom charger?
<z3ntu1> Is this some quirk of 429/439? On all devices I've touched so far USB has zero dependency on charger driver
<lanik123[m]> <z3ntu1> "Is this some quirk of 429/439..." <- This is becouse some old SoCs (for example msm8916) have externel otg trigger which can trigger host mode without charging driver. In other SoCs (for example 8917, 8937, 8953 or sdm439) control of the otg mode is implemented in charger driver and we can't change it directly
<lanik123[m]> lanik123[m]: Maybe it is possible to use usb without charger driver, but I don't know about this method yet.
<minecrell[m]> unless it's very special you should be able to force the mode as you wish
<minecrell[m]> implementing auto-detection properly is another topic of course
<lanik123[m]> minecrell[m]: Hmm, I'll check it again later on sdm439. On rolex and santoni perpehral mode doesn't help
<minecrell[m]> is this usb2 (chipidea) or 3 (dwc3)?
<lanik123[m]> usb2
<minecrell[m]> then you likely need to make sure you have some kind of extcon that reports detected peripheral mode (it can be some dummy driver that reports it permanently)
<minecrell[m]> maybe something like pm8916_usbin can work https://wiki.postmarketos.org/wiki/MSM8916_Mainlining#Otherwise
<lanik123[m]> minecrell[m]: Hm, ty. I will test it later
<z3ntu1> tbh it was really useful for 8226 bringup, fortunately nowadays this thing has smbb charger support
<barni2000[m]> <lanik123[m]> "Hmm, I'll check it again later..." <- on santoni usb is working without charger
<barni2000[m]> <minecrell[m]> "then you likely need to make..." <- i think that will help me with usb on ugg, ugglite and riva, ty
<barni2000[m]> finally it seems working
<barni2000[m]> now i can work on them
<barni2000[m]> Luca Weiss: minecrell[m] thanks again
<barni2000[m]> it seems fg is still broken
<barni2000[m]> the registers were incorrect in the mainline driver but not enough to correcting them
<barni2000[m]> <lanik123[m]> "It doesn't work properly without..." <- it seems we will have working IPA driver soon, but call and sms should work without it but we don't have userspace support to it
<barni2000[m]> IPA only needs because of modemanager requires it
<barni2000[m]> but only msm8940 using IPA as I saw
<lanik123[m]> barni2000[m]: msm8953 also use IPA
<barni2000[m]> yes thats why we will have a working driver
<M0xCAFEBABE[m]> barni2000[m]: msm8920 uses it too
<barni2000[m]> sdm439 also i think
<barni2000[m]> we have a half broken IPA driver sms and calls are working
<barni2000[m]> but vladly is working on a new one
<lanik123[m]> barni2000[m]: No, sdm439 have same modem as msm8937
<barni2000[m]> x7?
<barni2000[m]> x6
<lanik123[m]> barni2000[m]: x6
<lanik123[m]> > <@barni2000:matrix.org> x7?
<lanik123[m]> * x6 lte
<barni2000[m]> with rootfs i have got bluescreen with debug-shell it works fine do you know what can cause it?
<barni2000[m]> i am on 6.6-developmet branch
<barni2000[m]> i have find an overlap maybe that cause
<lanik123[m]> <barni2000[m]> "i am on 6.6-developmet branch" <- You use danct tree?
<lanik123[m]> ?
<lanik123[m]> > <@barni2000:matrix.org> i am on 6.6-developmet branch
<lanik123[m]> * Are you using danct tree?
<barni2000[m]> <lanik123[m]> "You use danct tree?..." <- yes
<barni2000[m]> i have corrected tsens that is fine now i have some issue with reserved memory maybe that causing my issues
<lanik123[m]> barni2000[m]: That's because dunct tree doesn't have some important commits for smmu
<barni2000[m]> oh ok than i will cherry-pick from your tree
<barni2000[m]> at least usb is working now
<lanik123[m]> This two commits need for you
<barni2000[m]> lanik123[m]: ty
<barni2000[m]> wait i am hacking ugglite atm and it has msm8917
<lanik123[m]> barni2000[m]: Ah, can u share logs?
<barni2000[m]> sure but i don't see any stacktrace in it
* barni2000[m] posted a file: console-ramoops-0 (18KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/pFHMutVHuCmgpywDDKkQPrFo >
<barni2000[m]> i still have overlaps
<lanik123[m]> I don't think overlap is the main problem, maybe this is device specific problem
<lanik123[m]> lanik123[m]: Like with splash on land
<lanik123[m]> > <@lanik123:matrix.org> I don't think overlap is the main problem, maybe this is device specific problem
<lanik123[m]> * Like splash on land
<lanik123[m]> s/problem/issue/
<barni2000[m]> i have disabled msm_drm thought it cause the issue but not
<barni2000[m]> it caused by simpleframbuffer
<barni2000[m]> i have removed power-domain and clocks
<barni2000[m]> but now the display cannot refresh without it
<barni2000[m]> time to generate panel driver i think
<barni2000[m]> why ugglite has 2 leds defined when the device only have a white led?
<barni2000[m]> wifi is working
<barni2000[m]> is it worth to use goodix fw if the touchscreen works without it?
<barni2000[m]> [ 20.202886] Goodix-TS 0-005d: Direct firmware load for goodix_9157_cfg.bin failed with error -2
<barni2000[m]> [ 20.225139] Goodix-TS 0-005d: Invalid config (0, 0, 0), using defaults