[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240814134103.esnt6niyu36adtgp@pengutronix.de>
Date: Wed, 14 Aug 2024 15:41:03 +0200
From: Marco Felsch <m.felsch@...gutronix.de>
To: Rob Herring <robh@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Matthias Kaehlcke <mka@...omium.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Fabio Estevam <festevam@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, kernel@...gutronix.de,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: usb: microchip,usb2514: add support for
port vbus-supply
Hi Rob,
On 24-08-13, Rob Herring wrote:
> On Wed, Aug 07, 2024 at 04:36:52PM +0200, Marco Felsch wrote:
> > Some PCB designs don't connect the USB hub port power control GPIO and
> > instead make use of an host controllable regulator. Add support for this
> > use-case by introducing an portX-vbus-supply property.
> >
> > Signed-off-by: Marco Felsch <m.felsch@...gutronix.de>
> > ---
> > Documentation/devicetree/bindings/usb/microchip,usb2514.yaml | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/usb/microchip,usb2514.yaml b/Documentation/devicetree/bindings/usb/microchip,usb2514.yaml
> > index 783c27591e56..51d02c4b8f2d 100644
> > --- a/Documentation/devicetree/bindings/usb/microchip,usb2514.yaml
> > +++ b/Documentation/devicetree/bindings/usb/microchip,usb2514.yaml
> > @@ -35,6 +35,13 @@ required:
> > - compatible
> > - reg
> >
> > +patternProperties:
> > + "^port[1-7]-vbus-supply$"
> > + type: object
> > + description:
> > + Regulator controlling the USB VBUS on portX. Only required if the host
> > + controls the portX VBUS.
>
> This is completely external to the Microchip part, right?
>
> I think each port node should have a 'vbus-supply' property instead.
This was my first approach but the problem is that we currently don't
support such use-case:
parent-node {
/* Parent controlling the supply of the child node */
child-node {
vbus-supply = <®>;
};
};
at least I didn't found such use-case. I'm happy for pointers if you
know more :) At the moment *-supply properties and device-nodes are
bound together:
parent-node {
vbus-supply = <®>;
};
Regards,
Marco
>
> Rob
>
Powered by blists - more mailing lists