mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: quic_sibis@quicinc.com, srinivas.kandagatla@linaro.org
Cc: quic_gurus@quicinc.com, robh+dt@kernel.org, robimarko@gmail.com,
	krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	konrad.dybcio@somainline.org, agross@kernel.org
Subject: Re: [PATCH V10 0/2] SCM: Add support for wait-queue aware firmware
Date: Wed, 18 Jan 2023 22:53:59 -0600	[thread overview]
Message-ID: <167410403677.3048186.12291874601679971916.b4-ty@kernel.org> (raw)
In-Reply-To: <20230113161114.22607-1-quic_sibis@quicinc.com>

On Fri, 13 Jan 2023 21:41:12 +0530, Sibi Sankar wrote:
> 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):
> 
> [...]

Applied, thanks!

[1/2] dt-bindings: firmware: qcom,scm: Add optional interrupt
      commit: afb37e2577938bb854f20d428d8f29a01ea8bc93
[2/2] firmware: qcom: scm: Add wait-queue handling logic
      commit: 6bf32599223634294cdc6efb359ffaab1d68073c

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2023-01-19  5:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 16:11 Sibi Sankar
2023-01-13 16:11 ` [PATCH V10 1/2] dt-bindings: firmware: qcom,scm: Add optional interrupt Sibi Sankar
2023-01-13 16:11 ` [PATCH V10 2/2] firmware: qcom: scm: Add wait-queue handling logic Sibi Sankar
2023-01-13 22:16   ` Guru Das Srinagesh
2023-01-19  4:53 ` Bjorn Andersson [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=167410403677.3048186.12291874601679971916.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_gurus@quicinc.com \
    --cc=quic_sibis@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=robimarko@gmail.com \
    --cc=srinivas.kandagatla@linaro.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

all inboxes | Powered by JetHome®