public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>, Gabor Juhos <j4g8y7@gmail.com>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: marvell: armada-37xx: drop 'marvell,usb-misc-reg' properties
Date: Thu, 05 Mar 2026 08:54:34 +0100	[thread overview]
Message-ID: <874imug18l.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <db997887-2431-4baa-8e96-04f53ea59060@lunn.ch>

Hello Andrew,

> On Wed, Mar 04, 2026 at 08:12:43PM +0100, Gabor Juhos wrote:
>> The 'marvell,usb-misc-reg' property is present both in the EHCI and
>> in the XHCI USB host device nodes, however it is not documented. Thus
>> 'make dtbs_check' produces warnings like these:
>> 
>>   /arch/arm64/boot/dts/marvell/armada-3720-db.dtb: usb@58000 (marvell,armada3700-xhci): Unevaluated properties are not allowed ('marvell,usb-misc-reg' was unexpected)
>>           from schema $id: http://devicetree.org/schemas/usb/generic-xhci.yaml
>>   /arch/arm64/boot/dts/marvell/armada-3720-db.dtb: usb@5e000 (marvell,armada-3700-ehci): Unevaluated properties are not allowed ('marvell,usb-misc-reg' was unexpected)
>>           from schema $id: http://devicetree.org/schemas/usb/generic-ehci.yaml
>> 
>> Apart from the fact that the properties are not documented, those are
>> not even used by any USB host drivers. At least 'git grep' says this:
>> 
>>   $ git grep -n 'marvell.usb-misc-reg' v7.0-rc2
>>   v7.0-rc2:Documentation/devicetree/bindings/phy/marvell,armada-3700-utmi-phy.yaml:30:  marvell,usb-misc-reg:
>>   v7.0-rc2:Documentation/devicetree/bindings/phy/marvell,armada-3700-utmi-phy.yaml:41:  - marvell,usb-misc-reg
>>   v7.0-rc2:Documentation/devicetree/bindings/phy/marvell,armada-3700-utmi-phy.yaml:50:      marvell,usb-misc-reg = <&usb2_syscon>;
>>   v7.0-rc2:arch/arm64/boot/dts/marvell/armada-37xx.dtsi:372:                              marvell,usb-misc-reg = <&usb32_syscon>;
>>   v7.0-rc2:arch/arm64/boot/dts/marvell/armada-37xx.dtsi:383:                              marvell,usb-misc-reg = <&usb32_syscon>;
>>   v7.0-rc2:arch/arm64/boot/dts/marvell/armada-37xx.dtsi:396:                              marvell,usb-misc-reg = <&usb2_syscon>;
>>   v7.0-rc2:arch/arm64/boot/dts/marvell/armada-37xx.dtsi:406:                              marvell,usb-misc-reg = <&usb2_syscon>;
>>   v7.0-rc2:drivers/phy/marvell/phy-mvebu-a3700-utmi.c:231:                                                         "marvell,usb-misc-reg");
>

I don't follow:

> The phy-mvebu-a3700-utmi.c does use it, and does document it:
>
>   marvell,usb-misc-reg:
>     description:
>       Phandle on the "USB miscellaneous registers" shared region
>       covering registers related to both the host controller and
>       the PHY.
>     $ref: /schemas/types.yaml#/definitions/phandle
>
> And the patch which added the property to the USB nodes also added the
> PHY nodes.
>
> commit 05d168a56fae8ff50432d5dfe6e7423b989455a8
> Author: Miquel Raynal <miquel.raynal@bootlin.com>
> Date:   Tue Jan 29 10:36:34 2019 +0100
>
>     arm64: dts: marvell: armada-37xx: declare USB2 UTMI PHYs
>

You stated that the property is used and was properly added.

> So this change does lookcorrect.

But here you agree with removing it.

I am lost :)

Gregory

>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>
>     Andrew

-- 
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2026-03-05  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 19:12 [PATCH] arm64: dts: marvell: armada-37xx: drop 'marvell,usb-misc-reg' properties Gabor Juhos
2026-03-04 19:48 ` Andrew Lunn
2026-03-05  7:54   ` Gregory CLEMENT [this message]
2026-03-05 13:28     ` Andrew Lunn
2026-03-05 19:51       ` Gabor Juhos
2026-03-13 15:57         ` Gregory CLEMENT

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=874imug18l.fsf@BLaptop.bootlin.com \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j4g8y7@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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