[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c9b1422d-46f4-467a-b6c4-27eecae95897@oss.qualcomm.com>
Date: Tue, 20 May 2025 16:41:08 +0200
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: "Maulik Shah (mkshah)" <maulik.shah@....qualcomm.com>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org,
Marijn Suijten <marijn.suijten@...ainline.org>,
Doug Anderson <dianders@...omium.org>
Subject: Re: [PATCH 1/3] soc: qcom: qcom_stats: Add support to read DDR
statistic
On 5/20/25 11:59 AM, Maulik Shah (mkshah) wrote:
>
[...]
>>> +static int qcom_ddr_stats_show(struct seq_file *s, void *d)
>>> +{
>>> + struct ddr_stats_entry data[DDR_STATS_MAX_NUM_MODES];
>>> + void __iomem *reg = (void __iomem *)s->private;
>>> + u32 entry_count;
>>> + int i;
>>> +
>>> + entry_count = readl_relaxed(reg + DDR_STATS_NUM_MODES_ADDR);
>>> + if (entry_count > DDR_STATS_MAX_NUM_MODES)
>>> + return 0;
>>
>> -EINVAL
>>
>> Konrad
>
> I kept this return as success from details given in commit message of [1]
> which made the qcom_subsystem_sleep_stats_show() function return 0
> in order to run command like below to collect the stats without interspersed errors
> grep ^ /sys/kernel/debug/qcom_stats/*
>
> The same may break if return error from ddr stats too.
Stephen mentioned that the errors may have appeared because the subsystems
may only populate data after the probe of the stats driver.
I would assume and hope the DDR stats aren't affected by this..
Konrad
Powered by blists - more mailing lists