From: Krzysztof Kozlowski <krzk@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>
Cc: Peter Griffin <peter.griffin@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Will McVicker <willmcvicker@google.com>,
kernel-team@android.com, linux-samsung-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: samsung: clk-pll: simplify samsung_pll_lock_wait()
Date: Mon, 13 Oct 2025 03:23:23 +0200 [thread overview]
Message-ID: <fc343072-423f-41db-b7ee-1f1496183363@kernel.org> (raw)
In-Reply-To: <20251001-samsung-clk-pll-simplification-v1-1-d12def9e74b2@linaro.org>
On 01/10/2025 17:13, André Draszik wrote:
> /*
> @@ -93,25 +92,15 @@ static int samsung_pll_lock_wait(struct samsung_clk_pll *pll,
> * initialized, another when the timekeeping is suspended. udelay() also
> * cannot be used when the clocksource is not running on arm64, since
> * the current timer is used as cycle counter. So a simple busy loop
> - * is used here in that special cases. The limit of iterations has been
> - * derived from experimental measurements of various PLLs on multiple
> - * Exynos SoC variants. Single register read time was usually in range
> - * 0.4...1.5 us, never less than 0.4 us.
> + * is used here.
> + * The limit of iterations has been derived from experimental
> + * measurements of various PLLs on multiple Exynos SoC variants. Single
> + * register read time was usually in range 0.4...1.5 us, never less than
> + * 0.4 us.
> */
> - if (pll_early_timeout || timekeeping_suspended) {
Please drop now pll_early_timeout, it is not used anymore.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-13 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 15:13 André Draszik
2025-10-03 18:48 ` Sam Protsenko
2025-10-13 1:23 ` Krzysztof Kozlowski [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=fc343072-423f-41db-b7ee-1f1496183363@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=kernel-team@android.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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®