Devicetree
 help / color / mirror / Atom feed
From: Gokul Praveen <g-praveen@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "conor+dt@kernel.org" <conor+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
	"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"sjakhade@cadence.com" <sjakhade@cadence.com>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"yamonkar@cadence.com" <yamonkar@cadence.com>,
	"Vadapalli, Siddharth" <s-vadapalli@ti.com>
Subject: Re: [PATCH v6] dt-bindings: phy: cadence-torrent: Update clocks for multilink SERDES
Date: Mon, 27 Jul 2026 15:05:38 +0530	[thread overview]
Message-ID: <eac428f3-fbab-437b-a881-e0d333de8360@ti.com> (raw)
In-Reply-To: <0b8a91f0-8a2e-4dfa-aecf-acb865442d53@ti.com>

Hi  Krzystof,

Hope this clarifies your query.

Best Regards

Gokul Praveen

On 23/07/26 15:45, Gokul Praveen wrote:
> Hi Krzystzof,
>
> On 23/07/26 12:45, Krzysztof Kozlowski wrote:
>> On Wed, Jul 22, 2026 at 11:48:31AM +0530, Gokul Praveen wrote:
>>> For multilink SERDES configurations where each link requires a
>>> different clock frequency, the SERDES provisions an additional
>>> reference clock for PLL1. Hence, document it.
>> The pll1 is already there.
> Yes, but the existing configuration has a limitation as
>
> it does not allow both pll1 and phy_en_refclk to be used at the same time.
>
>> Also, the TI variant does it or cdns one or both?
> Both of them.
>
> Best Regards
>
> Gokul Praveen
>
>> Best regards,
>> Krzysztof
>>

      reply	other threads:[~2026-07-27  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  6:18 [PATCH v6] dt-bindings: phy: cadence-torrent: Update clocks for multilink SERDES Gokul Praveen
2026-07-23  7:15 ` Krzysztof Kozlowski
2026-07-23 10:15   ` Gokul Praveen
2026-07-27  9:35     ` Gokul Praveen [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=eac428f3-fbab-437b-a881-e0d333de8360@ti.com \
    --to=g-praveen@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=sjakhade@cadence.com \
    --cc=vkoul@kernel.org \
    --cc=yamonkar@cadence.com \
    /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