10:05 <z3ntu> Hi, in the qcom_stats driver I noticed that querying apss leads to a warning from smem.c because WARN_ON(item >= __smem->item_count) All the other files query without problem, some return data, some do not

10:05 <z3ntu> that's on sm6350, similar generation as sm8250

10:07 <z3ntu> While I don't really understand how the smem stuff works, from Linux side I don't see an API to check beforehand if a given item could be accessible qcom_smem_get or will be higher than the item count, there's no API to get the item_count from smem into qcom_stats to not query it in the first place. Maybe just the WARN_ON should be removed in smem?

11:02 <konradybcio> z3ntu is it also empty/invalid downstream?

11:03 <konradybcio> is it also empty if you let the phone sleep in android?

11:12 <z3ntu> konradybcio: The equivalent downstream seems to be /sys/power/system_sleep/stats ? I only get aosd, cxsd and ddr there

11:13 <konradybcio> we may want to turn that WARN_ON into a return -ERANGE then..

11:14 <z3ntu> ah there's also /sys/power/rpmh_stats/master_stats , that has data for APSS, MPSS, ADSP, ADSP_ISLAND and CDSP. And yes, for APSS it shows data

11:14 <z3ntu> APSS

11:14 <z3ntu> Version:0x1

11:14 <z3ntu>  Sleep Count:0x4fc

11:14 <z3ntu> Sleep Last Entered At:0x1002800f9

11:14 <z3ntu> 

11:14 <z3ntu>  Sleep Last Exited At:0x1002f1e36

11:14 <z3ntu> Sleep Accumulated Duration:0x2ebb6e00

11:14 <z3ntu> 

11:15 <z3ntu> but looks like the APSS stuff is just collected by a Linux driver, not read from anywhere special