From: Sean Anderson <sean.anderson@linux.dev>
To: "Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>
Cc: Vinod Koul <vkoul@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Simek, Michal" <michal.simek@amd.com>,
Kishon Vijay Abraham I <kishon@kernel.org>
Subject: Re: [PATCH v2 1/4] phy: zynqmp: Enable reference clock correctly
Date: Fri, 14 Jun 2024 11:17:39 -0400 [thread overview]
Message-ID: <f8a5307a-ab9a-4b9a-9cf5-1b88f912b201@linux.dev> (raw)
In-Reply-To: <MN0PR12MB59531E522EC62B160EEC35E5B7C22@MN0PR12MB5953.namprd12.prod.outlook.com>
On 6/14/24 01:30, Pandey, Radhey Shyam wrote:
>> -----Original Message-----
>> From: Sean Anderson <sean.anderson@linux.dev>
>> Sent: Monday, May 6, 2024 10:31 PM
>> To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>; linux-
>> phy@lists.infradead.org
>> Cc: Vinod Koul <vkoul@kernel.org>; linux-arm-kernel@lists.infradead.org;
>> linux-kernel@vger.kernel.org; Michal Simek <michal.simek@amd.com>;
>> Kishon Vijay Abraham I <kishon@kernel.org>; Sean Anderson
>> <sean.anderson@linux.dev>
>> Subject: [PATCH v2 1/4] phy: zynqmp: Enable reference clock correctly
>>
>> Lanes can use other lanes' reference clocks, as determined by refclk.
>> Use refclk to determine the clock to enable/disable instead of always
>> using the lane's own reference clock. This ensures the clock selected in
>> xpsgtr_configure_pll is the one enabled.
>>
>> For the other half of the equation, always program REF_CLK_SEL even when
>> we are selecting the lane's own clock. This ensures that Linux's idea of
>> the reference clock matches the hardware. We use the "local" clock mux
>> for this instead of going through the ref clock network.
>>
>> Fixes: 25d700833513 ("phy: xilinx: phy-zynqmp: dynamic clock support for
>> power-save")
>> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
>> ---
>>
>> Changes in v2:
>> - New
>>
>> drivers/phy/xilinx/phy-zynqmp.c | 14 +++++++++-----
>> 1 file changed, 9 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/phy/xilinx/phy-zynqmp.c b/drivers/phy/xilinx/phy-
>> zynqmp.c
>> index f72c5257d712..5a434382356c 100644
>> --- a/drivers/phy/xilinx/phy-zynqmp.c
>> +++ b/drivers/phy/xilinx/phy-zynqmp.c
>> @@ -80,7 +80,8 @@
>>
>> /* Reference clock selection parameters */
>> #define L0_Ln_REF_CLK_SEL(n) (0x2860 + (n) * 4)
>> -#define L0_REF_CLK_SEL_MASK 0x8f
>> +#define L0_REF_CLK_LCL_SEL BIT(7)
>> +#define L0_REF_CLK_SEL_MASK 0x9f
>>
>> /* Calibration digital logic parameters */
>> #define L3_TM_CALIB_DIG19 0xec4c
>> @@ -349,11 +350,14 @@ static void xpsgtr_configure_pll(struct xpsgtr_phy
>> *gtr_phy)
>> PLL_FREQ_MASK, ssc->pll_ref_clk);
>>
>> /* Enable lane clock sharing, if required */
>> - if (gtr_phy->refclk != gtr_phy->lane) {
>> + if (gtr_phy->refclk == gtr_phy->lane)
>> + /* Lane3 Ref Clock Selection Register */
>
> This is common ref clock selection and not lane 3?
This is copied from the existing comment. I will remove it.
--Sean
>> + xpsgtr_clr_set(gtr_phy->dev, L0_Ln_REF_CLK_SEL(gtr_phy-
>> >lane),
>> + L0_REF_CLK_SEL_MASK, L0_REF_CLK_LCL_SEL);
>> + else
>> /* Lane3 Ref Clock Selection Register */
>> xpsgtr_clr_set(gtr_phy->dev, L0_Ln_REF_CLK_SEL(gtr_phy-
>> >lane),
>> L0_REF_CLK_SEL_MASK, 1 << gtr_phy->refclk);
>> - }
>>
>> /* SSC step size [7:0] */
>> xpsgtr_clr_set_phy(gtr_phy, L0_PLL_SS_STEP_SIZE_0_LSB,
>> @@ -573,7 +577,7 @@ static int xpsgtr_phy_init(struct phy *phy)
>> mutex_lock(>r_dev->gtr_mutex);
>>
>> /* Configure and enable the clock when peripheral phy_init call */
>> - if (clk_prepare_enable(gtr_dev->clk[gtr_phy->lane]))
>> + if (clk_prepare_enable(gtr_dev->clk[gtr_phy->refclk]))
>> goto out;
>>
>> /* Skip initialization if not required. */
>> @@ -625,7 +629,7 @@ static int xpsgtr_phy_exit(struct phy *phy)
>> gtr_phy->skip_phy_init = false;
>>
>> /* Ensure that disable clock only, which configure for lane */
>> - clk_disable_unprepare(gtr_dev->clk[gtr_phy->lane]);
>> + clk_disable_unprepare(gtr_dev->clk[gtr_phy->refclk]);
>>
>> return 0;
>> }
>> --
>> 2.35.1.1320.gc452695387.dirty
>
next prev parent reply other threads:[~2024-06-14 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 17:01 [PATCH v2 0/4] phy: zynqmp: Fixes and debugfs support Sean Anderson
2024-05-06 17:01 ` [PATCH v2 1/4] phy: zynqmp: Enable reference clock correctly Sean Anderson
2024-06-14 5:30 ` Pandey, Radhey Shyam
2024-06-14 15:17 ` Sean Anderson [this message]
2024-05-06 17:01 ` [PATCH v2 2/4] phy: zynqmp: Store instance instead of type Sean Anderson
2024-06-14 6:02 ` Pandey, Radhey Shyam
2024-06-14 15:16 ` Sean Anderson
2024-05-06 17:01 ` [PATCH v2 3/4] phy: zynqmp: Only wait for PLL lock "primary" instances Sean Anderson
2024-05-06 17:01 ` [PATCH v2 4/4] phy: zynqmp: Add debugfs support Sean Anderson
2024-06-13 9:20 ` Pandey, Radhey Shyam
2024-06-13 15:02 ` Sean Anderson
2024-06-14 5:16 ` Pandey, Radhey Shyam
2024-06-14 15:26 ` Sean Anderson
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=f8a5307a-ab9a-4b9a-9cf5-1b88f912b201@linux.dev \
--to=sean.anderson@linux.dev \
--cc=kishon@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=michal.simek@amd.com \
--cc=radhey.shyam.pandey@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).