<aka_[m]>
[ 59.262021] cpufreq: __target_index: Failed to change cpu frequency: -16
<aka_[m]>
they flooding way too much and i cannot see start of log
<aka_[m]>
Device or resource busy
<aka_[m]>
[ 1.113100] qcom-cpr: probe of b018000.power-controller failed with error -22
<aka_[m]>
[ 1.113554] qcom-cpr: probe of b118000.power-controller failed with error -22
<aka_[m]>
great
<aka_[m]>
it throws me on probe because i defined ACC as NULL
<aka_[m]>
data = of_device_get_match_data(dev);
<aka_[m]>
return -EINVAL;
<aka_[m]>
if (!data || !data->cpr_desc || !data->acc_desc)
<aka_[m]>
do i need to workaround this?
<aka_[m]>
or remove checks
<aka_[m]>
or do if (acc_desc)
<aka_[m]>
hmm
<aka_[m]>
can i define global variable in driver and then do conditional?
<bamse>
konradybcio: ^^ did your cpr changes get picked up? or this is unrelated?
<aka_[m]>
bamse: unrelated
<aka_[m]>
im talking about legacy cpr
<aka_[m]>
with qcs404 it has mem_acc but it does not on 8976
<bamse>
aka_[m]: ahh, so not a regression?
<JIaxyga[m]>
Hey krzk! What do you think about merging pm6150l and pm8150l into one dtsi? I did some research and I'm almost certain that pm6150l, pm7150l and pm8150l are all the same pmic with different naming. This is indicated by the same id (from PM8150L 3.0). I also saw experiments on the forums of repairmen, where they put pm6150l instead of pm8150l and vice versa. I also saw where pm6150l and pm8150l were installed instead of pm7150l. All these
<JIaxyga[m]>
experiments ended successfully. I think there is no point in duplicating lines of code for the same pmic with different names
<JIaxyga[m]>
This can be a little tricky due to the already large number of devices added
<JIaxyga[m]>
But why not?
<aka_[m]>
on older pmis these sometimes differ with few hardware blocks and/or mpp/gpio pins
<aka_[m]>
weird
<aka_[m]>
i was having -22 errors then after adding debug msgs everywhere i get no such anymore but instead nvmem throws EBUSY
<aka_[m]>
s/was/were/
<aka_[m]>
probe of qcom-cpufreq-nvmem failed with error -16