From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: 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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2] arm64: dts: qcom: sm8750-mtp: Add WiFi and Bluetooth
Date: Wed, 13 Aug 2025 20:49:56 +0200 [thread overview]
Message-ID: <8fc497df-116e-4df2-a33f-bd71476ce065@kernel.org> (raw)
In-Reply-To: <3jrs5gkxzjgrjmfbd65qr3uzblzzz5ae4apo5qwpxb63jm4i23@jzpaxp3dxais>
On 12/08/2025 14:45, Dmitry Baryshkov wrote:
>
>> Devices will be different, they will have different compatibles, thus
>> you CANNOT have one DTS for both. What else - not my task, not my
>> expertise, not relevant to this submission.
>
> Them having different compatibles is exactly my question. It's not
> obvious if they are compatible or not.
So we talk about basics now... even if devices are compatible, they will
have different "compatible" property, so your question about
compatibility does not matter. They could be compatible or could be not.
Different DTS in both cases, so this is just bikeschedding this patch.
>
> We've discussed this offline and I hope that the next iteration will
> cover all these details.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-13 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 13:10 [RFC PATCH v2] arm64: dts: qcom: sm8750-mtp: Add WiFi and Bluetooth Krzysztof Kozlowski
2025-08-11 14:22 ` Dmitry Baryshkov
2025-08-11 14:25 ` Krzysztof Kozlowski
2025-08-11 14:33 ` Dmitry Baryshkov
2025-08-11 14:40 ` Krzysztof Kozlowski
2025-08-12 11:00 ` Dmitry Baryshkov
2025-08-12 11:07 ` Krzysztof Kozlowski
2025-08-12 12:45 ` Dmitry Baryshkov
2025-08-13 18:49 ` Krzysztof Kozlowski [this message]
2025-08-13 19:07 ` 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=8fc497df-116e-4df2-a33f-bd71476ce065@kernel.org \
--to=krzk@kernel.org \
--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=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).