From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sibi Sankar <quic_sibis@quicinc.com>,
andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org
Cc: agross@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, konrad.dybcio@somainline.org,
robimarko@gmail.com, quic_gurus@quicinc.com,
quic_rjendra@quicinc.com
Subject: Re: [PATCH V6 1/2] dt-bindings: firmware: qcom,scm: Add optional interrupt
Date: Thu, 8 Dec 2022 08:59:17 +0100 [thread overview]
Message-ID: <a2653b17-4ed4-6fe3-ca46-6f8917a58171@linaro.org> (raw)
In-Reply-To: <20221208064031.2875-2-quic_sibis@quicinc.com>
On 08/12/2022 07:40, Sibi Sankar wrote:
> From: Guru Das Srinagesh <quic_gurus@quicinc.com>
>
> Add an interrupt specification to the bindings to support the wait-queue
> feature on SM8450 SoCs.
>
> Signed-off-by: Guru Das Srinagesh <quic_gurus@quicinc.com>
> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
> ---
>
> The interrupt property for scm firmware from a binding perspective is
> completely optional i.e. not all tz fw running in the wild on sm8450
> devices support this feature. The bootloader does the interrupt property
> addition on sm8450 devices with wait-queue support.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-08 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 6:40 [PATCH V6 0/2] SCM: Add support for wait-queue aware firmware Sibi Sankar
2022-12-08 6:40 ` [PATCH V6 1/2] dt-bindings: firmware: qcom,scm: Add optional interrupt Sibi Sankar
2022-12-08 7:59 ` Krzysztof Kozlowski [this message]
2022-12-08 6:40 ` [PATCH V6 2/2] firmware: qcom: scm: Add wait-queue handling logic Sibi Sankar
2022-12-08 22:11 ` Bjorn Andersson
2023-01-10 7:56 ` Guru Das Srinagesh
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=a2653b17-4ed4-6fe3-ca46-6f8917a58171@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@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_rjendra@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robh+dt@kernel.org \
--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®