Re: [PATCH v2] arm64: dts: qcom: hamoa-iot-evk: Add vbus regulator support for Type-A ports

[Krishna Kurapati]

On 12/9/2025 8:49 PM, Dmitry Baryshkov wrote:
> On Tue, Dec 09, 2025 at 01:31:10PM +0530, Krishna Kurapati wrote:
> > On 12/9/2025 1:22 PM, Dmitry Baryshkov wrote:
> > > On Tue, Dec 09, 2025 at 09:47:01AM +0530, Krishna Kurapati wrote:
> > > > The Multiport controller on Hamoa EVK platform is connected to Two Type-A
> > > > ports. VBUS for each of these ports are provided by a TPS2559QWDRCTQ1
> > > > regulator, controlled from PMIC GPIOs.
> > > >
> > > > Add the necessary regulators and GPIO configuration to power these.
> > >
> > > Should this also include corresponding USB-A connector devices? See
> > > qcs6490-radxa-dragon-q6a.dts for the example of how to describe them.
> >
> > Hi Dmitry,
> >
> >   I see same discussion that came up when we were trying to upstream TypeA
> > connectors of SA8295:
> > 	
> > https://lore.kernel.org/all/CAA8EJppf+j6H8vPOrer1Oj6SuM=qHKXoBahtCaCr7an-cbpyOQ@xxxxxxxxxxxxxx/
> >
> > There is no entity (either phy or dwc3) as of today that can read the vbus
> > from connector-A node and use it. So keeping these regulators always on for
> > now.
>
> There are two distinct questions:
> - one is how you describe the board and onboard devices / connectors
> - another one is how to make sure VBus is enabled.
>
> I'd suggest having full description (with connectors, graph links
> between USB host and connector and vbus-supply properties) and then
> having the comment before regulator-always-on describing why it's on.

Thanks for the review Dmitry. So, IIUC, the suggestion is to add the 
connector nodes for Type-A ports, add the vbus in the connector and mark 
the vbus regulator nodes as always ON.

W.r.t the graph nodes, we can't link the connector to any available node 
today. Can we leave the remote endpoints empty and unlinked to anything.

Regards,
Krishna,