From: Charan Pedumuru <charan.pedumuru@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: phy: ti,control-phy-otghs: convert to DT schema
Date: Tue, 20 Jan 2026 20:45:56 +0530 [thread overview]
Message-ID: <00bb2ec6-8992-4282-bd83-cd5e411aaa0b@gmail.com> (raw)
In-Reply-To: <20260115145137.GB3319937-robh@kernel.org>
On 15-01-2026 20:21, Rob Herring wrote:
> On Wed, Jan 07, 2026 at 04:11:16PM +0000, Charan Pedumuru wrote:
>> Convert TI OMAP Control PHY binding to DT schema.
>> Changes during conversion:
>> - Define a new pattern 'control-phy' to match nodes defined in DT.
>>
>> Signed-off-by: Charan Pedumuru <charan.pedumuru@gmail.com>
>> ---
>> .../bindings/phy/ti,control-phy-otghs.yaml | 94 +++++++++++++++++++++
>> Documentation/devicetree/bindings/phy/ti-phy.txt | 98 ----------------------
>> 2 files changed, 94 insertions(+), 98 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/phy/ti,control-phy-otghs.yaml b/Documentation/devicetree/bindings/phy/ti,control-phy-otghs.yaml
>> new file mode 100644
>> index 000000000000..2c91609cac35
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/ti,control-phy-otghs.yaml
>> @@ -0,0 +1,94 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/phy/ti,control-phy-otghs.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: TI OMAP Control PHY Module
>> +
>> +maintainers:
>> + - Kishon Vijay Abraham I <kishon@ti.com>
>> +
>> +description:
>> + The TI OMAP Control PHY module is a hardware block within the system
>> + control module (SCM) of Texas Instruments OMAP SoCs. It provides
>> + centralized control over power, configuration, and auxiliary features
>> + for multiple on-chip PHYs. This module is essential for proper PHY
>> + operation in power-constrained embedded systems.
>> +
>> +properties:
>> + $nodename:
>> + pattern: "^control-phy(@[0-9a-f]+)?$"
>
> Drop. Non-standard.
Sure, I will change it to phy and will modify in dts too.
>
>> +
>> + compatible:
>> + enum:
>> + - ti,control-phy-otghs
>> + - ti,control-phy-usb2
>> + - ti,control-phy-pipe3
>> + - ti,control-phy-pcie
>> + - ti,control-phy-usb2-dra7
>> + - ti,control-phy-usb2-am437
>
> Alphabetical order
Okay.
>
>> +
>> + reg:
>> + minItems: 1
>> + maxItems: 4
>
> With the constraints below, there is no case that allows 4 entries.
Yeah, I will make it 3.
>
>> +
>> + reg-names:
>> + minItems: 1
>> + maxItems: 4
I will make it 3 here too
>> + items:
>> + enum: [otghs_control, power, pcie_pcs, control_sma]
>> +
>> +allOf:
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - ti,control-phy-otghs
>> + then:
>> + properties:
>> + reg-names:
>> + const: otghs_control
>> +
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - ti,control-phy-pcie
>
> There's no .dts with this compatible. Do you really need this
> compatible or can drop it?
Yeah, currently there is no such compatible, I was following the old binding, I could remove if it's necessary.
>
>> + then:
>> + properties:
>> + reg-names:
>> + items:
>> + - enum: [power, pcie_pcs, control_sma]
>
> It's really 1 entry of 3 possible names?
I think it should be direct 3 entries as per the binding, shouldn't be an enum, I will change it.
>
>> +
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - ti,control-phy-usb2
>> + - ti,control-phy-usb2-dra7
>> + - ti,control-phy-usb2-am437
>> + - ti,control-phy-pipe3
>> + then:
>> + properties:
>> + reg-names:
>> + const: power
>> +
>> +required:
>> + - reg
>> + - compatible
>> + - reg-names
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> + - |
>> + control-phy@4a00233c {
>
> phy@...
>
>> + compatible = "ti,control-phy-otghs";
>> + reg = <0x4a00233c 0x4>;
>> + reg-names = "otghs_control";
>> + };
>> +...
>> diff --git a/Documentation/devicetree/bindings/phy/ti-phy.txt b/Documentation/devicetree/bindings/phy/ti-phy.txt
>> deleted file mode 100644
>> index 7c7936b89f2c..000000000000
>> --- a/Documentation/devicetree/bindings/phy/ti-phy.txt
>> +++ /dev/null
>> @@ -1,98 +0,0 @@
>> -TI PHY: DT DOCUMENTATION FOR PHYs in TI PLATFORMs
>> -
>> -OMAP CONTROL PHY
>> -
>> -Required properties:
>> - - compatible: Should be one of
>> - "ti,control-phy-otghs" - if it has otghs_control mailbox register as on OMAP4.
>> - "ti,control-phy-usb2" - if it has Power down bit in control_dev_conf register
>> - e.g. USB2_PHY on OMAP5.
>> - "ti,control-phy-pipe3" - if it has DPLL and individual Rx & Tx power control
>> - e.g. USB3 PHY and SATA PHY on OMAP5.
>> - "ti,control-phy-pcie" - for pcie to support external clock for pcie and to
>> - set PCS delay value.
>> - e.g. PCIE PHY in DRA7x
>> - "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on
>> - DRA7 platform.
>> - "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on
>> - AM437 platform.
>> - - reg : register ranges as listed in the reg-names property
>> - - reg-names: "otghs_control" for control-phy-otghs
>> - "power", "pcie_pcs" and "control_sma" for control-phy-pcie
>> - "power" for all other types
>> -
>> -omap_control_usb: omap-control-usb@4a002300 {
>> - compatible = "ti,control-phy-otghs";
>> - reg = <0x4a00233c 0x4>;
>> - reg-names = "otghs_control";
>> -};
>> -
>> -TI PIPE3 PHY
>> -
>> -Required properties:
>> - - compatible: Should be "ti,phy-usb3", "ti,phy-pipe3-sata" or
>> - "ti,phy-pipe3-pcie. "ti,omap-usb3" is deprecated.
>> - - reg : Address and length of the register set for the device.
>> - - reg-names: The names of the register addresses corresponding to the registers
>> - filled in "reg".
>> - - #phy-cells: determine the number of cells that should be given in the
>> - phandle while referencing this phy.
>> - - clocks: a list of phandles and clock-specifier pairs, one for each entry in
>> - clock-names.
>> - - clock-names: should include:
>> - * "wkupclk" - wakeup clock.
>> - * "sysclk" - system clock.
>> - * "refclk" - reference clock.
>> - * "dpll_ref" - external dpll ref clk
>> - * "dpll_ref_m2" - external dpll ref clk
>> - * "phy-div" - divider for apll
>> - * "div-clk" - apll clock
>> -
>> -Optional properties:
>> - - id: If there are multiple instance of the same type, in order to
>> - differentiate between each instance "id" can be used (e.g., multi-lane PCIe
>> - PHY). If "id" is not provided, it is set to default value of '1'.
>> - - syscon-pllreset: Handle to system control region that contains the
>> - CTRL_CORE_SMA_SW_0 register and register offset to the CTRL_CORE_SMA_SW_0
>> - register that contains the SATA_PLL_SOFT_RESET bit. Only valid for sata_phy.
>> - - syscon-pcs : phandle/offset pair. Phandle to the system control module and the
>> - register offset to write the PCS delay value.
>> -
>> -Deprecated properties:
>> - - ctrl-module : phandle of the control module used by PHY driver to power on
>> - the PHY.
>> -
>> -Recommended properties:
>> - - syscon-phy-power : phandle/offset pair. Phandle to the system control
>> - module and the register offset to power on/off the PHY.
>> -
>> -This is usually a subnode of ocp2scp to which it is connected.
>> -
>> -usb3phy@4a084400 {
>> - compatible = "ti,phy-usb3";
>> - reg = <0x4a084400 0x80>,
>> - <0x4a084800 0x64>,
>> - <0x4a084c00 0x40>;
>> - reg-names = "phy_rx", "phy_tx", "pll_ctrl";
>> - ctrl-module = <&omap_control_usb>;
>> - #phy-cells = <0>;
>> - clocks = <&usb_phy_cm_clk32k>,
>> - <&sys_clkin>,
>> - <&usb_otg_ss_refclk960m>;
>> - clock-names = "wkupclk",
>> - "sysclk",
>> - "refclk";
>> -};
>> -
>> -sata_phy: phy@4a096000 {
>> - compatible = "ti,phy-pipe3-sata";
>> - reg = <0x4A096000 0x80>, /* phy_rx */
>> - <0x4A096400 0x64>, /* phy_tx */
>> - <0x4A096800 0x40>; /* pll_ctrl */
>> - reg-names = "phy_rx", "phy_tx", "pll_ctrl";
>> - ctrl-module = <&omap_control_sata>;
>> - clocks = <&sys_clkin1>, <&sata_ref_clk>;
>> - clock-names = "sysclk", "refclk";
>> - syscon-pllreset = <&scm_conf 0x3fc>;
>> - #phy-cells = <0>;
>> -};
>>
>> --
>> 2.52.0
>>
--
Best Regards,
Charan.
prev parent reply other threads:[~2026-01-20 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 16:11 [PATCH v2 0/2] dt-bindings: phy: Convert TI OMAP control and PIPE3 PHY to DT schema Charan Pedumuru
2026-01-07 16:11 ` [PATCH v2 1/2] dt-bindings: phy: ti,phy-usb3: convert " Charan Pedumuru
2026-01-14 14:16 ` Vinod Koul
2026-01-14 14:46 ` Charan Pedumuru
2026-01-15 4:41 ` Vinod Koul
2026-01-15 14:45 ` Rob Herring
2026-01-20 14:50 ` Charan Pedumuru
2026-01-07 16:11 ` [PATCH v2 2/2] dt-bindings: phy: ti,control-phy-otghs: " Charan Pedumuru
2026-01-15 14:51 ` Rob Herring
2026-01-20 15:15 ` Charan Pedumuru [this message]
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=00bb2ec6-8992-4282-bd83-cd5e411aaa0b@gmail.com \
--to=charan.pedumuru@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
/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