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
Subject: Re: [PATCH v2 1/3] soc: qcom: cmd-db: export RPMh accelerator type string helper
Date: Thu, 6 Aug 2026 11:27:14 +0530 [thread overview]
Message-ID: <6fd06d54-cc60-46fa-ac5b-c32d1c67c2f3@oss.qualcomm.com> (raw)
In-Reply-To: <20260717-rpmh-timeout-debug-v1-v2-1-81ade4fcdb49@oss.qualcomm.com>
On 7/17/2026 1:19 PM, Maulik Shah wrote:
> RPMh resource addresses encode the accelerator type (ARC, VRM, BCM)
> in bits [19:16], matching the cmd_db_hw_type enum values. Add
> cmd_db_hw_type_str() to map an RPMh address to its accelerator type
> name string using the existing SLAVE_ID() macro, and export it so
> drivers that handle raw RPMh addresses can produce human-readable
> diagnostic output without duplicating the address encoding knowledge.
>
> Assisted-by: Claude:claude-sonnet-4-5
> Signed-off-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
Reviewed-by: Navya Malempati <navya.malempati@oss.qualcomm.com>
Thanks,
Navya
next prev parent reply other threads:[~2026-08-06 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 7:49 [PATCH v2 0/3] Output debug information from RSC 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 [this message]
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
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=6fd06d54-cc60-46fa-ac5b-c32d1c67c2f3@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 \
/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®