Re: [PATCH v4 2/3] soc: qcom: stats: Add stats compatible and config for Shikra

From: Abel Vesa

Date: Mon Sep 14 2026 - 11:52:56 EST


On 26-09-07 19:17:54, Sneh Mankad wrote:
> SoC LPM stats are present in RPM MSGRAM and subsystem LPM stats are
> present in SMEM for Shikra.
>
> For earlier targets using RPM processor like msm8974, rpm_master_stat.c was
> used for subsystem LPM stats since those stats were populated in RPM
> MSGRAM.
>
> Here is a brief summary of previous targets and their stats configuration,
> along with the drivers used to display them.
>
> +---------------|----------------------------|---------------------------+
> | SoC | subsystem LPM stats | SoC LPM stats |
> |---------------|----------------------------|---------------------------|
> | msm8974, | RPM processor MSGRAM | RPM processor MSGRAM |
> | msm8226 | (rpm_master_stat.c) | (qcom_stats.c) |
> |---------------|----------------------------|---------------------------|
> | sm6350, | SMEM (DDR) | AOP processor MSGRAM |
> | sdm845, etc. | (qcom_stats.c) | (qcom_stats.c) |
> |---------------|----------------------------|---------------------------|
> | Shikra | SMEM (DDR) | RPM processor MSGRAM |
> | | (qcom_stats.c) | (qcom_stats.c) |
> +---------------|----------------------------|---------------------------+
>
> qcom_stats.c supports both the configurations for shikra, reading subsystem
> LPM stats from SMEM and reading SoC LPM stats from RPM MSGRAM.
>
> A generic "qcom,rpm-stats" compatible only reads SoC LPM stats like vmin
> and vlow. Add shikra rpm compatible and config to read subsystem LPM
> stats too along with SoC LPM stats.
>
> Below is an example showing LPM stats for "apss" subsystem with this
> change:
>
> cat /sys/kernel/debug/qcom_stats/apss
> Count: 2192
> Last Entered At: 5498618336
> Last Exited At: 5498708046
> Accumulated Duration: 2046572620.
>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxxxx>
> Reviewed-by: Maulik Shah <maulik.shah@xxxxxxxxxxxxxxxx>
> Signed-off-by: Sneh Mankad <sneh.mankad@xxxxxxxxxxxxxxxx>

Reviewed-by: Abel Vesa <abel.vesa@xxxxxxxxxxxxxxxx>