From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Umang Chheda <umang.chheda@oss.qualcomm.com>,
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: Wed, 1 Apr 2026 17:39:12 +0200 [thread overview]
Message-ID: <aa953eb1-39f1-4162-9884-d5de9cc49903@kernel.org> (raw)
In-Reply-To: <acSfUEVueSR5Ikq7@baldur>
On 26/03/2026 03:59, Bjorn Andersson wrote:
>>
>>> considering above point - is it okay to have this patch ? I believe it would be good to have model string in the DTSO file added.
>>
>> No. A _mezzanine_ can not be a device model. It is by definition
>> something that you plug into the main device. Maybe creating something
>> new, a new kit.
>>
>> Moreover, the model name is not an ABI, we should not be using it for
>> device identification.
>>
>
> I do agree.
>
> That said, as we (others) discussed during LPC, it would be very useful
> for bug reporting purposes to know what overlays has been applied - or
> in general what "version" of the dtb we're running the system from.
>
> I don't think "model" is what we're looking for there though.
No, it's not. Prepending compatible is one way, but that cannot be done
directly by DTSO. In my notes from LPC I have also top-level config node
(there is patch for U-Boot for that). And I finished my notes around
that time, so I don't have more ideas...
Best regards,
Krzysztof
prev parent reply other threads:[~2026-04-01 15:39 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
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 [this message]
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=aa953eb1-39f1-4162-9884-d5de9cc49903@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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=umang.chheda@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