From: Vinod Koul <vkoul@kernel.org>
To: Swapnil Jakhade <sjakhade@cadence.com>
Cc: kishon@ti.com, robh+dt@kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
mparab@cadence.com, lokeshvutla@ti.com, a-govindraju@ti.com
Subject: Re: [PATCH v2 0/4] PHY: Add support to output derived and received reference clock from Torrent
Date: Wed, 20 Oct 2021 23:27:04 +0530 [thread overview]
Message-ID: <YXBYcOeydTf4xj4H@matsya> (raw)
In-Reply-To: <20210922123735.21927-1-sjakhade@cadence.com>
On 22-09-21, 14:37, Swapnil Jakhade wrote:
> This patch series updates reference clock driver implementation for Torrent
> by adding support to output derived as well as received reference clock.
> When reference clock driver is enabled, either derived or received refclk
> is output on cmn_refclk_p/m.
>
> In derived reference clock mode, cmn_refclk_p/m outputs the refclk derived
> from internal PLLs while when received refclk is selected to output on
> cmn_refclk_p/m, this is the internal reference clock driven on the
> pma_cmn_refclk_int.
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2021-10-20 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 12:37 [PATCH v2 0/4] PHY: Add support to output derived and received reference clock from Torrent Swapnil Jakhade
2021-09-22 12:37 ` [PATCH v2 1/4] phy: cadence-torrent: Migrate to clk_hw based registration and OF APIs Swapnil Jakhade
2021-09-22 12:37 ` [PATCH v2 2/4] dt-bindings: phy: cadence-torrent: Add clock IDs for derived and received refclk Swapnil Jakhade
2021-09-22 12:37 ` [PATCH v2 3/4] phy: cadence-torrent: Model reference clock driver as a clock to enable derived refclk Swapnil Jakhade
2021-09-22 12:37 ` [PATCH v2 4/4] phy: cadence-torrent: Add support to output received reference clock Swapnil Jakhade
2021-10-20 17:57 ` Vinod Koul [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=YXBYcOeydTf4xj4H@matsya \
--to=vkoul@kernel.org \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=mparab@cadence.com \
--cc=robh+dt@kernel.org \
--cc=sjakhade@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;
as well as URLs for NNTP newsgroup(s).