From: Charan Pedumuru <charan.pedumuru@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Herve Codina <herve.codina@bootlin.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: usb: atmel,at91rm9200-ohci: convert to DT schema
Date: Wed, 4 Feb 2026 18:45:00 +0530 [thread overview]
Message-ID: <7bb66a07-51c5-4e9a-b484-e96a8f12c783@gmail.com> (raw)
In-Reply-To: <20260201-atmel-usb-v1-1-d1a3e93003f1@gmail.com>
On 01-02-2026 17:04, Charan Pedumuru wrote:
> Convert Atmel AT91RM9200 / AT91SAM9 style OHCI USB Host
> Controller binding to DT schema.
> Changes during conversion:
> - Include "usb-ohci" as a fallback compatible to allow at91 OHCI
> driver matching.
>
> Signed-off-by: Charan Pedumuru <charan.pedumuru@gmail.com>
> ---
> .../bindings/usb/atmel,at91rm9200-ohci.yaml | 85 ++++++++++++++++++++++
> 1 file changed, 85 insertions(+)
Hi Rob,
For this patch, can I modify the existing generic-ohci.yaml file to include the compatible "atmel,at91rm9200-ohci" to it and define missing properties, as the fall back compatible "usb-ohci" is already defined for other vendors there, can I drop this patch and make changes for generic-ohci.yaml file and include it in the patch series for the next revision?
>
> diff --git a/Documentation/devicetree/bindings/usb/atmel,at91rm9200-ohci.yaml b/Documentation/devicetree/bindings/usb/atmel,at91rm9200-ohci.yaml
> new file mode 100644
> index 000000000000..f04de6d553d2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/atmel,at91rm9200-ohci.yaml
> @@ -0,0 +1,85 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/atmel,at91rm9200-ohci.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Atmel AT91RM9200 / AT91SAM9 style OHCI USB Host Controller
> +
> +maintainers:
> + - Nicolas Ferre <nicolas.ferre@microchip.com>
> + - Alexandre Belloni <alexandre.belloni@bootlin.com>
> +
> +description:
> + The Atmel AT91RM9200 / AT91SAM9 OHCI USB Host Controller implements a
> + USB 1.1 Open Host Controller Interface (OHCI) compliant host interface.
> + It provides low-speed and full-speed USB host functionality and is
> + integrated into Atmel AT91RM9200 and AT91SAM9 family SoCs.
> +
> +allOf:
> + - $ref: /schemas/usb/usb.yaml#
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - const: atmel,at91rm9200-ohci
> + - const: usb-ohci
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + minItems: 3
> + maxItems: 3
> +
> + clock-names:
> + items:
> + - const: ohci_clk
> + - const: hclk
> + - const: uhpck
> +
> + num-ports:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: Number of downstream ports supported by this OHCI controller
> + minimum: 1
> + maximum: 15
> +
> + atmel,vbus-gpio:
> + description: GPIO used to control or sense the USB VBUS power.
> + minItems: 1
> + maxItems: 3
> +
> + atmel,oc-gpio:
> + description: GPIO used to signal USB overcurrent condition.
> + minItems: 1
> + maxItems: 3
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/at91.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/gpio/gpio.h>
> + usb@500000 {
> + compatible = "atmel,at91rm9200-ohci", "usb-ohci";
> + reg = <0x500000 0x100000>;
> + interrupts = <20 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&uhphs_clk>, <&uhphs_clk>, <&uhpck>;
> + clock-names = "ohci_clk", "hclk", "uhpck";
> + atmel,vbus-gpio = <&pioA 18 GPIO_ACTIVE_HIGH>;
> + atmel,oc-gpio = <&pioB 10 GPIO_ACTIVE_LOW>;
> + num-ports = <2>;
> + };
> +...
>
--
Best Regards,
Charan.
next prev parent reply other threads:[~2026-02-04 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 11:34 [PATCH 0/4] dt-bindings: usb: atmel: Convert Atmel USB controller bindings to YAML Charan Pedumuru
2026-02-01 11:34 ` [PATCH 1/4] dt-bindings: usb: atmel,at91rm9200-ohci: convert to DT schema Charan Pedumuru
2026-02-04 13:15 ` Charan Pedumuru [this message]
2026-02-01 11:34 ` [PATCH 2/4] dt-bindings: usb: atmel,at91sam9g45-ehci: " Charan Pedumuru
2026-02-01 12:37 ` Rob Herring (Arm)
2026-02-02 11:02 ` Charan Pedumuru
2026-02-03 18:08 ` Rob Herring
2026-02-04 13:09 ` Charan Pedumuru
2026-02-01 11:34 ` [PATCH 3/4] dt-bindings: usb: atmel,at91rm9200-udc: " Charan Pedumuru
2026-02-01 11:34 ` [PATCH 4/4] dt-bindings: usb: atmel,at91sam9rl-udc: " Charan Pedumuru
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=7bb66a07-51c5-4e9a-b484-e96a8f12c783@gmail.com \
--to=charan.pedumuru@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nicolas.ferre@microchip.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