From: Pavan Kondeti <quic_pkondeti@quicinc.com>
To: Unnathi Chalicheemala <quic_uchalich@quicinc.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@quicinc.com>
Subject: Re: [PATCH v3 2/2] firmware: qcom_scm: Support multiple waitq contexts
Date: Thu, 7 Nov 2024 10:53:11 +0530 [thread overview]
Message-ID: <e466a2bd-c1a0-4a55-9d20-eb9e58427554@quicinc.com> (raw)
In-Reply-To: <3fe8739458227081d43f00746fe527bc4f8fd8b5.1730735881.git.quic_uchalich@quicinc.com>
On Mon, Nov 04, 2024 at 08:20:56AM -0800, Unnathi Chalicheemala wrote:
>
> +static int qcom_scm_query_waitq_count(void)
> +{
> + int ret;
> + struct qcom_scm_desc desc = {
> + .svc = QCOM_SCM_SVC_WAITQ,
> + .cmd = QCOM_SCM_WAITQ_GET_INFO,
> + .owner = ARM_SMCCC_OWNER_SIP
> + };
> + struct qcom_scm_res res;
> +
> + if (!__qcom_scm_is_call_available(__scm->dev, QCOM_SCM_SVC_WAITQ, QCOM_SCM_WAITQ_GET_INFO))
> + return 1;
> +
> + ret = qcom_scm_call_atomic(__scm->dev, &desc, &res);
> + if (ret)
> + return ret;
> +
> + return res.result[0] & GENMASK(7, 0);
> +}
I see that this SCM call is same as what we called to get the IRQ, not
possible to populate all the waitq info at once and process/cache them
accordingly?
Thanks,
Pavan
prev parent reply other threads:[~2024-11-07 5:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 16:20 [PATCH v3 0/2] SCM: Support latest version of waitq-aware firmware Unnathi Chalicheemala
2024-11-04 16:20 ` [PATCH v3 1/2] firmware: qcom_scm: Add API to get waitqueue IRQ info Unnathi Chalicheemala
2024-11-07 5:02 ` Pavan Kondeti
2024-11-04 16:20 ` [PATCH v3 2/2] firmware: qcom_scm: Support multiple waitq contexts Unnathi Chalicheemala
2024-11-07 5:23 ` Pavan Kondeti [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=e466a2bd-c1a0-4a55-9d20-eb9e58427554@quicinc.com \
--to=quic_pkondeti@quicinc.com \
--cc=andersson@kernel.org \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_uchalich@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®