Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: Richard Acayan <mailingradian@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Vinod Koul <vkoul@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Chanho Park <chanho61.park@samsung.com>,
	Thierry Reding <treding@nvidia.com>,
	Stephan Gerhold <stephan.gerhold@kernkonzept.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Robert Marko <robimarko@gmail.com>,
	Das Srinagesh <quic_gurus@quicinc.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht, phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] dt-bindings: firmware: scm: add sdm670 compatible
Date: Fri, 4 Nov 2022 00:53:37 +0100	[thread overview]
Message-ID: <dba15541-e85f-6e45-cf44-e44f33788d51@somainline.org> (raw)
In-Reply-To: <20221103230349.212861-4-mailingradian@gmail.com>


On 04/11/2022 00:03, Richard Acayan wrote:
> The Snapdragon 670 uses SCM as for PSCI power management. Document the
> appropriate compatible string for it.

SCM and SMC (and SMCCC) are closely related but not the same.


SMC (secure monitor call) is the standard mechanism of invoking 
communication

with TZ.


SCM (secure channel manager) is a QC mechanism of communicating with their

vast vast vast HYP and TZ implementations, using HVC (hypervisor call) 
and SMC

respectively.


SMCCC (secure monitor call calling convention) is a standard for how to 
structure

SMCs and HVCs.


PSCI uses SMC calls on sdm670.


Konrad

>
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
> Acked-by: Rob Herring <robh@kernel.org>
> Reviewed-by: Guru Das Srinagesh <quic_gurus@quicinc.com>
> ---
>   Documentation/devicetree/bindings/firmware/qcom,scm.yaml | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> index be1b5746eddb..25688571ee7c 100644
> --- a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> +++ b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> @@ -41,6 +41,7 @@ properties:
>             - qcom,scm-sc7180
>             - qcom,scm-sc7280
>             - qcom,scm-sc8280xp
> +          - qcom,scm-sdm670
>             - qcom,scm-sdm845
>             - qcom,scm-sdx55
>             - qcom,scm-sdx65

  reply	other threads:[~2022-11-03 23:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 23:03 [PATCH v2 0/4] Initial SDM670 and Pixel 3a support Richard Acayan
2022-11-03 23:03 ` [PATCH v2 1/4] dt-bindings: arm: cpus: add qcom kryo 360 compatible Richard Acayan
2022-11-03 23:03 ` [PATCH v2 2/4] dt-bindings: arm: qcom: add sdm670 and pixel 3a compatible Richard Acayan
2022-11-03 23:03 ` [PATCH v2 3/4] dt-bindings: firmware: scm: add sdm670 compatible Richard Acayan
2022-11-03 23:53   ` Konrad Dybcio [this message]
2022-11-03 23:03 ` [PATCH v2 4/4] arm64: dts: qcom: add sdm670 and pixel 3a device trees Richard Acayan
2022-11-03 23:49   ` Konrad Dybcio
2022-11-04  2:56     ` Richard Acayan

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=dba15541-e85f-6e45-cf44-e44f33788d51@somainline.org \
    --to=konrad.dybcio@somainline.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=chanho61.park@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mailingradian@gmail.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=quic_gurus@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=robimarko@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=stephan.gerhold@kernkonzept.com \
    --cc=treding@nvidia.com \
    --cc=vkoul@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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