From: Abel Vesa <abel.vesa@nxp.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Adrian Alonso <adrian.alonso@nxp.com>,
Mads Bligaard Nielsen <bli@bang-olufsen.dk>
Subject: Re: [PATCH v2 6/8] clk: imx: pll14xx: explicitly return lowest rate
Date: Fri, 25 Feb 2022 15:26:45 +0200 [thread overview]
Message-ID: <YhjZFRLeGdsI41qQ@abelvesa> (raw)
In-Reply-To: <20220225082937.2746176-7-s.hauer@pengutronix.de>
On 22-02-25 09:29:35, Sascha Hauer wrote:
> clk_pll14xx_round_rate() returns the lowest rate by indexing into
> the rate table with the variable i. i is actually pll->rate_count
> as this is the value we come out of the loop with. Use pll->rate_count
> explicitly to make it a bit more clear what is being done. While at
> it fix a typo in the comment. No functional change.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Reviewed-by: Abel Vesa <abel.vesa@nxp.com>
> ---
> drivers/clk/imx/clk-pll14xx.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/imx/clk-pll14xx.c b/drivers/clk/imx/clk-pll14xx.c
> index b464e1155e25b..af4c979e70a64 100644
> --- a/drivers/clk/imx/clk-pll14xx.c
> +++ b/drivers/clk/imx/clk-pll14xx.c
> @@ -118,13 +118,13 @@ static long clk_pll14xx_round_rate(struct clk_hw *hw, unsigned long rate,
> const struct imx_pll14xx_rate_table *rate_table = pll->rate_table;
> int i;
>
> - /* Assumming rate_table is in descending order */
> + /* Assuming rate_table is in descending order */
> for (i = 0; i < pll->rate_count; i++)
> if (rate >= rate_table[i].rate)
> return rate_table[i].rate;
>
> /* return minimum supported value */
> - return rate_table[i - 1].rate;
> + return rate_table[pll->rate_count - 1].rate;
> }
>
> static unsigned long clk_pll14xx_recalc_rate(struct clk_hw *hw,
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-02-25 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 8:29 [PATCH v2 0/8] clk: i.MX: PLL14xx: Support dynamic rates Sascha Hauer
2022-02-25 8:29 ` [PATCH v2 1/8] clk: imx: pll14xx: Use register defines consistently Sascha Hauer
2022-02-25 8:29 ` [PATCH v2 2/8] clk: imx: pll14xx: Drop wrong shifting Sascha Hauer
2022-02-25 8:29 ` [PATCH v2 3/8] clk: imx: pll14xx: Use FIELD_GET/FIELD_PREP Sascha Hauer
2022-02-25 8:29 ` [PATCH v2 4/8] clk: imx: pll14xx: consolidate rate calculation Sascha Hauer
2022-02-25 13:24 ` Abel Vesa
2022-02-25 8:29 ` [PATCH v2 5/8] clk: imx: pll14xx: name variables after usage Sascha Hauer
2022-02-25 13:25 ` Abel Vesa
2022-02-25 8:29 ` [PATCH v2 6/8] clk: imx: pll14xx: explicitly return lowest rate Sascha Hauer
2022-02-25 13:26 ` Abel Vesa [this message]
2022-02-25 8:29 ` [PATCH v2 7/8] clk: imx: pll14xx: Add pr_fmt Sascha Hauer
2022-02-25 13:27 ` Abel Vesa
2022-02-25 8:29 ` [PATCH v2 8/8] clk: imx: pll14xx: Support dynamic rates Sascha Hauer
2022-02-25 14:13 ` Abel Vesa
2022-03-04 8:39 ` Abel Vesa
2022-03-04 12:44 ` Sascha Hauer
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=YhjZFRLeGdsI41qQ@abelvesa \
--to=abel.vesa@nxp.com \
--cc=adrian.alonso@nxp.com \
--cc=bli@bang-olufsen.dk \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=s.hauer@pengutronix.de \
--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