01:02 <HappY[m]> strongtz: if you don't mind can you share your kernel config for sm8350.. I just want to verify my usb configuration..

01:58 <strongtz[m]> HappY: https://gitlab.com/sakuramist-group/linux-next/-/blob/testing/ayn-odin2/arch/arm64/configs/odin2_defconfig

01:58 <strongtz[m]> this should work on sm8350

01:59 <strongtz[m]> remember to edit cmdline and initramfs path

01:59 <HappY[m]> strongtz[m]: Thank you so much.. I have to check usb & pmic part..

01:59 <strongtz[m]> I hardcoded them

02:00 <HappY[m]> strongtz[m]: No problem dear.. I will just verify with my kernel configuration..

02:02 <HappY[m]> I saw without usb c connector my device charging but not all the time..if I am lucky then some times charging..

05:05 <HappY[m]> <strongtz[m]> "I hardcoded them" <- Thank you Ur usb configuration solve my one issue.. now my device serial reporting currect.. If I don't want audio out via usb C then "fsa4480" is not required right? Like this?

05:10 <HappY[m]> One more thing.. I create my device tree with simple-battery + fuel-guge + pmic-glink it is okay?

05:53 <strongtz[m]> I'm not sure about fsa4480. It controls the type-c sbu signal and does exist on my device. So why don't I enable it?🤣

05:54 <strongtz[m]> and for me pmic-gpink is all I need, no extra fg or battery

05:55 <strongtz[m]> <HappY[m]> "Thank you Ur usb configuration..." <- u probably forgot battmgr before?

05:55 <HappY[m]> strongtz[m]: It is actually type C role switch for audio output mey be.. because.. see this https://github.com/Saikatsaha1996/android_kernel_oneplus_sm8350/blob/9c86b0cf0172c8ca42ed377af48c0e877ba7a050/arch/arm64/boot/dts/vendor/oplus/porsche/porsche-common.dtsi#L1402

05:55 <strongtz[m]> yes, but it also does something when doing DP Altmode switching

05:56 <HappY[m]> strongtz[m]: I have battery manager.. still my device reporting 100% battery..

05:57 <HappY[m]> strongtz[m]: In my device always failed to connect usb or fsa4480..

06:07 <HappY[m]> <strongtz[m]> "yes, but it also does something..." <- By the way i forgot.. https://matrix.to/#/!mCFUAbDMChDbEFqHbW:matrix.org/$MKlkUclpr3HMvNR3QEIUgVytnFeJOKF8fYyRCjFNREY?via=matrix.org&via=adomerle.xyz&via=reactos.org is it okay?

06:07 <HappY[m]> Fuel-guge + pmic-glink + simple-battery

06:08 <strongtz[m]> If it works, then it's okay🤣

06:09 <HappY[m]> strongtz[m]: It's working.. even my downstream dmesg reporting fuel-guge.. but in downstream kernel device tree not available any fuel-guge

06:13 <HappY[m]> strongtz[m]: Example in this device don't have any simple battery & fuel-guge but how battery manager working actually without guge & batt data ?

06:13 <HappY[m]> https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts

06:13 <strongtz[m]> pmic-glink driver will register battmgr once adsp is ready

06:14 <strongtz[m]> adsp has battery data

06:14 <strongtz[m]> there's no need to define a battery in device tree

06:15 <HappY[m]> strongtz[m]: Ohhhh okay than guge also not required if adsp works ?

06:15 <strongtz[m]> ideally it should be

06:17 <HappY[m]> Okay it was my fst device so I only was 0% knowledge about mobile hardware & software..

11:29 <HappY[m]> Without fuel-guge device randomly rebooting :/ so fuel-guge required for my device?

15:15 <HappY[m]> <strongtz[m]> "ideally it should be" <- today I ping you many times and I am really sorry for that.. but seriously I am facing one issue which I never faced before .. I removed "simple-battery" device booting perfectly with fuel-guge & pmic-glink.. and then I removed fuel-guge also.. but now device randomly rebooting if I remove fuel-guge.. only pmos logo shown then reboot.. and then I added fuel-guge now booting perfectly.. is it really cause

15:15 <HappY[m]> for fuel-guge?

15:50 <strongtz[m]> <HappY[m]> "today I ping you many times..." <- never mind for pinging me :D but I also have no idea about your fuel gauge

16:13 <ungeskriptet> Hi all, I have an SM7125 device whose UFS is compatible with the one from SM7150. Should I upstream the patch below or is it fine to reuse the SM7150 compatible in my DTS?

16:13 <ungeskriptet> https://github.com/ungeskriptet/linux/blob/0378e0a/drivers/phy/qualcomm/phy-qcom-qmp-ufs.c#L1659-L1660

16:15 <ungeskriptet> Oh, and SC7180 also works with the SM7150 UFS config. Should I add SC7180 too or just one of them?

16:34 <HappY[m]> <strongtz[m]> "never mind for pinging me :D but..." <- Problem solved or not it's not matter for me.. but thanks for your reply... 😊

20:38 <aka_[m]> <ungeskriptet> "https://github.com/ungeskriptet..."; <- its annoying but you could just upstream compatible into yaml and do : compatible-X-soc-specific, compatible-y-real-soc, generic

20:39 <aka_[m]> and it will just select y one as X does not exist in driver