mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Linkai Gong <gonglinkai@kylinos.cn>,
	Stephen Boyd <sboyd@kernel.org>,
	Brian Masney <bmasney+clk@redhat.com>,
	Jerome Brunet <jbrunet+clk@baylibre.com>
Cc: Mike Turquette <mturquette@linaro.org>,
	Soren Brinkmann <soren.brinkmann@xilinx.com>,
	Kees Cook <kees@kernel.org>,
	Babanpreet Singh <bbnpreetsingh@gmail.com>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] clk: zynq: return -ETIMEDOUT if the PLL never locks
Date: Tue, 10 Nov 2026 14:21:41 +0100	[thread overview]
Message-ID: <7abc747f-a9c7-41cd-9dc5-710caf739cf0@amd.com> (raw)
In-Reply-To: <20260908084727.1552042-1-gonglinkai@kylinos.cn>



On 9/8/26 10:47, Linkai Gong wrote:
> zynq_pll_enable() waits for lock under a spinlock with no timeout.
> A stuck PLL would wedge the enable path with IRQs off.
> 
> Poll with readl_poll_timeout_atomic() and return -ETIMEDOUT on
> failure. The 1 ms upper bound is a software limit for a stuck PLL,
> not a TRM-derived value; Zynq PLL lock is still expected well
> within that window.
> 
> Changes in v2:
> - Use BIT(clk->lockbit)
> - Name the poll delay/timeout constants
> - Clarify the 1 ms bound in the commit message
> 
> Fixes: 3682af46d55f ("clk: zynq: Factor out PLL driver")
> Signed-off-by: Linkai Gong <gonglinkai@kylinos.cn>
> ---
>   drivers/clk/zynq/pll.c | 15 ++++++++++++---
>   1 file changed, 12 insertions(+), 3 deletions(-)
Tested-by: Michal Simek <michal.simek@amd.com>

Thanks,
Michal

      reply	other threads:[~2026-11-10 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 12:53 [PATCH] " Linkai Gong
2026-09-07 12:58 ` Michal Simek
2026-09-08  8:44   ` Linkai Gong
2026-09-08  8:47 ` [PATCH v2] " Linkai Gong
2026-11-10 13:21   ` Michal Simek [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=7abc747f-a9c7-41cd-9dc5-710caf739cf0@amd.com \
    --to=michal.simek@amd.com \
    --cc=bbnpreetsingh@gmail.com \
    --cc=bmasney+clk@redhat.com \
    --cc=gonglinkai@kylinos.cn \
    --cc=jbrunet+clk@baylibre.com \
    --cc=kees@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=sboyd@kernel.org \
    --cc=soren.brinkmann@xilinx.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

all inboxes | Powered by JetHome®