From: Navya Malempati <navya.malempati@oss.qualcomm.com>
To: Maulik Shah <maulik.shah@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Raju P.L.S.S.S.N" <quic_rplsssn@quicinc.com>
Subject: Re: [PATCH v2 3/3] soc: qcom: rpmh-rsc: Output debug information from RSC
Date: Thu, 6 Aug 2026 12:17:35 +0530 [thread overview]
Message-ID: <9e9071a4-cd9e-4aa1-8f2a-a607451084ce@oss.qualcomm.com> (raw)
In-Reply-To: <20260717-rpmh-timeout-debug-v1-v2-3-81ade4fcdb49@oss.qualcomm.com>
On 7/17/2026 1:19 PM, Maulik Shah wrote:
> From: "Raju P.L.S.S.S.N" <rplsssn@codeaurora.org>
>
> When an RPMh transfer times out there is no visibility into which
> TCS was stuck, what commands it was carrying, or whether the
> completion IRQ was pending at the GIC. Add rpmh_rsc_debug() to
> capture this state at timeout:
>
> - Iterates all in-use TCSes and dumps per-TCS control register
> state (controller status, AMC mode, IRQ status) and per-command
> register state (address, data, message ID, completion status).
> The accelerator type (ARC/VRM/BCM) is decoded from the address
> using cmd_db_hw_type_str().
>
> - Queries the GIC pending state for the RSC IRQ via
> irq_get_irqchip_state() to distinguish two failure modes:
> * AOSS firmware did not respond (IRQ never fired)
> * Linux lockup (IRQ pending at GIC but handler never ran)
>
> - Reports the completion object state to cross-check with the
> IRQ status.
>
> Store the IRQ number in struct rsc_drv to enable the GIC query.
>
> Signed-off-by: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
> Co-developed-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
> Signed-off-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
Reviewed-by: Navya Malempati <navya.malempati@oss.qualcomm.com>
Thanks,
Navya
prev parent reply other threads:[~2026-08-06 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 7:49 [PATCH v2 0/3] " Maulik Shah
2026-07-17 7:49 ` [PATCH v2 1/3] soc: qcom: cmd-db: export RPMh accelerator type string helper Maulik Shah
2026-08-06 5:57 ` Navya Malempati
2026-08-06 9:50 ` Dmitry Baryshkov
2026-07-17 7:49 ` [PATCH v2 2/3] soc: qcom: cmd-db: add reverse address-to-name lookup Maulik Shah
2026-08-06 6:45 ` Navya Malempati
2026-08-06 9:50 ` Dmitry Baryshkov
2026-07-17 7:49 ` [PATCH v2 3/3] soc: qcom: rpmh-rsc: Output debug information from RSC Maulik Shah
2026-08-06 6:47 ` Navya Malempati [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=9e9071a4-cd9e-4aa1-8f2a-a607451084ce@oss.qualcomm.com \
--to=navya.malempati@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maulik.shah@oss.qualcomm.com \
--cc=quic_rplsssn@quicinc.com \
/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®