From: Beleswar Padhi <b-padhi@ti.com>
To: <nm@ti.com>, <kristo@kernel.org>, <ssantosh@kernel.org>,
<sboyd@kernel.org>, <bmasney+clk@redhat.com>,
<jbrunet+clk@baylibre.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<afd@ti.com>, <u-kumar1@ti.com>, <vigneshr@ti.com>,
<b-padhi@ti.com>
Subject: [PATCH] clk: keystone: sci-clk: Handle missing get_num_parents operation
Date: Thu, 1 Oct 2026 00:33:48 +0530 [thread overview]
Message-ID: <20260930190348.11720-1-b-padhi@ti.com> (raw)
The sci-clk driver unconditionally calls the get_num_parents TI-SCI
operation while scanning clocks, both from DT and from firmware. This
works for all cases today, but with future support for some System
Controllers (e.g. PDM on TDA54), this may not be always right.
The PDM system controller on TI TDA54 SoC manages clock parents
internally and does not support the clock parent related ops. Therefore,
when scanning clocks from DT, treat the clock as having a single parent
if get_num_parents is not provided. Such a clock is registered without
parents, so the get_parent and set_parent operations are never invoked
for it.
Scanning clocks from firmware relies on get_num_parents to discover the
valid clock IDs, so return -EOPNOTSUPP in that case instead.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
---
Testing Done:
- Boot test on all keystone and K3 platforms.
- Verified that the patch does not result in any warnings or errors
Logs:
https://gist.github.com/3V3RYONE/d821cea46f5dc1e70a759c97878fa487
Note:
This patch is independent and can be applied directly.
drivers/clk/keystone/sci-clk.c | 23 +++++++++++++++++++----
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/drivers/clk/keystone/sci-clk.c b/drivers/clk/keystone/sci-clk.c
index 9d2094bd48e3b..5bf615893a8c0 100644
--- a/drivers/clk/keystone/sci-clk.c
+++ b/drivers/clk/keystone/sci-clk.c
@@ -468,6 +468,13 @@ static int ti_sci_scan_clocks_from_fw(struct sci_clk_provider *provider)
int gap_size = 0;
struct device *dev = provider->dev;
+ /*
+ * Clocks are discovered by probing the firmware with get_num_parents,
+ * which is not available with every system firmware (e.g. ABI5.0 PDM).
+ */
+ if (!provider->ops->get_num_parents)
+ return -EOPNOTSUPP;
+
while (1) {
ret = provider->ops->get_num_parents(provider->sci, dev_id,
clk_id,
@@ -589,10 +596,18 @@ static int ti_sci_scan_clocks_from_dt(struct sci_clk_provider *provider)
sci_clk->dev_id = args.args[0];
sci_clk->clk_id = args.args[1];
sci_clk->provider = provider;
- provider->ops->get_num_parents(provider->sci,
- sci_clk->dev_id,
- sci_clk->clk_id,
- (void *)&sci_clk->num_parents);
+ /*
+ * Firmware without get_num_parents (e.g. ABI5.0
+ * PDM) manages clock parents internally, so
+ * treat the clock as having a single parent.
+ */
+ if (provider->ops->get_num_parents)
+ provider->ops->get_num_parents(provider->sci,
+ sci_clk->dev_id,
+ sci_clk->clk_id,
+ &sci_clk->num_parents);
+ else
+ sci_clk->num_parents = 1;
list_add_tail(&sci_clk->node, &clks);
num_clks++;
--
2.34.1
next reply other threads:[~2026-09-30 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 19:03 Beleswar Padhi [this message]
2026-09-30 19:19 ` Andrew Davis
2026-09-30 20:58 ` Padhi, Beleswar
2026-09-30 22:52 ` Andrew Davis
2026-10-01 6:34 ` Padhi, Beleswar
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=20260930190348.11720-1-b-padhi@ti.com \
--to=b-padhi@ti.com \
--cc=afd@ti.com \
--cc=bmasney+clk@redhat.com \
--cc=jbrunet+clk@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=sboyd@kernel.org \
--cc=ssantosh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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®