<Daanct12>
okay time to go back to msm8937 porting
<Daanct12>
where did you get this `{ "l13", 0x4c00, "vdd_l10_l11_l12_l13"}`?
<Daanct12>
especially the last part
<Daanct12>
looked at some docs, doesnt seem to be referenced
<minecrell>
Daanct12: the PMIC has pads named similar to that
<Daanct12>
hmm, is there any pmic docs?
<Daanct12>
hold on i think i found it
<Daanct12>
ah yup, looks like i do
<minecrell>
Daanct12: no, qcom barely has any public docs
<Daanct12>
in this particular schematic i found, it seems like pm8937 has s1-s6, but only s1-s4 are grounded to something
<Daanct12>
s5 and s6 exists, but doesnt seem to ground to anything
<minecrell>
Daanct12: you should have other regulators going to the vdd_ pads you need, the grounding isn't relevant for that property
<aka_[m]>
s1-s4 -> lX
jhovold has quit [Ping timeout: 480 seconds]
<Daanct12>
how did we get regulator_linear_range from qcom_smd-regulator?
<Daanct12>
gaaaaaaaaaaaaah
<Daanct12>
oops wrong chat
<minecrell>
Daanct12: you can try matching the regulator types using the SPMI driver and then match it back to what's in smd. If you're lucky the PMIC only has regulator types that are already in both drivers
<Daanct12>
ah yeah that requires me to get a working usb driver first lol
<Daanct12>
or does it by default dump everything to dmesg?
<minecrell>
Daanct12: lk2nd has a port of the spmi driver, can dump it from there using "fastboot oem debug dump-regulators", after adding your pmic
<minecrell>
but you could also add logging to dmesg in the Linux one of course
<Daanct12>
didnt know that
<mal>
bryanodonoghue: did you test rmmod of camss module after the power domain changes? I get "refcount_t: underflow; use-after-free" and a backtrace about msm_vfe_genpd_cleanup when doing rmmod