06:00 <jstultz> bamse: vkoul: Hey! Any thoughts on that lt9611 issue I emailed you on?

12:39 <elder_> calebccff_: If you are willing, I think I'd like to work with you to get the IPA resume-from-system-suspend functionality working the way I really want it to. You reported a couple weeks ago that it worked, but I had ideas on how I wanted to do it a little differently. I just found I was unable to cause the condition to occur.

12:39 <elder_> Are you open to that? It would probably involve running some instrumented code for me and reporting back what you find, and then as I implement any changes, you testing them for me.

12:40 <elder_> I'm not in a huge hurry (it's an issue I reported last summer), but I could be ready to try something in the coming week or so.

15:54 <Mis012[m]> uh hm, so https://github.com/torvalds/linux/blob/master/drivers/clk/qcom/clk-smd-rpm.c#L169 is where it reboots

15:54 <Mis012[m]> on this iteration: `#define RPM_SMD_MMAXI_CLK66`

15:55 <Mis012[m]> how does not running UEFI affect that...

16:01 <Mis012[m]> konradybcio: did you have no similar issues with the Sony who-needs-display-in-the-bootloader specimen?

17:28 <konradybcio> "who-needs-display-in-the-bootloader" aka no_cont_splash or yes_cont_splash?

17:29 <Mis012[m]> well, iirc there's one Sony device that literally doesn't have display drivers in the bootloader?

17:33 <konradybcio> >Sony device that literally doesn't have display drivers in the bootloader

17:33 <konradybcio> xperia z1, msm8974 yes

17:33 <konradybcio> any newer device may need loads of stock dtb garbage to initialize the display, but the code is there

17:34 <Mis012[m]> and that one didn't have any weird issues like reboots when trying to enable RPM_SMD_MMAXI_CLK?

17:35 <Mis012[m]> not that 8974 had an entire NoC dedicated to MMSS

17:39 <konradybcio> >and that one didn't have any weird issues like reboots when trying to enable RPM_SMD_MMAXI_CLK?

17:39 <konradybcio> 8998? no

17:40 <Mis012[m]> well, msm8974 if msm8974 is the only SoC where they skipped doing display stuff in bootloader

17:41 <Mis012[m]> but yeah, msm8974 doesn't have MMSS NoC

17:46 <konradybcio> it's a matter of bringing up all of the dependencies correctly in linux

17:46 <konradybcio> these devices allow you to make sure your setup is fully correct

17:47 <Mis012[m]> yeah, but sadly it's clearly not atm

17:48 <Mis012[m]> >these devices allow you to make sure your setup is fully correct

17:48 <Mis012[m]> konradybcio: that reminds me of the regulator that's needed for the big cores

17:48 <Mis012[m]> should probably bug you people to put that into CPR

17:54 <konradybcio> in what? in the 1.5y-in-review-freezerbox thing? :P

17:54 <Mis012[m]> yeah, that would be the one :P

17:55 <Mis012[m]> konradybcio: so, how exactly do I figure out what the dependencies for RPM_SMD_MMAXI_CLK are? :P

17:55 <Mis012[m]> I don't like have a clock tree on me

17:56 <Mis012[m]> sadly

17:56 <konradybcio> trial and error and error and error and error and error and trial and error

17:56 <Mis012[m]> tries to wish clock tree documentation into materializing on ssd

17:57 <Mis012[m]> well, the UEFI code has to do stuff in the right order, right?

17:58 <Mis012[m]> looking at hyp in ghidra was the breakthough for SSC, so that might be the thing to check

18:13 <bamse> jstultz: i got your email and i've always felt that the "sleep" function is pretty hard...but i think the gpio reset should bring things back up...perhaps we're missing some re-initialization afterwards

18:13 <bamse> jstultz: but i haven't had the chance to really dig into the details

18:14 <bamse> jstultz: we do have some documentation, but far from complete...i think we should be able to figure out what's going on though

18:39 <jstultz> bamse: ok, let me know if there's anything I can help test or try.

18:40 <jstultz> bamse: (or if you need register dumps or something before/after)