From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Markus Niebel <Markus.Niebel@ew.tq-group.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@ew.tq-group.com
Subject: Re: [PATCH 5/5] ARM: dts: imx6qdl: Rename USB hub node name
Date: Tue, 13 Aug 2024 11:44:28 +0200 [thread overview]
Message-ID: <82ee2be2-366e-40b2-ac95-e755443032be@kernel.org> (raw)
In-Reply-To: <1901821.CQOukoFCf9@steina-w>
On 13/08/2024 11:27, Alexander Stein wrote:
> Am Dienstag, 13. August 2024, 11:20:08 CEST schrieb Krzysztof Kozlowski:
>> On 12/08/2024 16:34, Markus Niebel wrote:
>>> From: Alexander Stein <alexander.stein@ew.tq-group.com>
>>>
>>> According to microchip,usb2514.yaml the node name shall be usb-hub.
>>
>> That's not true. The schema does not say anything like this. Old name is
>> correct. NAK.
>
> So, is the schema incorrect? There is the dtbs_check warning:
> arch/arm/boot/dts/nxp/imx/imx6q-mba6b.dtb: hub@1: $nodename:0: 'hub@1' does not match '^usb(@.*)?'
> from schema $id: http://devicetree.org/schemas/usb/microchip,usb2514.yaml#
If you have a warning, shorten it and paste it so this will be obvious.
If you look at several bindings, the hub is widely used name. I think
the schema is not correct here - I do not see any properties from
usb.yaml being used here (for usb2514). What's more, if you compare
usb2514 with any other on-board HUB representations (because that's the
only point why we have it in bindings, right?), none of them reference
usb(-hcd)?.yaml.
These are not USB controllers, IMO.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-13 9:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 14:34 [PATCH 0/5] TQMa6x / MBa6x DT improvements Markus Niebel
2024-08-12 14:34 ` [PATCH 1/5] arm: dts: imx6qdl-tqma6: move i2c3 pinmux to imx6qdl-tqma6b Markus Niebel
2024-08-12 14:34 ` [PATCH 2/5] arm: dts: imx6qdl-tqma6: improve compatible for LM75 temp sensor Markus Niebel
2024-08-12 14:34 ` [PATCH 3/5] arm: dts: imx6qdl-mba6: " Markus Niebel
2024-08-12 14:34 ` [PATCH 4/5] arm: dts: imx6qdl-mba6b: remove doubled entry for I2C1 pinmux Markus Niebel
2024-08-12 14:34 ` [PATCH 5/5] ARM: dts: imx6qdl: Rename USB hub node name Markus Niebel
2024-08-12 15:13 ` Niebel, Markus
2024-08-13 9:20 ` Krzysztof Kozlowski
2024-08-13 9:27 ` Alexander Stein
2024-08-13 9:44 ` Krzysztof Kozlowski [this message]
2024-08-13 11:02 ` Alexander Stein
2024-08-13 13:13 ` Niebel, Markus
2024-08-13 16:13 ` Krzysztof Kozlowski
2024-08-28 3:26 ` [PATCH 0/5] TQMa6x / MBa6x DT improvements Shawn Guo
2024-08-28 11:40 ` Niebel, Markus
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=82ee2be2-366e-40b2-ac95-e755443032be@kernel.org \
--to=krzk@kernel.org \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).