From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SM8850
Date: Thu, 23 Oct 2025 08:18:27 +0200 [thread overview]
Message-ID: <118dfd79-f65f-4845-9436-b6be99a5223c@kernel.org> (raw)
In-Reply-To: <20251022-knp-socid-v2-1-d147eadd09ee@oss.qualcomm.com>
On 23/10/2025 06:57, Jingyi Wang wrote:
> Add the ID for the Qualcomm SM8850 SoC which represents the Kaanapali
> platform.
>
> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
> ---
> include/dt-bindings/arm/qcom,ids.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/dt-bindings/arm/qcom,ids.h b/include/dt-bindings/arm/qcom,ids.h
> index cb8ce53146f0..19598ed4679e 100644
> --- a/include/dt-bindings/arm/qcom,ids.h
> +++ b/include/dt-bindings/arm/qcom,ids.h
> @@ -286,6 +286,7 @@
> #define QCOM_ID_IPQ5424 651
> #define QCOM_ID_QCM6690 657
> #define QCOM_ID_QCS6690 658
> +#define QCOM_ID_SM8850 660
Why no QCOM_ID_KAANAPALI?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-23 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 4:57 [PATCH v2 0/2] Add Qualcomm SM8850 socinfo Jingyi Wang
2025-10-23 4:57 ` [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SM8850 Jingyi Wang
2025-10-23 6:18 ` Krzysztof Kozlowski [this message]
2025-10-23 6:25 ` Jingyi Wang
2025-10-23 6:46 ` Krzysztof Kozlowski
2025-10-23 4:57 ` [PATCH v2 2/2] soc: qcom: socinfo: Add SM8850 SoC ID Jingyi Wang
2025-10-27 22:36 ` [PATCH v2 0/2] Add Qualcomm SM8850 socinfo Bjorn Andersson
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=118dfd79-f65f-4845-9436-b6be99a5223c@kernel.org \
--to=krzk@kernel.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=robh@kernel.org \
--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