From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Stephen Boyd <swboyd@chromium.org>
Subject: Re: [PATCH 2/4] soc: qcom: stats: don't crash if DDR offset contains invalid data
Date: Thu, 14 Dec 2023 12:59:06 +0100 [thread overview]
Message-ID: <be7fe545-3a5f-4af3-89f6-c22326689465@linaro.org> (raw)
In-Reply-To: <CAD=FV=XX4wLg1NNVL15RK4D4tLvuSzZyUv=k_tS4bSb3=7QJzQ@mail.gmail.com>
On 12/14/23 01:59, Doug Anderson wrote:
> Hi,
>
> On Mon, Dec 11, 2023 at 1:11 AM Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
>>
>> On 9.12.2023 22:55, Dmitry Baryshkov wrote:
>>> The stats ram on sm8150 platform contains invalid data at the
>>> DDR_DYNAMIC_OFFSET. Most likely this is because the platform didn't
>>> support DDR sleep stats.
>> Interesting. Can you read back DDR_DYNAMIC_OFFSET on 8350/8280 and
>> see if 8150 has correct data in there?
>>
>>> However this platform uses generic
>>> "qcom,rpmh-stats" compatible, which implies presense of the DDR data.
>>> Add safety net to prevent old DTB files from crashing the
>>> qcom,rpmh-stats driver.
>> Yeah I'dve never thought there would be garbage in there..
>>
>> I'd advocate for simply not doing anything wrt sleep stats if DDR
>> stats are unavailable though. The QMP handle can stay, as there
>> may (I don't know) be more data available that we want to export
>> through this driver.
>
> FWIW, I'm getting a crash on sc7180-trogdor like this too. In kgdb it
> says I'm on line:
>
> key = readl(ddrd->base);
>
> ...and
>
> (gdb) print ddrd->base
> $1 = (void *) 0xffffffc0833a3149
> (gdb) print reg
> $2 = (void *) 0xffffffc0833a3000
>
> ...so I guess my "stats_offset" must have been 0x149.
>
> Can we get a fix landed or a revert? Thanks! :-)
Right, I guess we may want to revert it and I'll try to get more
info from Qualcomm folks..
Konrad
next prev parent reply other threads:[~2023-12-14 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 21:55 [PATCH 1/4] dt-bindings: soc: qcom: stats: add compatible for SM8150 platform Dmitry Baryshkov
2023-12-09 21:55 ` [PATCH 2/4] soc: qcom: stats: don't crash if DDR offset contains invalid data Dmitry Baryshkov
2023-12-11 9:10 ` Konrad Dybcio
2023-12-14 0:59 ` Doug Anderson
2023-12-14 11:59 ` Konrad Dybcio [this message]
2023-12-09 21:56 ` [PATCH 3/4] soc: qcom: stats: support SM8150 platform Dmitry Baryshkov
2023-12-11 9:11 ` Konrad Dybcio
2023-12-11 9:43 ` Dmitry Baryshkov
2023-12-11 10:46 ` Konrad Dybcio
2023-12-11 11:09 ` Dmitry Baryshkov
2023-12-09 21:56 ` [PATCH 4/4] arm64: dts: qcom: sm8150: use SoC-specific compat for RPMh stats Dmitry Baryshkov
2023-12-11 10:50 ` [PATCH 1/4] dt-bindings: soc: qcom: stats: add compatible for SM8150 platform Krzysztof Kozlowski
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=be7fe545-3a5f-4af3-89f6-c22326689465@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).