From: Chuan Liu <chuan.liu@amlogic.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
Chuan Liu via B4 Relay <devnull+chuan.liu.amlogic.com@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, da@libre.computer
Subject: Re: [PATCH v2 4/5] clk: amlogic: Optimize PLL enable timing
Date: Thu, 30 Oct 2025 17:23:29 +0800 [thread overview]
Message-ID: <1c1b699a-6ebe-4c6c-b818-44da8e1bd79c@amlogic.com> (raw)
In-Reply-To: <1ja518zsvu.fsf@starbuckisacylon.baylibre.com>
Hi Jerome,
On 10/30/2025 4:38 PM, Jerome Brunet wrote:
> [ EXTERNAL EMAIL ]
>
> On Thu 30 Oct 2025 at 13:24, Chuan Liu via B4 Relay <devnull+chuan.liu.amlogic.com@kernel.org> wrote:
>
>> From: Chuan Liu <chuan.liu@amlogic.com>
>>
>> l_detect controls the enablement of the PLL lock detection module.
>> It should remain disabled while the internal PLL circuits are
>> reaching a steady state; otherwise, the lock signal may be falsely
>> triggered high.
>>
>> Before enabling the internal power supply of the PLL, l_detect should
>> be disabled. After the PLL’s internal circuits have stabilized,
>> l_detect should be enabled to prevent false lock signal triggers.
>
> You to reformat this description. It feel that both paragraph are saying
> the same thing.
>
Ok, drop it.
>>
>> Currently, only A1 supports both l_detect and current_en, so this
>> patch will only affect A1.
>>
>> Signed-off-by: Chuan Liu <chuan.liu@amlogic.com>
>> ---
>> drivers/clk/meson/clk-pll.c | 28 +++++++++++++++-------------
>> 1 file changed, 15 insertions(+), 13 deletions(-)
>>
>> diff --git a/drivers/clk/meson/clk-pll.c b/drivers/clk/meson/clk-pll.c
>> index 6c794adb8ccd..c6eebde1f516 100644
>> --- a/drivers/clk/meson/clk-pll.c
>> +++ b/drivers/clk/meson/clk-pll.c
>> @@ -383,36 +383,38 @@ static int meson_clk_pll_enable(struct clk_hw *hw)
>> if (MESON_PARM_APPLICABLE(&pll->rst))
>> meson_parm_write(clk->map, &pll->rst, 1);
>>
>> + /* Disable the PLL lock-detect module */
>> + if (MESON_PARM_APPLICABLE(&pll->l_detect))
>> + meson_parm_write(clk->map, &pll->l_detect, 1);
>> +
>> /* Enable the pll */
>> meson_parm_write(clk->map, &pll->en, 1);
>> /* Wait for Bandgap and LDO to power up and stabilize */
>> udelay(20);
>>
>> - /* Take the pll out reset */
>> - if (MESON_PARM_APPLICABLE(&pll->rst))
>> - meson_parm_write(clk->map, &pll->rst, 0);
>
> Why is the reset moving around ? nothing is said in the description about
> that
>
The function of current_en in the PLL is similar to en. It's more
reliable to assert the reset signal after current_en is set high.
I'll update the commit description accordingly in the next version.
>> -
>> - /* Wait for PLL loop stabilization */
>> - udelay(20);
>> -
>> /*
>> * Compared with the previous SoCs, self-adaption current module
>> * is newly added for A1, keep the new power-on sequence to enable the
>> * PLL. The sequence is:
>> - * 1. enable the pll, delay for 10us
>> + * 1. enable the pll, delay for 20us
>> * 2. enable the pll self-adaption current module, delay for 40us
>> * 3. enable the lock detect module
>> */
>> if (MESON_PARM_APPLICABLE(&pll->current_en)) {
>> - udelay(10);
>> meson_parm_write(clk->map, &pll->current_en, 1);
>> - udelay(40);
>> + udelay(20);
>> }
>>
>> - if (MESON_PARM_APPLICABLE(&pll->l_detect)) {
>> - meson_parm_write(clk->map, &pll->l_detect, 1);
>> + /* Take the pll out reset */
>> + if (MESON_PARM_APPLICABLE(&pll->rst))
>> + meson_parm_write(clk->map, &pll->rst, 0);
>> +
>> + /* Wait for PLL loop stabilization */
>> + udelay(20);
>> +
>> + /* Enable the lock-detect module */
>> + if (MESON_PARM_APPLICABLE(&pll->l_detect))
>> meson_parm_write(clk->map, &pll->l_detect, 0);
>> - }
>>
>> if (meson_clk_pll_wait_lock(hw)) {
>> /* disable PLL when PLL lock failed. */
>
> --
> Jerome
next prev parent reply other threads:[~2025-10-30 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 5:24 [PATCH v2 0/5] clk: amlogic: optimize the PLL driver Chuan Liu via B4 Relay
2025-10-30 5:24 ` [PATCH v2 1/5] clk: amlogic: Fix out-of-range PLL frequency setting Chuan Liu via B4 Relay
2025-10-30 5:24 ` [PATCH v2 2/5] clk: amlogic: Improve the issue of PLL lock failures Chuan Liu via B4 Relay
2025-10-30 8:41 ` Jerome Brunet
2025-10-30 9:09 ` Chuan Liu
2025-10-30 5:24 ` [PATCH v2 3/5] clk: amlogic: Add handling for PLL lock failure Chuan Liu via B4 Relay
2025-10-30 8:32 ` Jerome Brunet
2025-10-30 9:15 ` Chuan Liu
2025-10-30 11:48 ` Chuan Liu
2025-10-30 5:24 ` [PATCH v2 4/5] clk: amlogic: Optimize PLL enable timing Chuan Liu via B4 Relay
2025-10-30 8:38 ` Jerome Brunet
2025-10-30 9:23 ` Chuan Liu [this message]
2025-10-30 5:24 ` [PATCH v2 5/5] clk: amlogic: Change the active level of l_detect Chuan Liu via B4 Relay
2025-10-30 8:40 ` Jerome Brunet
2025-10-30 9:27 ` Chuan Liu
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=1c1b699a-6ebe-4c6c-b818-44da8e1bd79c@amlogic.com \
--to=chuan.liu@amlogic.com \
--cc=da@libre.computer \
--cc=devnull+chuan.liu.amlogic.com@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=sboyd@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
all inboxes | Powered by JetHome®