The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Wasim Nazir <quic_wasimn@quicinc.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@quicinc.com,
	kernel@oss.qualcomm.com
Subject: Re: [PATCH v8 1/4] dt-bindings: arm: qcom: Add bindings for QCS9075 SOC based board
Date: Wed, 28 May 2025 17:20:56 -0500	[thread overview]
Message-ID: <20250528222056.GA907125-robh@kernel.org> (raw)
In-Reply-To: <20250528122753.3623570-2-quic_wasimn@quicinc.com>

On Wed, May 28, 2025 at 05:57:48PM +0530, Wasim Nazir wrote:
> QCS9075 is compatible Industrial-IOT grade variant of SA8775p SOC.
> Unlike QCS9100, it doesn't have safety monitoring feature of
> Safety-Island(SAIL) subsystem, which affects thermal management.
> 
> qcs9075-iq-9075-evk board is based on QCS9075 SOC.
> 
> Signed-off-by: Wasim Nazir <quic_wasimn@quicinc.com>

This is missing Krzysztof's ack.

> ---
>  Documentation/devicetree/bindings/arm/qcom.yaml | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 56f78f0f3803..3b2c60af12cd 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -58,6 +58,7 @@ description: |
>          qcs8550
>          qcm2290
>          qcm6490
> +        qcs9075
>          qcs9100
>          qdu1000
>          qrb2210
> @@ -961,6 +962,12 @@ properties:
>                - qcom,sa8775p-ride-r3
>            - const: qcom,sa8775p
> 
> +      - items:
> +          - enum:
> +              - qcom,qcs9075-iq-9075-evk
> +          - const: qcom,qcs9075
> +          - const: qcom,sa8775p
> +
>        - items:
>            - enum:
>                - qcom,qcs9100-ride
> --
> 2.49.0
> 

  reply	other threads:[~2025-05-28 22:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 12:27 [PATCH v8 0/4] qcom: Add support for IQ-9075-evk board Wasim Nazir
2025-05-28 12:27 ` [PATCH v8 1/4] dt-bindings: arm: qcom: Add bindings for QCS9075 SOC based board Wasim Nazir
2025-05-28 22:20   ` Rob Herring [this message]
2025-05-29  6:29     ` Krzysztof Kozlowski
2025-05-29  8:55       ` Wasim Nazir
2025-05-29  8:51     ` Wasim Nazir
2025-05-28 12:27 ` [PATCH v8 2/4] arm64: dts: qcom: iq9: Introduce new memory map for qcs9100/qcs9075 Wasim Nazir
2025-05-28 12:27 ` [PATCH v8 3/4] arm64: dts: qcom: qcs9075: Introduce QCS9075 SOM Wasim Nazir
2025-05-28 12:27 ` [PATCH v8 4/4] arm64: dts: qcom: Add support for qcs9075 IQ-9075-EVK Wasim Nazir
2025-05-29  2:36 ` [PATCH v8 0/4] qcom: Add support for IQ-9075-evk board Rob Herring (Arm)

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=20250528222056.GA907125-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@oss.qualcomm.com \
    --cc=kernel@quicinc.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_wasimn@quicinc.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