From: Konrad Dybcio <konradybcio@kernel.org>
To: Tengfei Fan <quic_tengfan@quicinc.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: kernel@quicinc.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] dt-bindings: arm: qcom: Document qcs9100-ride and qcs9100-ride Rev3
Date: Wed, 11 Sep 2024 13:24:03 +0200 [thread overview]
Message-ID: <707f8df3-096f-45e6-a37f-9d9d4ca259e1@kernel.org> (raw)
In-Reply-To: <20240911-add_qcs9100_support-v2-3-e43a71ceb017@quicinc.com>
On 11.09.2024 1:10 PM, Tengfei Fan wrote:
> Document qcs9100-ride and qcs9100-ride Rev3 is based on QCS9100 SoC.
>
> QCS9100 is a IoT version of SA8775p, hence use the latter's compatible
> string as fallback.
>
> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
> ---
Reviewed-by: Konrad Dybcio <konradybcio@kernel.org>
Konrad
next prev parent reply other threads:[~2024-09-11 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 11:10 [PATCH v2 0/4] arm64: dts: qcom: Add support for the QCS9100 SoC and board Tengfei Fan
2024-09-11 11:10 ` [PATCH v2 1/4] dt-bindings: arm: qcom,ids: add SoC ID for QCS9100 Tengfei Fan
2024-09-11 11:10 ` [PATCH v2 2/4] soc: qcom: socinfo: add QCS9100 ID Tengfei Fan
2024-09-11 11:10 ` [PATCH v2 3/4] dt-bindings: arm: qcom: Document qcs9100-ride and qcs9100-ride Rev3 Tengfei Fan
2024-09-11 11:24 ` Konrad Dybcio [this message]
2024-09-16 15:12 ` Krzysztof Kozlowski
2024-09-11 11:10 ` [PATCH v2 4/4] arm64: dts: qcom: qcs9100: Add support for the QCS9100 Ride and Ride Rev3 boards Tengfei Fan
2024-09-16 23:32 ` Konrad Dybcio
2025-01-08 14:55 ` Caleb Connolly
2024-09-11 13:50 ` [PATCH v2 0/4] arm64: dts: qcom: Add support for the QCS9100 SoC and board Rob Herring (Arm)
2024-11-04 4:13 ` (subset) " 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=707f8df3-096f-45e6-a37f-9d9d4ca259e1@kernel.org \
--to=konradybcio@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tengfan@quicinc.com \
--cc=robh@kernel.org \
/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).