From: Guru Das Srinagesh <quic_gurus@quicinc.com>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: David Heidelberg <david@ixit.cz>,
Robert Marko <robimarko@gmail.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Elliot Berman <quic_eberman@quicinc.com>,
Guru Das Srinagesh <quic_gurus@quicinc.com>
Subject: [RESEND PATCH v2 0/5] SCM: Add support for wait-queue aware firmware
Date: Tue, 30 Aug 2022 15:25:06 -0700 [thread overview]
Message-ID: <1661898311-30126-1-git-send-email-quic_gurus@quicinc.com> (raw)
This patch series enables the QCOM SCM driver to support firmware (FW) versions
that expect the high-level OS (HLOS) to be tolerant of SCM call requests not
being processed right away and, instead, being placed on a wait-queue in FW and
processed accordingly.
The problem this feature is fixing is as follows. In a scenario where there is
a VM in addition to HLOS (and an underlying hypervisor):
1. HLOS makes an SMC call on core 5
2. The hypervisor scheduling interrupt interrupts this SMC call.
3. The hypervisor schedules the VM on core 5.
4. The VM makes an SMC call on core 5.
5. The SMC call is non-interruptibly stuck on FW spinlock on core 5.
6. HLOS cannot reschedule since core 5 is not responding to Reschedule IPIs.
7. Watchdog timer expires waiting for core 5.
This problem is solved by FW returning a new return code SCM_WAITQ_SLEEP to
HLOS right away when it is overwhelmed by the VM's SMC call. HLOS then places
the call on a wait-queue and wakes it up when it receives an interrupt that
signifies "all-clear".
Additionally, this new design also supports scenarios involving only HLOS (and
no other VMs). Such scenarios make use of a second new return code
SCM_WAITQ_WAKE.
There are three new SMC calls also being defined in this design that, together
with the two new return codes, form the handshake protocol between Linux and
FW.
This design is also backwards-compatible with existing firmware versions that
do not support this feature.
---
v2:
- Changes made to patches 4 and 5 are listed therein.
- Rebased dt-bindings on top of the YAML conversion patch [1].
[1] https://lore.kernel.org/lkml/20220708090431.30437-1-david@ixit.cz/
---
Guru Das Srinagesh (5):
dt-bindings: firmware: qcom-scm: Add "allow-multi-call" property
firmware: qcom: scm: Optionally remove SCM call serialization
dt-bindings: firmware: qcom-scm: Add optional interrupt
firmware: qcom: scm: Add wait-queue helper functions
firmware: qcom: scm: Add wait-queue handling logic
.../devicetree/bindings/firmware/qcom,scm.yaml | 10 ++
drivers/firmware/qcom_scm-smc.c | 140 +++++++++++++++++++--
drivers/firmware/qcom_scm.c | 125 +++++++++++++++++-
drivers/firmware/qcom_scm.h | 14 +++
4 files changed, 279 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2022-08-30 22:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 22:25 Guru Das Srinagesh [this message]
2022-08-30 22:25 ` [RESEND PATCH v2 1/5] dt-bindings: firmware: qcom-scm: Add "allow-multi-call" property Guru Das Srinagesh
2022-08-31 8:00 ` Krzysztof Kozlowski
2022-10-18 5:56 ` Sibi Sankar
2022-08-30 22:25 ` [RESEND PATCH v2 2/5] firmware: qcom: scm: Optionally remove SCM call serialization Guru Das Srinagesh
2022-08-31 8:06 ` Krzysztof Kozlowski
2022-08-30 22:25 ` [RESEND PATCH v2 3/5] dt-bindings: firmware: qcom-scm: Add optional interrupt Guru Das Srinagesh
2022-08-31 8:02 ` Krzysztof Kozlowski
2022-10-18 5:49 ` Sibi Sankar
2022-10-18 13:11 ` Krzysztof Kozlowski
2022-08-30 22:25 ` [RESEND PATCH v2 4/5] firmware: qcom: scm: Add wait-queue helper functions Guru Das Srinagesh
2022-08-31 0:32 ` kernel test robot
2022-08-31 6:30 ` kernel test robot
2022-10-19 22:52 ` Bjorn Andersson
2022-08-30 22:25 ` [RESEND PATCH v2 5/5] firmware: qcom: scm: Add wait-queue handling logic Guru Das Srinagesh
2022-10-19 23:23 ` Bjorn Andersson
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=1661898311-30126-1-git-send-email-quic_gurus@quicinc.com \
--to=quic_gurus@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=david@ixit.cz \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_eberman@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=robimarko@gmail.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®