Re: [PATCH 1/2] dt-bindings: phy: Add sa8255p high-speed USB PHY
Krzysztof Kozlowski <[email protected]> Tue, 4 Aug 2026 10:07:48 +0200
| Newsgroups | org.kernel.vger.linux-arm-msm,org.infradead.lists.linux-phy,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <20260804-active-sensible-reindeer-f459a3@quoll> |
On Thu, Jul 30, 2026 at 03:58:14PM +0200, Mattijs Korpershoek wrote: > SA8255p platform abstracts resources such as clocks, interconnect and > GPIO pins configuration in Firmware. SCMI power protocol is used to > request resource configurations. > > Two power domains can be requested: transfer and core. > transfer controls clocks and interconnects and core controls > the GDSC, resets and TLMM (GPIOs). > > Add a new binding for the Qualcomm SA8255p Synopsys Femto High-Speed > USB PHY V2 found in SA8255P. > > Signed-off-by: Mattijs Korpershoek <[email protected]> > --- > .../bindings/phy/qcom,sa8255p-usb-hs-phy.yaml | 52 ++++++++++++++++++++++ > 1 file changed, 52 insertions(+) > > diff --git a/Documentation/devicetree/bindings/phy/qcom,sa8255p-usb-hs-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,sa8255p-usb-hs-phy.yaml > new file mode 100644 > index 000000000000..09f7ca6e7f72 > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/qcom,sa8255p-usb-hs-phy.yaml > @@ -0,0 +1,52 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/phy/qcom,sa8255p-usb-hs-phy.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Qualcomm SA8255p Synopsys Femto High-Speed USB PHY V2 > + > +maintainers: > + - Mattijs Korpershoek <[email protected]> > + > +properties: > + compatible: > + const: qcom,sa8255p-usb-hs-phy > + > + reg: > + maxItems: 1 > + > + "#phy-cells": > + const: 0 > + > + power-domains: > + maxItems: 2 > + > + power-domain-names: > + items: > + - const: transfer > + - const: core Here and in your other binding you call these 'transfer' and 'core' but all other bindings call them 'power' and 'perf'. Why this difference? What are these domains responsible for? Commit msg is pretty useless here - repeats the diff. I can read the diff but I still do not understand why such naming. And why core is not the first one? It clearly feels like the power domain thus the main one. Best regards, Krzysztof