From: Rob Herring <robh@kernel.org>
To: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, vkoul@kernel.org,
neil.armstrong@linaro.org, krzk+dt@kernel.org,
conor+dt@kernel.org, johan@kernel.org, rogerq@ti.com,
Julian.FRIEDRICH@frequentis.com, upstream+omap@sigma-star.at
Subject: Re: [PATCH v2 1/2] dt-bindings: phy: ti,phy-usb3: Add aspcie reference clock setting
Date: Tue, 11 Aug 2026 21:20:31 -0500 [thread overview]
Message-ID: <20260812022031.GA554483-robh@kernel.org> (raw)
In-Reply-To: <20260806091112.164695-2-david.oberhollenzer@sigma-star.at>
On Thu, Aug 06, 2026 at 11:11:11AM +0200, David Oberhollenzer wrote:
> The PHY control logic in the OMAP PCIe PHY subsystem has a
> configurable reference clock selection. It can either use
> the ljcb_clkp/ljcb_clkn pin as inputs, recovering the clock
> from the bus (RX mode), or generate the reference clock
> internally, driving the bus pins as outputs (TX mode).
>
> The setting is exposed through a register in a system controller.
> A device tree property is added to specify the syscon node,
> register offset and mode value.
>
> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
> ---
> .../devicetree/bindings/phy/ti,phy-usb3.yaml | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/ti,phy-usb3.yaml b/Documentation/devicetree/bindings/phy/ti,phy-usb3.yaml
> index 84f538aa587c..11787b042345 100644
> --- a/Documentation/devicetree/bindings/phy/ti,phy-usb3.yaml
> +++ b/Documentation/devicetree/bindings/phy/ti,phy-usb3.yaml
> @@ -52,6 +52,20 @@ properties:
> enum: [wkupclk, sysclk, refclk, dpll_ref,
> dpll_ref_m2, phy-div, div-clk]
>
> + ti,syscon-acspcie-tx-rx:
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + description: |
Don't need '|' unless there is formatting to preserve.
> + Syscon register and setting to configure the clock buffer to run
> + in RX mode (clock pins are inputs, the clock is recovered from
> + the bus), or in TX mode (pins are outputs, internal reference
> + clock drives the bus).
Wrap lines at 80 chars.
> + maxItems: 1
> + items:
> + items:
> + - description: Phandle to the system control module
> + - description: Register offset of CTRL_CORE_SMA_SW_6
> + - description: Setting for PCIE_TX_RX_CONTROL
> +
> syscon-phy-power:
> $ref: /schemas/types.yaml#/definitions/phandle-array
> maxItems: 1
> @@ -94,6 +107,17 @@ allOf:
> else:
> properties:
> syscon-pllreset: false
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: ti,phy-pipe3-pcie
> + then:
> + properties:
> + ti,syscon-acspcie-tx-rx: true
This has no effect. Invert the if and move the else here.
> + else:
> + properties:
> + ti,syscon-acspcie-tx-rx: false
>
> required:
> - reg
> @@ -135,4 +159,19 @@ examples:
> syscon-pllreset = <&scm_conf 0x3fc>;
> #phy-cells = <0>;
> };
> +
> + - |
> + /* TI PIPE3 PCIE PHY */
> + pcie-phy@4a0a4000 {
> + compatible = "ti,phy-pipe3-pcie";
> + reg = <0x4a0a4000 0x80>, /* phy_rx */
> + <0x4a0a4400 0x64>; /* phy_tx */
> + reg-names = "phy_rx", "phy_tx";
> + clocks = <&dpll_pcie_ref_ck>, <&dpll_pcie_ref_m2ldo_ck>;
> + clock-names = "dpll_ref", "dpll_ref_m2";
> + #phy-cells = <0>;
> + syscon-phy-power = <&scm_conf_pcie 0x1c>;
> + syscon-pcs = <&scm_conf_pcie 0x10>;
> + ti,syscon-acspcie-tx-rx = <&scm_conf1 0x10 0x2>;
> + };
> ...
> --
> 2.55.0
>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-08-12 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 9:11 [PATCH v2 0/2] phy: ti: ti-pipe3: allow configuring ACSPCIe TX/RX mode David Oberhollenzer
2026-08-06 9:11 ` [PATCH v2 1/2] dt-bindings: phy: ti,phy-usb3: Add aspcie reference clock setting David Oberhollenzer
2026-08-12 2:20 ` Rob Herring [this message]
2026-08-06 9:11 ` [PATCH v2 2/2] phy: ti: ti-pipe3: allow configuring ACSPCIe TX/RX mode David Oberhollenzer
2026-08-06 9:24 ` sashiko-bot
2026-08-10 7:48 ` David Oberhollenzer
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=20260812022031.GA554483-robh@kernel.org \
--to=robh@kernel.org \
--cc=Julian.FRIEDRICH@frequentis.com \
--cc=conor+dt@kernel.org \
--cc=david.oberhollenzer@sigma-star.at \
--cc=devicetree@vger.kernel.org \
--cc=johan@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=rogerq@ti.com \
--cc=upstream+omap@sigma-star.at \
--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