Linux clock framework development
 help / color / mirror / Atom feed
From: Jacky Bai <ping.bai@nxp.com>
To: abelvesa@kernel.org, peng.fan@nxp.com, sboyd@kernel.org,
	shawnguo@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH 3/3] clk: imx: Add 519.75MHz frequency support for imx9 pll
Date: Wed, 28 Jun 2023 14:17:24 +0800	[thread overview]
Message-ID: <20230628061724.2056520-3-ping.bai@nxp.com> (raw)
In-Reply-To: <20230628061724.2056520-1-ping.bai@nxp.com>

For video pll, it may need 519.75MHz clock frequency for
the LVDS display usage. So add 519.75MHz frequency config
support for video pll.

Signed-off-by: Jacky Bai <ping.bai@nxp.com>
---
 drivers/clk/imx/clk-fracn-gppll.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/clk/imx/clk-fracn-gppll.c b/drivers/clk/imx/clk-fracn-gppll.c
index c54f9999da04..44462ab50e51 100644
--- a/drivers/clk/imx/clk-fracn-gppll.c
+++ b/drivers/clk/imx/clk-fracn-gppll.c
@@ -81,6 +81,7 @@ static const struct imx_fracn_gppll_rate_table fracn_tbl[] = {
 	PLL_FRACN_GP(650000000U, 162, 50, 100, 0, 6),
 	PLL_FRACN_GP(594000000U, 198, 0, 1, 0, 8),
 	PLL_FRACN_GP(560000000U, 140, 0, 1, 0, 6),
+	PLL_FRACN_GP(519750000U, 173, 25, 100, 1, 8),
 	PLL_FRACN_GP(498000000U, 166, 0, 1, 0, 8),
 	PLL_FRACN_GP(484000000U, 121, 0, 1, 0, 6),
 	PLL_FRACN_GP(445333333U, 167, 0, 1, 0, 9),
-- 
2.34.1


  parent reply	other threads:[~2023-06-28  9:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  6:17 [PATCH 1/3] dt-bindings: clock: imx93: Add PDM IPG clk Jacky Bai
2023-06-28  6:17 ` [PATCH 2/3] clk: " Jacky Bai
2023-06-30  6:55   ` Peng Fan
2023-06-28  6:17 ` Jacky Bai [this message]
2023-06-30  6:55   ` [PATCH 3/3] clk: imx: Add 519.75MHz frequency support for imx9 pll Peng Fan
2023-06-30  6:55 ` [PATCH 1/3] dt-bindings: clock: imx93: Add PDM IPG clk Peng Fan
2023-07-02 10:44 ` Krzysztof Kozlowski
2023-07-25  8:22 ` Abel Vesa

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=20230628061724.2056520-3-ping.bai@nxp.com \
    --to=ping.bai@nxp.com \
    --cc=abelvesa@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@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