From: Krzysztof Kozlowski <krzk@kernel.org>
To: Diederik de Haas <diederik@cknow-tech.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Samuel Holland <samuel@sholland.org>
Cc: hrdl <git@hrdl.eu>, phantomas <phantomas@phantomas.xyz>,
Dragan Simic <dsimic@manjaro.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: Simplify usb-c-connector port on rk3566-pinenote
Date: Sun, 9 Nov 2025 18:37:26 +0100 [thread overview]
Message-ID: <a726fac9-afe5-4639-b06a-4bccc256d98f@kernel.org> (raw)
In-Reply-To: <20251109-rk3566-pinenote-dt-fixes-upstream-v1-1-ed38d200cc04@cknow-tech.com>
On 09/11/2025 18:05, Diederik de Haas wrote:
> The USB-C connector on the PineNote has only 1 port, so there's no need
> for a 'ports' node with address-/size-cells properties as a single
> 'port' node suffices.
>
> This fixes the following DT validation issue:
>
> Warning (graph_child_address): /i2c@fe5c0000/tcpc@60/connector/ports:
> graph node has single child node 'port@0',
> #address-cells/#size-cells are not necessary
This is not a DT validation, but DTC warning which we do not really fix.
Are you sure the 'port' is accepted by bindings?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-09 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 17:05 [PATCH 0/2] Fixes for PineNote DT validation issues Diederik de Haas
2025-11-09 17:05 ` [PATCH 1/2] arm64: dts: rockchip: Simplify usb-c-connector port on rk3566-pinenote Diederik de Haas
2025-11-09 17:37 ` Krzysztof Kozlowski [this message]
2025-11-09 22:16 ` Heiko Stübner
2025-11-10 7:12 ` Krzysztof Kozlowski
2025-11-09 17:05 ` [PATCH 2/2] arm64: dts: rockchip: Move otg-port to controller " Diederik de Haas
2025-11-09 21:52 ` [PATCH 0/2] Fixes for PineNote DT validation issues Diederik de Haas
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=a726fac9-afe5-4639-b06a-4bccc256d98f@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--cc=dsimic@manjaro.org \
--cc=git@hrdl.eu \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=phantomas@phantomas.xyz \
--cc=robh@kernel.org \
--cc=samuel@sholland.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).