From: Tessolve Upstream <tessolveupstream@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: konradybcio@kernel.org, andersson@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, tingweiz@qti.qualcomm.com
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: add bindings for QCS615 talos evk board
Date: Mon, 15 Sep 2025 11:21:53 +0530 [thread overview]
Message-ID: <433068b2-f899-4b28-8498-e9672b8c0b69@gmail.com> (raw)
In-Reply-To: <33ldjudketkyledzp473bwal4jmrigozjjwqtqlrmrkjmh5sze@ak4cusfossus>
On 09/09/25 19:20, Dmitry Baryshkov wrote:
> On Tue, Sep 09, 2025 at 06:22:54PM +0530, Sudarshan Shetty wrote:
>> This adds binding support for the QCS615-based talos evk SMARC platform.
>>
>> Signed-off-by: Sudarshan Shetty <tessolveupstream@gmail.com>
>> ---
>> Documentation/devicetree/bindings/arm/qcom.yaml | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>> index 03a7d3c92ecd..a5dbe6af68ac 100644
>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>> @@ -952,6 +952,12 @@ properties:
>> - const: qcom,qcs615
>> - const: qcom,sm6150
>>
>> + - items:
>> + - enum:
>> + - qcom,qcs615-iq-615-evk
>
> Should it follow the recent example and be named "qcom,talos-evk" ?
Yes, I’ll update the board compatible to "qcom,talos-evk" in v2.
Thanks for the suggestion.
>
>> + - const: qcom,qcs615
>> + - const: qcom,sm6150
>> +
>> - items:
>> - enum:
>> - qcom,sa8155p-adp
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2025-09-15 5:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 12:52 [PATCH 1/2] dt-bindings: arm: qcom: add bindings for QCS615 talos evk board Sudarshan Shetty
2025-09-09 12:52 ` [PATCH 2/2] arm64: dts: qcom: Add support " Sudarshan Shetty
2025-09-09 13:58 ` Dmitry Baryshkov
2025-09-16 5:52 ` Tessolve Upstream
2025-09-16 10:25 ` Dmitry Baryshkov
2025-09-17 5:30 ` Tessolve Upstream
2025-09-17 13:38 ` Dmitry Baryshkov
2025-09-18 5:23 ` Sudarshan Shetty
2025-09-09 14:02 ` Dmitry Baryshkov
2025-09-09 14:05 ` Krzysztof Kozlowski
2025-09-15 12:23 ` Tessolve Upstream
2025-09-15 12:11 ` Tessolve Upstream
2025-09-09 14:26 ` Bjorn Andersson
2025-09-16 5:47 ` Tessolve Upstream
2025-09-16 10:29 ` Dmitry Baryshkov
2025-09-22 8:54 ` Tessolve Upstream
2025-09-09 13:50 ` [PATCH 1/2] dt-bindings: arm: qcom: add bindings " Dmitry Baryshkov
2025-09-15 5:51 ` Tessolve Upstream [this message]
2025-09-09 13:57 ` Krzysztof Kozlowski
2025-09-15 5:53 ` Tessolve Upstream
2025-09-09 14:27 ` Bjorn Andersson
2025-09-15 5:54 ` Tessolve Upstream
2025-10-10 11:47 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2025-10-10 11:47 ` [PATCH v2 2/2] arm64: dts: qcom: Add support for QCS615 talos evk board Sudarshan Shetty
2025-10-10 12:19 ` Dmitry Baryshkov
2025-10-13 9:04 ` Tessolve Upstream
2025-10-13 9:42 ` Dmitry Baryshkov
2025-10-10 12:13 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Add QCS615 Talos EVK SMARC platform Dmitry Baryshkov
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=433068b2-f899-4b28-8498-e9672b8c0b69@gmail.com \
--to=tessolveupstream@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@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=tingweiz@qti.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).