From: "Maulik Shah (mkshah)" <maulik.shah@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Marijn Suijten <marijn.suijten@somainline.org>,
Doug Anderson <dianders@chromium.org>
Subject: Re: [PATCH v2 2/3] soc: qcom: qcom_stats: Add QMP support for syncing ddr stats
Date: Thu, 22 May 2025 11:18:44 +0530 [thread overview]
Message-ID: <7f1d0db1-bdd5-4d50-8880-c0a1d2df4af7@oss.qualcomm.com> (raw)
In-Reply-To: <jl4g7mutb65ifxuv3covropjntziv5enxyc3lgz2fi7ddu64bd@e726p6by3vfh>
On 5/21/2025 6:22 PM, Dmitry Baryshkov wrote:
> On Wed, May 21, 2025 at 02:02:11PM +0530, Maulik Shah wrote:
>> Recent SoCs (SM8450 onwards) require QMP command to be sent before reading
>> ddr stats. The duration field of ddr stats will get populated only if QMP
>> command is sent.
>>
>> Add support to send ddr stats freqsync QMP command.
>>
>> Signed-off-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
>> ---
>> drivers/soc/qcom/qcom_stats.c | 29 ++++++++++++++++++++++++++++-
>> 1 file changed, 28 insertions(+), 1 deletion(-)
>>
>> @@ -310,6 +329,14 @@ static int qcom_stats_probe(struct platform_device *pdev)
>> qcom_create_subsystem_stat_files(root, config);
>> qcom_create_soc_sleep_stat_files(root, reg, d, config);
>> qcom_create_ddr_stat_files(root, reg, config);
>> + /*
>> + * QMP is used for DDR stats syncing to MSG RAM for recent SoCs (SM8450 onwards).
>> + * The prior SoCs do not need QMP handle as the required stats are already present
>> + * in MSG RAM, provided the DDR_STATS_MAGIC_KEY matches.
>> + */
>> + qcom_stats_qmp = qmp_get(&pdev->dev);
>> + if (IS_ERR(qcom_stats_qmp))
>> + qcom_stats_qmp = NULL;
>
> Don't we need to handle QMP being not probed _yet_? In other words,
> there are several distinct cases:
>
> - No QMP defined, proceed without it
> - QMP defined, not probed yet, return -EPROBE_DEFER here
> - QMP defined, qmp_get() returns an error, return that error code
> - QMP defined, qmp_get() returned valid pointer, proceed with using it.
>
Yes we need to handle these cases.
I will update in v3.
Thanks,
Maulik
>>
>> platform_set_drvdata(pdev, root);
>>
>>
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2025-05-22 5:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 8:32 [PATCH v2 0/3] soc: qcom: qcom_stats: Add DDR stats Maulik Shah
2025-05-21 8:32 ` [PATCH v2 1/3] soc: qcom: qcom_stats: Add support to read DDR statistic Maulik Shah
2025-05-21 17:01 ` Konrad Dybcio
2025-05-22 5:48 ` Maulik Shah (mkshah)
2025-05-22 14:24 ` Konrad Dybcio
2025-05-21 23:40 ` kernel test robot
2025-05-21 8:32 ` [PATCH v2 2/3] soc: qcom: qcom_stats: Add QMP support for syncing ddr stats Maulik Shah
2025-05-21 12:52 ` Dmitry Baryshkov
2025-05-21 21:53 ` Konrad Dybcio
2025-05-22 5:48 ` Maulik Shah (mkshah) [this message]
2025-05-21 8:32 ` [PATCH v2 3/3] arm64: dts: qcom: Add QMP handle for qcom_stats Maulik Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7f1d0db1-bdd5-4d50-8880-c0a1d2df4af7@oss.qualcomm.com \
--to=maulik.shah@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®