ChanServ 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
<jackm[m]> > in 7"
<jackm[m]> @barni2000:matrix.org do you have any 8953/8952/8937/etc with the slimbus to cirrus codec and amp setup?
<jackm[m]> I've been gradually working on it for ali and have some ideas of how it works
<jackm[m]> but i'm kinda stuck
<barni2000[m]> Idk, i think i dont have
<jackm[m]> it's the motos obviously
<jackm[m]> not sure if you have motos
<barni2000[m]> I have but my motos are using the simplest architecture
<jackm[m]> cs47l35 + cs35l35 is a very fancy setup
<jackm[m]> maybe you'd have advice anyways, i should write down what i've done
<jackm[m]> i barely understand the ASoC system
<barni2000[m]> Montana is using cirrus codec but afaik it also combined with pm8937 codec and it not using the slimbus
<jackm[m]> I wonder if it would be easier to get audio up on sdm660 motos first
Veynamer[m] has joined #msm8937-mainline
<Veynamer[m]> Redmi 5a goodix touch fixed
f_ has quit [Read error: Connection reset by peer]
f_ has joined #msm8937-mainline
<jackm[m]> <jackm[m]> "i barely understand the ASoC..." <- my brain is exploding
<barni2000[m]> <Veynamer[m]> "1000199351.mp4" <- What was the issue, it was working for me
<Biswa96[m]> <barni2000[m]> "." <- It seems that those values are present in lineageos kernel's touchscreen driver. I think the logic could be added in this mainline kernel https://github.com/LineageOS/android_kernel_xiaomi_msm8937/blob/244a83c94d2e0d855848cf16bd4b91b9ef372947/techpack/xiaomi-msm8937/touchscreen/focaltech_touch/focaltech_core.c#L1759
<Biswa96[m]> or, maybe not.
<barni2000[m]> Some generic stuff can be implemented with more dt properties but it can be mapped from userspace
<Biswa96[m]> I am getting itchy for running a python process constantly for 3 touch keys. It seems that battery drains quickly in postmarketos than in android.
<barni2000[m]> It should not drain the battery too much, graphical stuff eats more
<barni2000[m]> Btw most of the mobile ui on linux not really using these buttons
<Veynamer[m]> <barni2000[m]> "What was the issue, it was..." <- Use compatible in dts gt911 while in fact there is 917d, I took a patch for it from msm8953 and changed dts
<barni2000[m]> I think i have different goodix touch
<barni2000[m]> I will check when i have arrived home, btw the compatible does not matter because it selects nothing in the driver
<barni2000[m]> Maybe it is not matching with the compatible in lk2nd
<barni2000[m]> The compatible part is useless
<barni2000[m]> It is getting the chip type from the register
<barni2000[m]> But 917d should work without any change
<barni2000[m]> Change im 8953 also useless
<Veynamer[m]> Well, without the changes I made, it didn't work
<barni2000[m]> s/im/in/
<barni2000[m]> Add only the chip id and keep the compatible
<barni2000[m]> Length is selected by the chip id if it is not matching it will choose the largest
<barni2000[m]> Line 248
<barni2000[m]> Both 917d and 915 are working for me without any change
<Veynamer[m]> magic, idk
<Veynamer[m]> I had an error in reading the presses, they were shifted to the bottom edge on the right side, but they were pressed in a different place
<barni2000[m]> Length can cause this, maybe different fw versions handling messages differently
<barni2000[m]> But as I said you only need to add chip id with data to driver
<barni2000[m]> Compatible part is not needed
<Veynamer[m]> <barni2000[m]> "Compatible part is not needed" <- It turns out we can only add
<Veynamer[m]> { .id = "917D", .data = &gt967_chip_data },
<Veynamer[m]> but it is compatible to use goodix,gt911
<Veynamer[m]> What about other changes besides compatable that I made in dts
<barni2000[m]> Revert them
<barni2000[m]> interrupts-extended was just an alias for parent and interrupts so it was useless to change that
<barni2000[m]> idk if mainlime driver have irq-gpios property
<barni2000[m]> If you uncomment pinctrls it will break my riva toich
<barni2000[m]> s/toich/touch/
<barni2000[m]> [ 3.150721] goodix-ts-mi8937 3-005d: IC Version: 917D_5003 [ 3.151489] goodix-ts-mi8937 3-005d: Config group0 used,length: 186
<barni2000[m]> this is my 5A touch and it is working ootb
<barni2000[m]> Veynamer: can you check your touch version?
<barni2000[m]> this is from the mainline driver withouth change [ 118.708632] Goodix-TS 1-005d: ID 917D, version: 5003
<Veynamer[m]> Identical to what you showed.....
<barni2000[m]> s/withouth/without/, s//`/, s//`/
<barni2000[m]> 5003?
<Veynamer[m]> Yes
<barni2000[m]> then i don't understand why your touch is not working ootb
<barni2000[m]> what is the downstream driver version in dmesg?
<Veynamer[m]> <barni2000[m]> "what is the downstream driver..." <- V2.8.1<2022/07/25>
<Veynamer[m]> I have twrp 3.7.1_12-0 last version, there I watch dmesg
<barni2000[m]> [ 3.011242] goodix-ts-mi8937 3-005d: GTP Driver Version: V2.8.1<2022/07/25>
<barni2000[m]> same
<barni2000[m]> but LoS not updating the fw so maybe the last miui was flash it
<Veynamer[m]> barni2000[m]: No, miui 9.6.5.0 I installed it for the last time
<barni2000[m]> idk what is the difference
<Veynamer[m]> As a result, my node in DTS is now made like in Redmi ugglite
<Veynamer[m]> I just didn't change VDDIO-supply
<Veynamer[m]> Touchscreen Works
<Veynamer[m]> Can you check this variant today? Maybe that's the problem
<barni2000[m]> only irq-gpios is missing
<barni2000[m]> maybe that is the real issue
<barni2000[m]> 1337misom: how do you compile sdm429?
<barni2000[m]> and why it complains about soc reference
<M1337misom[m]> barni2000[m]: No it is because of blsp2_uart2 since i gets defined there and i then use it later.
<M1337misom[m]> s/blsp2_uart2/blsp2\_uart2/, s/i/it/
<barni2000[m]> It is not really answer to my question
<M1337misom[m]> barni2000[m]: I will just move soc to sdm429.dtsi. dtc just complained about &blsp2_uart2 not being defined since i had the soc block below it. I hope that makes sense.
<barni2000[m]> strange
<barni2000[m]> oh, now i see
<barni2000[m]> yes you should move it or define everything in the first declaration
<M1337misom[m]> barni2000[m]: Done
<barni2000[m]> is there anyone here with rolex with focaltech touch?