From: Krzysztof Kozlowski <krzk@kernel.org>
To: 손신 <shin.son@samsung.com>,
"'Bartlomiej Zolnierkiewicz'" <bzolnier@gmail.com>,
"'Rafael J . Wysocki'" <rafael@kernel.org>,
"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
"'Zhang Rui'" <rui.zhang@intel.com>,
"'Lukasz Luba'" <lukasz.luba@arm.com>,
"'Rob Herring'" <robh@kernel.org>,
"'Conor Dooley'" <conor+dt@kernel.org>,
"'Alim Akhtar'" <alim.akhtar@samsung.com>
Cc: linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: exynosautov920: Add tmu hardware binding
Date: Tue, 2 Sep 2025 11:30:03 +0200 [thread overview]
Message-ID: <3fc54ddb-3947-4c2b-825c-01c16d4c7dab@kernel.org> (raw)
In-Reply-To: <000501dc1be8$e9ac0640$bd0412c0$@samsung.com>
On 02/09/2025 11:06, 손신 wrote:
>
>>
>>> + cpucl0right-thermal {
>>
>> It does not look like you tested the DTS against bindings. Please run
>> `make dtbs_check W=1` (see Documentation/devicetree/bindings/writing-
>> schema.rst or https://protect2.fireeye.com/v1/url?k=004c918d-61c784be-
>> 004d1ac2-000babff9bb7-06e007e7dc12091d&q=1&e=d6a22592-2d45-41f5-b737-
>> a90830cceaeb&u=https%3A%2F%2Fwww.linaro.org%2Fblog%2Ftips-and-tricks-for-
>> validating-devicetree-sources-with-the-devicetree-schema%2F
>> for instructions).
>> Maybe you need to update your dtschema and yamllint. Don't rely on distro
>> packages for dtschema and be sure you are using the latest released
>> dtschema.
>>
>
> Actually, I also updated both dtschema and yamllint and ran "make CHECK_DTBS=y W=1 exynos/exynosautov920-sadk.dtb", but no other issues were detected.
Thanks
> I assume that the problem you mentioned about "cpucl0right-thermal" might be related to the regex.
You actually fit exactly in the limit.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-09-02 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250825064933epcas2p37665fae32f51b04a43e5395d76759143@epcas2p3.samsung.com>
2025-08-25 6:49 ` [PATCH 0/3] Add exynosautov920 thermal support Shin Son
[not found] ` <CGME20250825064933epcas2p33e2b4566b5911fef8d7127900fc10002@epcas2p3.samsung.com>
2025-08-25 6:49 ` [PATCH 1/3] dt-bindings: thermal: samsung: Add tmu-name and sensor-index-ranges properties Shin Son
2025-08-30 9:06 ` Krzysztof Kozlowski
2025-09-02 8:54 ` 손신
[not found] ` <CGME20250825064933epcas2p1e138f8c874f634123590af3bf63e49bd@epcas2p1.samsung.com>
2025-08-25 6:49 ` [PATCH 2/3] thermal: exynos_tmu: Support new hardware and update TMU interface Shin Son
[not found] ` <CGME20250825064933epcas2p40a7c491366097f90add675bc36822ef9@epcas2p4.samsung.com>
2025-08-25 6:49 ` [PATCH 3/3] arm64: dts: exynosautov920: Add tmu hardware binding Shin Son
2025-08-30 9:08 ` Krzysztof Kozlowski
2025-09-02 9:06 ` 손신
2025-09-02 9:30 ` 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=3fc54ddb-3947-4c2b-825c-01c16d4c7dab@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=bzolnier@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=shin.son@samsung.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).