From: Ettore Chimenti <ettore.chimenti@linaro.org>
To: Tero Kristo <kristo@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Tony Lindgren <tony@atomide.com>,
Michael Turquette <mturquette@linaro.org>,
Andrew Goodbody <andrew.goodbody@linaro.org>,
Rouven Czerwinski <rouven.czerwinski@linaro.org>
Cc: linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ettore Chimenti <ettore.chimenti@linaro.org>
Subject: [PATCH v2 0/4] clk: ti: fapll/dm816x: clock tree and calculation fixes
Date: Wed, 28 Oct 2026 16:53:48 +0100 [thread overview]
Message-ID: <20261028-patch-ektor5-dm8168-clk-v2-0-dc6bf0fabae4@linaro.org> (raw)
During TI DM8168-EVM board testing we found that the clock hierarchy and
clock calculation was broken already on 6.12:
main_pll_clk1 <--- main PLL should be parent of other PLLs.
sysclk1_ck
main_pll_clk7
...
main_pll_clk6
...
main_pll_clk5
...
main_pll_clk4
...
This series brings fixes and additions for TI DM816x / FAPLL clock tree
and frequency calculation.
Summary:
- Fix clock tree hierarchy by not using ti_dt_clk_name() helper, that
causes the first PLL as the parent of all clocks in DM816x.
- Correct rate calculation logic in fapll driver (1/2^24, was 1/10^7).
- Add sys_ck alias required for DM816x clock lookup, fixing a boot
error.
- Add error logging for clocks failing registration to ease debugging.
Fixing clock tree hierarchy is critical as it fixes DM8168-EVM boot
failure in 7.3-rc7. These fixes are affecting DM816x SoCs only.
Signed-off-by: Ettore Chimenti <ettore.chimenti@linaro.org>
---
Changes in v2:
- Fixed off-by-one error in clock calculation (Sashiko).
- Fixed clock calculation also in the set rate path.
- Added Fixes tag to clock calculation fix patch.
- Link to v1: https://patch.msgid.link/20261015-patch-ektor5-dm8168-clk-v1-0-8b99c5cd5541@linaro.org
---
Andrew Goodbody (1):
clk: ti: fapll: Fix clock speed calculation
Ettore Chimenti (1):
clk-816x: add sys_ck clock as sys_clkin_ck alias
Rouven Czerwinski (2):
clk: ti: fapll: remove ti_dt_clk_name helper
clk: ti: fapll: print clock name that fails to register
drivers/clk/ti/clk-816x.c | 1 +
drivers/clk/ti/fapll.c | 22 +++++++++-------------
2 files changed, 10 insertions(+), 13 deletions(-)
---
base-commit: d135ab453a7400a34930bdda1ef4bdc8acfac80e
change-id: 20261014-patch-ektor5-dm8168-clk-e426101415b0
Best regards,
--
Ettore Chimenti <ettore.chimenti@linaro.org>
next reply other threads:[~2026-10-28 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 15:53 Ettore Chimenti [this message]
2026-10-28 15:53 ` [PATCH v2 1/4] clk: ti: fapll: remove ti_dt_clk_name helper Ettore Chimenti
2026-10-28 15:53 ` [PATCH v2 2/4] clk: ti: fapll: Fix clock speed calculation Ettore Chimenti
2026-10-28 15:53 ` [PATCH v2 3/4] clk: ti: fapll: print clock name that fails to register Ettore Chimenti
2026-10-28 15:53 ` [PATCH v2 4/4] clk-816x: add sys_ck clock as sys_clkin_ck alias Ettore Chimenti
2026-10-30 10:48 ` Ettore Chimenti
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=20261028-patch-ektor5-dm8168-clk-v2-0-dc6bf0fabae4@linaro.org \
--to=ettore.chimenti@linaro.org \
--cc=andrew.goodbody@linaro.org \
--cc=bmasney+clk@redhat.com \
--cc=jbrunet+clk@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=rouven.czerwinski@linaro.org \
--cc=sboyd@kernel.org \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®