12:03 <lewisje> What does the ¨msm¨ in this channel name mean?

12:10 <z3ntu> https://en.wikichip.org/wiki/qualcomm/msm

12:40 <lewisje> kthxbai

12:51 <z3ntu> lol

13:25 <Mis012[m]> it stands for 'mainline, son, mainline'

13:25 <Mis012[m]> true story

20:12 <Mis012[m]> I've found https://github.com/torvalds/linux/blob/master/drivers/remoteproc/qcom_q6v5_wcss.c mentioning SSCAON, but what it actually writes to is RELAY_MSG_BUFFER registers...

20:14 <Mis012[m]> and I'm not sure what is listening for those messages on the other end, but it can't be writing to SSCAON because on msm8974 there is no SSCAON...

20:15 <Mis012[m]> not here where it's on msm8998 nor anywhere else

20:16 <bamse> z3ntu: perhaps as you only have a single pmk8350 it's not a problem that you need to solve...but e.g. on sa8155p we have two pm8150 which in the datasheet are referred to as pmm8155_1 and pmm8155_2 (or something along those lines)...as such it would make sense to label and reference them as such

20:17 <Mis012[m]> bamse: how should I model the SSCAON registers?

20:19 <Mis012[m]> also there is https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/power/reset/msm-poweroff.txt

20:20 <Mis012[m]> so I can't really claim the whole PSHOLD module

20:21 <Mis012[m]> and I don't know if I should put SSCAON handling inside that driver since I don't know what SSCAON actually does