From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@ew.tq-group.com, linux-clk@vger.kernel.org
Subject: [PATCH v2 1/6] clk: imx: fracn-gppll: Add 333.333333 MHz support
Date: Fri, 13 Mar 2026 08:07:31 +0100 [thread overview]
Message-ID: <20260313070740.585043-2-alexander.stein@ew.tq-group.com> (raw)
In-Reply-To: <20260313070740.585043-1-alexander.stein@ew.tq-group.com>
Some parallel panels have a pixelclk of 33.30 MHz. Add support for
333.333333 MHz so a by 10 divider can be used to derive the exact pixelclk.
Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
---
Changes in v2:
* None
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 89ed7749bf47e..fe6ee77ba1485 100644
--- a/drivers/clk/imx/clk-fracn-gppll.c
+++ b/drivers/clk/imx/clk-fracn-gppll.c
@@ -88,6 +88,7 @@ static const struct imx_fracn_gppll_rate_table fracn_tbl[] = {
PLL_FRACN_GP(445333333U, 167, 0, 1, 0, 9),
PLL_FRACN_GP(400000000U, 200, 0, 1, 0, 12),
PLL_FRACN_GP(393216000U, 163, 84, 100, 0, 10),
+ PLL_FRACN_GP(333333333U, 125, 0, 1, 1, 9),
PLL_FRACN_GP(332600000U, 138, 584, 1000, 0, 10),
PLL_FRACN_GP(300000000U, 150, 0, 1, 0, 12),
PLL_FRACN_GP(241900000U, 201, 584, 1000, 0, 20),
--
2.43.0
next prev parent reply other threads:[~2026-03-13 7:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 7:07 [PATCH v2 0/6] TQMa91/TQMa93: display support on MBa91xxCA Alexander Stein
2026-03-13 7:07 ` Alexander Stein [this message]
2026-03-16 6:32 ` [PATCH v2 1/6] clk: imx: fracn-gppll: Add 333.333333 MHz support Peng Fan
2026-03-17 8:20 ` Abel Vesa
2026-03-13 7:07 ` [PATCH v2 2/6] clk: imx: fracn-gppll: Add 477.4MHz support Alexander Stein
2026-03-13 7:07 ` [PATCH v2 3/6] arm64: dts: imx93-tqma9352-mba91xxca: Add parallel display overlay Alexander Stein
2026-03-13 7:07 ` [PATCH v2 4/6] arm64: dts: imx93-tqma9352-mba91xxca: Add LVDS " Alexander Stein
2026-03-13 7:07 ` [PATCH v2 5/6] arm64: dts: imx91-tqma9131-mba91xxca: Add parallel " Alexander Stein
2026-03-13 7:07 ` [PATCH v2 6/6] arm64: dts: imx91-tqma9131-mba91xxca: Add LVDS " Alexander Stein
2026-03-18 15:39 ` (subset) [PATCH v2 0/6] TQMa91/TQMa93: display support on MBa91xxCA Abel Vesa
2026-03-23 22:46 ` Frank Li
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=20260313070740.585043-2-alexander.stein@ew.tq-group.com \
--to=alexander.stein@ew.tq-group.com \
--cc=Frank.Li@nxp.com \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--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