Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Roger Shimizu <rosh@debian.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	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: [PATCH] arm64: dts: qcom: qcs6490: Add Thundercomm AI Mini PC G1 IoT
Date: Mon, 9 Feb 2026 09:31:19 +0100	[thread overview]
Message-ID: <24cfbe35-c611-4d52-8a4c-b437287717f0@oss.qualcomm.com> (raw)
In-Reply-To: <CAEQ9gEkA-Gw=96LJe3vf3S6ada5o-mDqjY9B6NNpSaO8saSfvg@mail.gmail.com>

On 2/7/26 6:46 AM, Roger Shimizu wrote:
> On Fri, Feb 6, 2026 at 2:20 AM Konrad Dybcio
> <konrad.dybcio@oss.qualcomm.com> wrote:
>>
>> On 2/6/26 10:55 AM, Roger Shimizu wrote:
>>> On Fri, Feb 6, 2026 at 1:41 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>>>
>>>> On 04/02/2026 10:20, Konrad Dybcio wrote:
>>>>> On 1/31/26 11:31 AM, Roger Shimizu wrote:
>>>>>> ---
>>>>>
>>>>> [...]
>>>>>
>>>>>> +/ {
>>>>>> +    model = "Thundercomm AI Mini PC G1 IoT";
>>>>>> +    compatible = "qcom,sc7280", "qcom,qcm6490";
>>>>>
>>>>> You need to add a board-specific compatible here, see:
>>>>>
>>>>> Documentation/devicetree/bindings/arm/qcom.yaml
>>>>
>>>> The true problem is that this would probably fail validation, so I
>>>> suspect this was never tested/checked.
>>>
>>> Thanks for the review!
>>> I did test this device-tree with the board.
>>> If you mean some other test, please let me know in detail.
>>
>> make ... CHECK_DTBS=1 qcom/qcs6490-thundercomm-minipc-g1iot.dtb
> 
> Thanks for the guide!
> I tested above command, it was passed for my v1.
> Sure, it also passes after I add the board-specific compatible. (not send yet)
> 
>> make ... dt_binding_check
> 
> Sorry, I never can run this check command. It reports many python syntax error.
> I guess the script has issue, or it needs patch to run on my Debian system.
> I'll report the issue to upstream separately.

It may be that your version of pydtschema is wildly out of date.

Nowadays the general expectation for using bleeding-edge python
tools seems to be for one to grab them via pipx

Konrad

  reply	other threads:[~2026-02-09  8:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31 10:31 [PATCH] arm64: dts: qcom: qcs6490: Add Thundercomm AI Mini PC G1 IoT Roger Shimizu
2026-02-04  2:51 ` Dmitry Baryshkov
2026-02-04  8:53   ` Roger Shimizu
2026-02-04  9:20 ` Konrad Dybcio
2026-02-05  0:04   ` Roger Shimizu
2026-02-05  8:52     ` Konrad Dybcio
2026-02-06  9:35       ` Roger Shimizu
2026-02-06  9:41   ` Krzysztof Kozlowski
2026-02-06  9:55     ` Roger Shimizu
2026-02-06  9:57       ` Konrad Dybcio
2026-02-07  5:46         ` Roger Shimizu
2026-02-09  8:31           ` Konrad Dybcio [this message]
2026-02-11  7:27             ` Roger Shimizu
2026-02-12  9:04               ` Konrad Dybcio

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=24cfbe35-c611-4d52-8a4c-b437287717f0@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rosh@debian.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