From: Umang Chheda <umang.chheda@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
richardcochran@gmail.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: Add model string
Date: Tue, 10 Mar 2026 14:09:58 +0530 [thread overview]
Message-ID: <64f43d77-7c09-453e-8d7b-b4e0e5f05598@oss.qualcomm.com> (raw)
In-Reply-To: <rdglzhmncexfcvec5hyenj7jx3m5hsphjlxsaeq2zhi4z4arml@bjeqghbbaoa2>
Hello Dmitry,
On 3/10/2026 2:07 AM, Dmitry Baryshkov wrote:
> On Mon, Mar 09, 2026 at 05:49:35PM +0530, Umang Chheda wrote:
>> The RB3 Gen2 Industrial mezzanine DT file lacks a "model" property,
>> resulting in the hardware always being reported as the "Robotics RB3gen2".
>> This prevents applications and user-space tooling from distinguishing
>> the Industrial mezzanine Kit from other RB3Gen2 variants.
>>
>> To ensure consistent identification across all RB3 Gen2 mezzanines,
>> add the appropriate model string.
>>
>> Signed-off-by: Umang Chheda <umang.chheda@oss.qualcomm.com>
>> ---
>> .../boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso
>> index 619a42b5ef48..7d6e425dae89 100644
>> --- a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso
>> +++ b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-industrial-mezzanine.dtso
>> @@ -8,6 +8,10 @@
>> #include <dt-bindings/clock/qcom,gcc-sc7280.h>
>> #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
>>
>> +&{/} {
>> + model = "Qualcomm Technologies, Inc. QCS6490 RB3gen2 Industrial Mezzanine";
> So, what happens if I combine Industrial and Vision mezzanines?
H/W does not support to connect both Industrial and vision mezzanine at same time - only single mezzanine can be
connected at a given point in time - hence probably the above scenario would never occur.
>
>> +};
>> +
>> &spi11 {
>> #address-cells = <1>;
>> #size-cells = <0>;
>> --
>> 2.34.1
>>
Thanks,
Umang
next prev parent reply other threads:[~2026-03-10 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 12:19 [PATCH 1/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: Add model string Umang Chheda
2026-03-09 12:19 ` [PATCH 2/2] arm64: dts: qcom: qcs6490-rb3gen2-vision-mezzanine: " Umang Chheda
2026-03-09 20:40 ` Dmitry Baryshkov
2026-03-09 20:37 ` [PATCH 1/2] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: " Dmitry Baryshkov
2026-03-10 8:39 ` Umang Chheda [this message]
2026-03-13 17:53 ` Dmitry Baryshkov
2026-03-23 17:03 ` Umang Chheda
2026-03-23 19:06 ` Dmitry Baryshkov
2026-03-26 2:59 ` Bjorn Andersson
2026-04-01 15:21 ` Umang Chheda
2026-04-01 15:39 ` Krzysztof Kozlowski
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=64f43d77-7c09-453e-8d7b-b4e0e5f05598@oss.qualcomm.com \
--to=umang.chheda@oss.qualcomm.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=richardcochran@gmail.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