devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugen Hristev <eugen.hristev@linaro.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Robert Marko <robimarko@gmail.com>,
	Das Srinagesh <quic_gurus@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, aiqun.yu@oss.qualcomm.com,
	tingwei.zhang@oss.qualcomm.com, trilok.soni@oss.qualcomm.com,
	yijie.yang@oss.qualcomm.com
Subject: Re: [PATCH 3/3] dt-bindings: firmware: qcom,scm: document SCM on Kaanapali SOC
Date: Fri, 3 Oct 2025 14:53:40 +0300	[thread overview]
Message-ID: <8e687353-f505-4122-bd46-57ba0d84dabf@linaro.org> (raw)
In-Reply-To: <20250924-knp-soc-binding-v1-3-93a072e174f9@oss.qualcomm.com>



On 9/25/25 02:31, Jingyi Wang wrote:
> Document scm compatible for the Qualcomm Kaanapali SoC. It is an interface
> to communicate to the secure firmware.

Same nitpicks on subject name and extra sentence

Reviewed-by: Eugen Hristev <eugen.hristev@linaro.org>
> 
> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
> ---
>  Documentation/devicetree/bindings/firmware/qcom,scm.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> index ef97faac7e47..340b754e6322 100644
> --- a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> +++ b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
> @@ -31,6 +31,7 @@ properties:
>            - qcom,scm-ipq806x
>            - qcom,scm-ipq8074
>            - qcom,scm-ipq9574
> +          - qcom,scm-kaanapali
>            - qcom,scm-mdm9607
>            - qcom,scm-milos
>            - qcom,scm-msm8226
> @@ -202,6 +203,7 @@ allOf:
>            compatible:
>              contains:
>                enum:
> +                - qcom,scm-kaanapali
>                  - qcom,scm-milos
>                  - qcom,scm-sm8450
>                  - qcom,scm-sm8550
> 


      reply	other threads:[~2025-10-03 11:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 23:31 [PATCH 0/3] dt-bindings: soc: qcom: Add Kaanapali soc related bindings Jingyi Wang
2025-09-24 23:31 ` [PATCH 1/3] dt-bindings: soc: qcom: add qcom,kaanapali-imem compatible Jingyi Wang
2025-10-03 11:46   ` Eugen Hristev
2025-09-24 23:31 ` [PATCH 2/3] dt-bindings: soc: qcom,aoss-qmp: Document the Kaanapali AOSS channel Jingyi Wang
2025-10-03 11:47   ` Eugen Hristev
2025-09-24 23:31 ` [PATCH 3/3] dt-bindings: firmware: qcom,scm: document SCM on Kaanapali SOC Jingyi Wang
2025-10-03 11:53   ` Eugen Hristev [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=8e687353-f505-4122-bd46-57ba0d84dabf@linaro.org \
    --to=eugen.hristev@linaro.org \
    --cc=aiqun.yu@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jingyi.wang@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_gurus@quicinc.com \
    --cc=robh@kernel.org \
    --cc=robimarko@gmail.com \
    --cc=tingwei.zhang@oss.qualcomm.com \
    --cc=trilok.soni@oss.qualcomm.com \
    --cc=yijie.yang@oss.qualcomm.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;
as well as URLs for NNTP newsgroup(s).