From: Mike Tipton <mdtipton@codeaurora.org>
To: Georgi Djakov <georgi.djakov@linaro.org>, linux-pm@vger.kernel.org
Cc: okukatla@codeaurora.org, sibis@codeaurora.org,
bjorn.andersson@linaro.org, amit.pundir@linaro.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] interconnect: qcom: sdm845: Enable keepalive for the MM1 BCM
Date: Tue, 13 Oct 2020 18:10:21 -0700 [thread overview]
Message-ID: <56dc5ac7-2bed-4dbb-b7fc-c0308a2a454a@codeaurora.org> (raw)
In-Reply-To: <20201012194034.26944-1-georgi.djakov@linaro.org>
On 10/12/2020 12:40 PM, Georgi Djakov wrote:
> After enabling interconect scaling for display on the db845c board,
s/interconect/interconnect/
> in certain configurations the board hangs, while the following errors
> are observed on the console:
>
> Error sending AMC RPMH requests (-110)
> qcom_rpmh TCS Busy, retrying RPMH message send: addr=0x50000
> qcom_rpmh TCS Busy, retrying RPMH message send: addr=0x50000
> qcom_rpmh TCS Busy, retrying RPMH message send: addr=0x50000
> ...
>
> In this specific case, the above is related to one of the sequencers
> being stuck, while client drivers are returning from probe and trying
> to disable the currently unused clock and interconnect resources.
> Generally we want to keep the multimedia NoC enabled like the rest of
> the NoCs, so let's set the keepalive flag on it too.
>
> Fixes: aae57773fbe0 ("interconnect: qcom: sdm845: Split qnodes into their respective NoCs")
> Reported-by: Amit Pundir <amit.pundir@linaro.org>
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
> ---
> drivers/interconnect/qcom/sdm845.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Mike Tipton <mdtipton@codeaurora.org>
prev parent reply other threads:[~2020-10-14 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 19:40 [PATCH] interconnect: qcom: sdm845: Enable keepalive for the MM1 BCM Georgi Djakov
2020-10-14 1:10 ` Mike Tipton [this message]
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=56dc5ac7-2bed-4dbb-b7fc-c0308a2a454a@codeaurora.org \
--to=mdtipton@codeaurora.org \
--cc=amit.pundir@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=okukatla@codeaurora.org \
--cc=sibis@codeaurora.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).