[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DGB1P3K6I14J.1QCMDY84ZR7ZH@linux.dev>
Date: Tue, 10 Feb 2026 13:50:32 +0800
From: "Ze Huang" <huang.ze@...ux.dev>
To: "Chukun Pan" <amadeus@....edu.cn>, <krzk@...nel.org>
Cc: <broonie@...nel.org>, <conor+dt@...nel.org>,
<devicetree@...r.kernel.org>, <dlan@...nel.org>, <huang.ze@...ux.dev>,
<krzk+dt@...nel.org>, <lgirdwood@...il.com>,
<linux-kernel@...r.kernel.org>, <linux-phy@...ts.infradead.org>,
<linux-riscv@...ts.infradead.org>, <neil.armstrong@...aro.org>,
<robh@...nel.org>, <spacemit@...ts.linux.dev>, <vkoul@...nel.org>
Subject: Re: [PATCH 1/2] dt-bindings: phy: spacemit: add regulator support
to K1 USB2 PHY
On Mon Feb 9, 2026 at 2:40 PM CST, Chukun Pan wrote:
> Hi,
>
>> Plus, if this was a vbus regulator it would not be called "phy"...
>> Even more confusing.
>
> Sorry, I didn't consider that this naming is confusing. Other
> platforms, such as Rockchip's inno-usb2phy driver, use the
> "phy-supply" property. I continued with this bad naming.
>
>> Bindings are supposed to be complete regardless what driver does
>> (or does not).
>>
>> You must list all supplies with proper names.
>>
>> If this regulator was missing, then what else?
>
> (...)
>
>> Please start describing in the bindings your complete hardware, not
>> your drivers.
>
> It appears Ze Huang described the vbus-supply property in
> spacemit.k1-dwc3.yaml.
>
> So I should enable the regulator in the dwc3-generic-plat driver.
No, we will enable regulator at port level.
>
> Sorry for the noise.
>
> Thanks,
> Chukun
Powered by blists - more mailing lists