From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: "open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
linux-clk@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: meson: pll: adjust timeout in meson_clk_pll_wait_lock()
Date: Mon, 29 Aug 2022 20:50:34 +0200 [thread overview]
Message-ID: <f670d8e7-30a9-387a-156a-9ebeee9f638d@gmail.com> (raw)
In-Reply-To: <1jo7w3tlyo.fsf@starbuckisacylon.baylibre.com>
On 29.08.2022 11:52, Jerome Brunet wrote:
>
> On Sun 14 Aug 2022 at 23:29, Heiner Kallweit <hkallweit1@gmail.com> wrote:
>
>> Currently we loop over meson_parm_read() up to 24mln times.
>> This results in a unpredictable timeout period. In my case
>> it's over 5s on a S905X4-based system. Make the timeout
>> period predictable and set it to 100ms.
>>
>> Whilst we're at it: All callers of this function return -EIO
>> in case of failure, therefore we can return this value directly
>> in the timeout case.
>
> I'm okay with this change but I'd prefer if one change addressed a
> single topic. Please split this out.
>
OK, I'll send a v2.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> drivers/clk/meson/clk-pll.c | 15 ++++++---------
>> 1 file changed, 6 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/clk/meson/clk-pll.c b/drivers/clk/meson/clk-pll.c
>> index daa025b6d..d70bee331 100644
>> --- a/drivers/clk/meson/clk-pll.c
>> +++ b/drivers/clk/meson/clk-pll.c
>> @@ -277,17 +277,17 @@ static int meson_clk_pll_wait_lock(struct clk_hw *hw)
>> {
>> struct clk_regmap *clk = to_clk_regmap(hw);
>> struct meson_clk_pll_data *pll = meson_clk_pll_data(clk);
>> - int delay = 24000000;
>> + int delay = 5000;
>>
>> do {
>> - /* Is the clock locked now ? */
>> + /* Is the clock locked now ? Time out after 100ms. */
>> if (meson_parm_read(clk->map, &pll->l))
>> return 0;
>>
>> - delay--;
>> - } while (delay > 0);
>> + udelay(20);
>> + } while (--delay);
>>
>> - return -ETIMEDOUT;
>> + return -EIO;
>> }
>>
>> static int meson_clk_pll_init(struct clk_hw *hw)
>> @@ -350,10 +350,7 @@ static int meson_clk_pll_enable(struct clk_hw *hw)
>> /* Take the pll out reset */
>> meson_parm_write(clk->map, &pll->rst, 0);
>>
>> - if (meson_clk_pll_wait_lock(hw))
>> - return -EIO;
>> -
>> - return 0;
>> + return meson_clk_pll_wait_lock(hw);
>> }
>>
>> static void meson_clk_pll_disable(struct clk_hw *hw)
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2022-08-29 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 21:29 [PATCH] clk: meson: pll: adjust timeout in meson_clk_pll_wait_lock() Heiner Kallweit
2022-08-29 9:52 ` Jerome Brunet
2022-08-29 18:50 ` Heiner Kallweit [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=f670d8e7-30a9-387a-156a-9ebeee9f638d@gmail.com \
--to=hkallweit1@gmail.com \
--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=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--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;
as well as URLs for NNTP newsgroup(s).