From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marek Vasut <marex@nabladev.com>
Cc: linux-usb@vger.kernel.org, "Pankaj Dev" <pankaj.dev@st.com>,
"Clément Le Goffic" <clement.legoffic@foss.st.com>,
"Gatien Chevallier" <gatien.chevallier@foss.st.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Christian Bruel" <christian.bruel@foss.st.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Fabrice Gasnier" <fabrice.gasnier@foss.st.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Rahul Kumar" <rahul.kumar05@st.com>,
"Rob Herring" <robh@kernel.org>, "Rosen Penev" <rosenp@gmail.com>,
"Thinh Nguyen" <Thinh.Nguyen@synopsys.com>,
"Vinod Koul" <vkoul@kernel.org>,
devicetree@vger.kernel.org, kernel@dh-electronics.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2 5/9] dt-bindings: usb: dwc3: Document ST STM32MP2 DWC3 xHCI USB controller
Date: Tue, 18 Aug 2026 10:15:54 +0200 [thread overview]
Message-ID: <20260818-brainy-burgundy-monkey-fc2a0d@quoll> (raw)
In-Reply-To: <20260816213849.1044073-6-marex@nabladev.com>
On Sun, Aug 16, 2026 at 11:37:07PM +0200, Marek Vasut wrote:
> +properties:
> + compatible:
> + const: st,stm32mp25-dwc3
> +
> + reg:
> + maxItems: 1
> +
> + access-controllers:
> + maxItems: 1
> +
> + clocks:
> + minItems: 3
> + maxItems: 3
> +
> + clock-names:
> + items:
> + - const: ref
> + - const: bus_early
> + - const: suspend
> +
> + dr_mode:
> + $ref: /schemas/types.yaml#/definitions/string
> + enum: [host, peripheral, otg]
> +
> + interrupts:
> + maxItems: 1
> +
> + phys:
> + minItems: 1
> + maxItems: 2
> +
> + phy-names:
> + minItems: 1
> + items:
> + - const: usb2-phy
> + - const: usb3-phy
> +
> + resets:
> + minItems: 1
Hm? You keep coming with some odd style, not present in any other files.
Where do you see such code - property followed by minItems alone? This
applies to other places as well.
> +
> + st,syscfg:
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + description: Phandle to system configuration controller.
> + items:
> + - items:
> + - description: phandle to syscfg
> + - description: USB3DR control offset within syscfg
> +
> + st,enable-port-power-control:
> + type: boolean
> + description: Enable Host-Mode Port Power Control (bit-3 of capability param HCCPARAMS)
Why wouldn't this be enavled always? Why is this a board-level property?
> +
> + st,ovrcur-active-low:
Don't re-invent stuff:
st,over-current-active-low
> + type: boolean
> + description: Over-Current signal polarity is active-low
> +
> + st,vbusen-active-low:
> + type: boolean
> + description: VBUS-ENABLE signal polarity is active-low
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - interrupts
> + - phys
> + - phy-names
> + - resets
> + - st,syscfg
> +
> +unevaluatedProperties: false
So where did you reference any other schema - for properties here and
for this unevaluatedProps?
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/st,stm32mp25-rcc.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/reset/st,stm32mp25-rcc.h>
> +
> + usb3dr: usb@48300000 {
Drop unused label
> + compatible = "st,stm32mp25-dwc3";
> + reg = <0x48300000 0x100000>;
> + clocks = <&rcc CK_KER_USB2PHY2>, <&rcc CK_BUS_USB3DR>, <&rcc CK_KER_USB2PHY2>;
> + clock-names = "ref", "bus_early", "suspend";
> + interrupts = <GIC_SPI 228 IRQ_TYPE_LEVEL_HIGH>;
> + phys = <&usb2_phy>, <&usb3_phy>;
> + phy-names = "usb2-phy", "usb3-phy";
> + resets = <&rcc USB3DR_R>;
> + st,ovrcur-active-low;
> + st,syscfg = <&syscfg 0x4800>;
> + st,vbusen-active-low;
> + };
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-08-18 8:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 21:37 [PATCH v2 0/9] arm64: dts: phy: st: usb: Add STM32MP2 USB support Marek Vasut
2026-08-16 21:37 ` [PATCH v2 1/9] dt-bindings: phy: Document ST STM32MP25 USB2-FEMTO PHY Marek Vasut
2026-08-18 8:09 ` Krzysztof Kozlowski
2026-08-18 15:11 ` Marek Vasut
2026-08-16 21:37 ` [PATCH v2 2/9] phy: stm32: Add support for " Marek Vasut
2026-08-17 16:22 ` Fabrice Gasnier
2026-08-17 19:43 ` Marek Vasut
2026-08-18 9:28 ` Fabrice Gasnier
2026-08-18 9:53 ` Marek Vasut
2026-08-16 21:37 ` [PATCH v2 3/9] dt-bindings: usb: generic-ehci: Document access-controllers property Marek Vasut
2026-08-16 21:37 ` [PATCH v2 4/9] dt-bindings: usb: generic-ohci: " Marek Vasut
2026-08-16 21:37 ` [PATCH v2 5/9] dt-bindings: usb: dwc3: Document ST STM32MP2 DWC3 xHCI USB controller Marek Vasut
2026-08-18 8:15 ` Krzysztof Kozlowski [this message]
2026-08-18 15:31 ` Marek Vasut
2026-08-16 21:37 ` [PATCH v2 6/9] usb: dwc3: dwc3-generic-plat: Add ST STM32MP2 DWC3 xHCI USB controller glue Marek Vasut
2026-08-16 21:37 ` [PATCH v2 7/9] dt-bindings: arm: stm32: Switch st,stm32mp23/25-syscfg into simple-mfd Marek Vasut
2026-08-18 8:17 ` Krzysztof Kozlowski
2026-08-18 15:32 ` Marek Vasut
2026-08-16 21:37 ` [PATCH v2 8/9] arm64: dts: st: Add USB nodes on stm32mp231 Marek Vasut
2026-08-18 8:19 ` Krzysztof Kozlowski
2026-08-16 21:37 ` [PATCH v2 9/9] arm64: dts: st: Add USB nodes on stm32mp251 Marek Vasut
2026-08-17 16:35 ` [PATCH v2 0/9] arm64: dts: phy: st: usb: Add STM32MP2 USB support Fabrice Gasnier
2026-08-17 19:48 ` Marek Vasut
2026-08-18 16:07 ` Fabrice Gasnier
2026-08-18 16:35 ` Marek Vasut
2026-08-19 15:19 ` Fabrice Gasnier
2026-08-19 15:44 ` Marek Vasut
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=20260818-brainy-burgundy-monkey-fc2a0d@quoll \
--to=krzk@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=christian.bruel@foss.st.com \
--cc=clement.legoffic@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=gatien.chevallier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=marex@nabladev.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=pankaj.dev@st.com \
--cc=rahul.kumar05@st.com \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=vkoul@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