From: Dominique Martinet <dominique.martinet@atmark-techno.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-phy@lists.infradead.org, linux-imx@nxp.com,
festevam@gmail.com, frieder.schrempf@kontron.de,
aford@beaconembedded.com, Sandor.yu@nxp.com,
"Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Marco Felsch" <m.felsch@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lucas Stach" <l.stach@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V7 4/5] phy: freescale: fsl-samsung-hdmi: Use closest divider
Date: Wed, 11 Sep 2024 14:27:17 +0900 [thread overview]
Message-ID: <ZuEqNVWSPXXR1YHM@atmark-techno.com> (raw)
In-Reply-To: <20240911012838.944630-5-aford173@gmail.com>
Adam Ford wrote on Tue, Sep 10, 2024 at 08:28:10PM -0500:
> Currently, if the clock values cannot be set to the exact rate,
> the round_rate and set_rate functions use the closest value found in
> the look-up-table. In preparation of removing values from the LUT
> that can be calculated evenly with the integer calculator, it's
> necessary to ensure to check both the look-up-table and the integer
> divider clock values to get the closest values to the requested
> value. It does this by measuring the difference between the
> requested clock value and the closest value in both integer divider
> calucator and the fractional clock look-up-table.
>
> Which ever has the smallest difference between them is returned as
> the closest rate.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
Thank you for the rework,
Reviewed-by: Dominique Martinet <dominique.martinet@atmark-techno.com>
Tested-by: Dominique Martinet <dominique.martinet@atmark-techno.com>
> ---
> V7: Because of the previous patch refactoring, the flow of this patch
> changed quite a bit to use more help functions and goto statements
> to hopefully make the code flow better and improve comment
> readability. Because of the change, I removed s-o-b and r-b,
> and t-b tags.
>
> V6: Simplify the calculation of the closest rate and fix
> a situation where the integer divider values may not be properly
> setup before they are used.
> Fixup some comments
> V5: No Change
> V4: New to series
> ---
> drivers/phy/freescale/phy-fsl-samsung-hdmi.c | 40 ++++++++++++++------
> 1 file changed, 28 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/phy/freescale/phy-fsl-samsung-hdmi.c b/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
> index 49317a96f767..67a28aac9c45 100644
> --- a/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
> +++ b/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
> @@ -577,6 +577,16 @@ static void fsl_samsung_hdmi_calculate_phy(struct phy_config *cal_phy, unsigned
> /* pll_div_regs 3-6 are fixed and pre-defined already */
> }
>
> +static u32 fsl_samsung_hdmi_phy_get_closest_rate(unsigned long rate,
> + u32 int_div_clk, u32 frac_div_clk)
> +{
> + /* The int_div_clk may be greater than rate, so cast it and use ABS */
> + if (abs((long)rate - (long)int_div_clk) < (rate - frac_div_clk))
> + return int_div_clk;
> +
> + return frac_div_clk;
> +}
> +
> static long phy_clk_round_rate(struct clk_hw *hw,
> unsigned long rate, unsigned long *parent_rate)
> {
> @@ -624,27 +634,33 @@ static int phy_clk_set_rate(struct clk_hw *hw,
> goto use_fract_div;
>
> /*
> - * If the rate from the fractional divder is not exact, check the integer divider,
> + * If the rate from the fractional divider is not exact, check the integer divider,
> * and use it if that value is an exact match.
> */
> int_div_clk = fsl_samsung_hdmi_phy_find_pms(rate, &p, &m, &s);
> + fsl_samsung_hdmi_calculate_phy(&calculated_phy_pll_cfg, int_div_clk, p, m, s);
> if (int_div_clk == rate) {
> - dev_dbg(phy->dev, "fsl_samsung_hdmi_phy: integer divider rate = %u\n",
> - int_div_clk);
> -
> - fsl_samsung_hdmi_calculate_phy(&calculated_phy_pll_cfg, int_div_clk, p, m, s);
> - phy->cur_cfg = &calculated_phy_pll_cfg;
> - return fsl_samsung_hdmi_phy_configure(phy, phy->cur_cfg);
> + goto use_int_div;
> }
>
> /*
> - * If neither the fractional divder nor the integer divder can find an exact value
> - * fall back to using the fractional divider
> + * Compare the difference between the integer clock and the fractional clock against
> + * the desired clock and which whichever is closest,
> */
> + if (fsl_samsung_hdmi_phy_get_closest_rate(rate, int_div_clk,
> + fract_div_phy->pixclk) == fract_div_phy->pixclk)
> + goto use_fract_div;
> +
> +use_int_div:
> + dev_dbg(phy->dev, "fsl_samsung_hdmi_phy: integer divider rate = %u\n", int_div_clk);
> + phy->cur_cfg = &calculated_phy_pll_cfg;
> + goto end;
> +
> use_fract_div:
> - phy->cur_cfg = fract_div_phy;
> - dev_dbg(phy->dev, "fsl_samsung_hdmi_phy: using fractional divider rate = %u\n",
> - phy->cur_cfg->pixclk);
> + phy->cur_cfg = fract_div_phy;
> + dev_dbg(phy->dev, "fsl_samsung_hdmi_phy: using fractional divider rate = %u\n",
> + phy->cur_cfg->pixclk);
> +end:
> return fsl_samsung_hdmi_phy_configure(phy, phy->cur_cfg);
> }
>
next prev parent reply other threads:[~2024-09-11 5:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 1:28 [PATCH V7 0/5] phy: freescale: fsl-samsung-hdmi: Expand phy clock options Adam Ford
2024-09-11 1:28 ` [PATCH V7 1/5] phy: freescale: fsl-samsung-hdmi: Replace register defines with macro Adam Ford
2024-09-11 5:12 ` Dominique Martinet
2024-09-11 1:28 ` [PATCH V7 2/5] phy: freescale: fsl-samsung-hdmi: Simplify REG21_PMS_S_MASK lookup Adam Ford
2024-09-11 5:23 ` Dominique Martinet
2024-09-11 1:28 ` [PATCH V7 3/5] xphy: freescale: fsl-samsung-hdmi: Support dynamic integer Adam Ford
2024-09-11 5:26 ` Dominique Martinet
2024-09-11 7:01 ` Frieder Schrempf
2024-09-11 1:28 ` [PATCH V7 4/5] phy: freescale: fsl-samsung-hdmi: Use closest divider Adam Ford
2024-09-11 5:27 ` Dominique Martinet [this message]
2024-09-11 7:07 ` Frieder Schrempf
2024-09-11 1:28 ` [PATCH V7 5/5] phy: freescale: fsl-samsung-hdmi: Remove unnecessary LUT entries Adam Ford
2024-09-11 5:47 ` Dominique Martinet
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=ZuEqNVWSPXXR1YHM@atmark-techno.com \
--to=dominique.martinet@atmark-techno.com \
--cc=Sandor.yu@nxp.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=kishon@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=m.felsch@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vkoul@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