From: "Heiko Stübner" <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
quentin.schulz@theobroma-systems.com
Subject: Re: [PATCH 0/2] Add support for the dual-role dwc3 controllers on rk3588-tiger
Date: Mon, 22 Apr 2024 09:43:12 +0200 [thread overview]
Message-ID: <2108948.KlZ2vcFHjT@diego> (raw)
In-Reply-To: <171356537191.48026.7238978785873260892.robh@kernel.org>
Hi Rob,
Am Samstag, 20. April 2024, 00:24:23 CEST schrieb Rob Herring:
> On Thu, 18 Apr 2024 23:03:30 +0200, Heiko Stuebner wrote:
> > A comment fix and then the addition of the nodes for the dwc3 controllers
> > using the newly merged usbdp phys.
> >
> > Heiko Stuebner (2):
> > arm64: dts: rockchip: fix comment for upper usb3 port
> > arm64: dts: rockchip: add dual-role usb3 hosts to rk3588 Tiger-Haikou
> >
> > .../boot/dts/rockchip/rk3588-tiger-haikou.dts | 60 ++++++++++++++++++-
> > .../arm64/boot/dts/rockchip/rk3588-tiger.dtsi | 15 +++++
> > 2 files changed, 74 insertions(+), 1 deletion(-)
> >
> > --
> > 2.39.2
> >
> >
> >
>
>
> My bot found new DTB warnings on the .dts files added or changed in this
> series.
>
> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
> are fixed by another series. Ultimately, it is up to the platform
> maintainer whether these warnings are acceptable or not. No need to reply
> unless the platform maintainer has comments.
>
> If you already ran DT checks and didn't see these error(s), then
> make sure dt-schema is up to date:
>
> pip3 install dtschema --upgrade
>
>
> New warnings running 'make CHECK_DTBS=y rockchip/rk3588-tiger-haikou.dtb' for 20240418210332.2394871-1-heiko@sntech.de:
>
> arch/arm64/boot/dts/rockchip/rk3588-tiger-haikou.dtb: /extcon-usb3: failed to match any schema with compatible: ['linux,extcon-usb-gpio']
This follows the txt-binding from
https://www.kernel.org/doc/Documentation/devicetree/bindings/extcon/extcon-usb-gpio.txt
so in mainline there is no yaml binding yet for the usb-id-extcon.
Though I did find a still pending yaml conversion for it in
https://lore.kernel.org/linux-arm-kernel/20240215093214.796821-1-alexander.stein@ew.tq-group.com/T/
Though not sure what the holdup is there as it got a Review from you?
Can you just pick this for the main dt-tree?
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-04-22 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 21:03 [PATCH 0/2] Add support for the dual-role dwc3 controllers on rk3588-tiger Heiko Stuebner
2024-04-18 21:03 ` [PATCH 1/2] arm64: dts: rockchip: fix comment for upper usb3 port Heiko Stuebner
2024-04-22 8:53 ` Quentin Schulz
2024-04-18 21:03 ` [PATCH 2/2] arm64: dts: rockchip: add dual-role usb3 hosts to rk3588 Tiger-Haikou Heiko Stuebner
2024-04-22 9:06 ` Quentin Schulz
2024-04-19 22:24 ` [PATCH 0/2] Add support for the dual-role dwc3 controllers on rk3588-tiger Rob Herring
2024-04-22 7:43 ` Heiko Stübner [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=2108948.KlZ2vcFHjT@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@theobroma-systems.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;
as well as URLs for NNTP newsgroup(s).