From: Ryan Chen <ryan_chen@aspeedtech.com>
To: Conor Dooley <conor@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Philipp Zabel <p.zabel@pengutronix.de>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/4] dt-bindings: usb: uhci: Add reset property
Date: Tue, 16 Sep 2025 01:04:25 +0000 [thread overview]
Message-ID: <OS8PR06MB75419B97CDB5EA24560FB9ECF214A@OS8PR06MB7541.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20250915-fifteen-sappy-82f26231843a@spud>
> Subject: Re: [PATCH 1/4] dt-bindings: usb: uhci: Add reset property
>
> On Mon, Sep 15, 2025 at 03:39:23PM +0800, Ryan Chen wrote:
> > The UHCI controller on Aspeed SoCs (including AST2700) requires its
> > reset line to be deasserted before the controller can be used.
> > Add an optional "resets" property to the UHCI device tree bindings to
> > describe the phandle to the reset controller.
>
> Looks like the property is not optional at all for your aspeed devices, and you
> should require it for those compatibles.
>
> >
> > This property is optional for platforms which do not require explicit
> > reset handling.
Thanks, resets is required for ast2700-uhci.
I will add in following.
- if:
properties:
compatible:
contains:
const: aspeed,ast2700-uhci
then:
required:
- resets
> >
> > Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> > ---
> > Documentation/devicetree/bindings/usb/usb-uhci.yaml | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/usb/usb-uhci.yaml
> > b/Documentation/devicetree/bindings/usb/usb-uhci.yaml
> > index d8336f72dc1f..b1f2b9bd7921 100644
> > --- a/Documentation/devicetree/bindings/usb/usb-uhci.yaml
> > +++ b/Documentation/devicetree/bindings/usb/usb-uhci.yaml
> > @@ -28,6 +28,9 @@ properties:
> > interrupts:
> > maxItems: 1
> >
> > + resets:
> > + maxItems: 1
> > +
> > '#ports':
> > $ref: /schemas/types.yaml#/definitions/uint32
> >
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2025-09-16 1:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 7:39 [PATCH 0/4] Add Aspeed AST2700 uhci support Ryan Chen
2025-09-15 7:39 ` [PATCH 1/4] dt-bindings: usb: uhci: Add reset property Ryan Chen
2025-09-15 17:36 ` Conor Dooley
2025-09-16 1:04 ` Ryan Chen [this message]
2025-09-15 7:39 ` [PATCH 2/4] usb: uhci: Add reset control support Ryan Chen
2025-09-15 14:08 ` Alan Stern
2025-09-16 0:48 ` Ryan Chen
2025-09-15 7:39 ` [PATCH 3/4] dt-bindings: usb: uhci: Add Aspeed AST2700 compatible Ryan Chen
2025-09-15 17:35 ` Conor Dooley
2025-09-16 2:04 ` Ryan Chen
2025-09-15 7:39 ` [PATCH 4/4] usb: uhci: Add Aspeed AST2700 support Ryan Chen
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=OS8PR06MB75419B97CDB5EA24560FB9ECF214A@OS8PR06MB7541.apcprd06.prod.outlook.com \
--to=ryan_chen@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=stern@rowland.harvard.edu \
/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