From: Peng Fan <peng.fan@oss.nxp.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Brian Masney <bmasney@redhat.com>,
Conor Dooley <conor+dt@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Marco Felsch <m.felsch@pengutronix.de>,
Michael Turquette <mturquette@baylibre.com>,
Peng Fan <peng.fan@nxp.com>, Rob Herring <robh@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/5] clk: Introduce clk_hw_set_spread_spectrum
Date: Mon, 22 Sep 2025 10:05:11 +0800 [thread overview]
Message-ID: <20250922020511.GA14753@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <175848801471.4354.13819701022920596111@lazor>
Hi Stephen,
On Sun, Sep 21, 2025 at 01:53:34PM -0700, Stephen Boyd wrote:
>Quoting Peng Fan (2025-09-15 01:29:36)
>> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
>> index b821b2cdb155331c85fafbd2fac8ab3703a08e4d..06db8918a1b35e3280e565272bc4603a88295a92 100644
>> --- a/drivers/clk/clk.c
>> +++ b/drivers/clk/clk.c
>> @@ -2802,6 +2802,32 @@ int clk_set_max_rate(struct clk *clk, unsigned long rate)
>> }
>> EXPORT_SYMBOL_GPL(clk_set_max_rate);
>>
>> +int clk_hw_set_spread_spectrum(struct clk_hw *hw, struct clk_spread_spectrum *conf)
>> +{
...
>> + return ret;
>> +}
>
>Does it need to be exported?
Yeah. it should be exported, I will add it in v5.
>
>> +
>> /**
>> * clk_get_parent - return the parent of a clk
>> * @clk: the clk whose parent gets returned
>> diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
>> index 630705a47129453c241f1b1755f2c2f2a7ed8f77..4f48a4df95a1c54638a0e91e0a449fcc8aa40b80 100644
>> --- a/include/linux/clk-provider.h
>> +++ b/include/linux/clk-provider.h
>> @@ -84,6 +84,19 @@ struct clk_duty {
>> unsigned int den;
>> };
>>
>> +/**
>> + * struct clk_spread_spectrum - Structure encoding spread spectrum of a clock
>> + *
>> + * @modfreq_hz: Modulation frequency
>> + * @spread_bp: Modulation percent in permyriad
>> + * @method: Modulation method
>> + */
>> +struct clk_spread_spectrum {
>> + u32 modfreq_hz;
>> + u32 spread_bp;
>> + u32 method;
>
>What are the possible values of 'method'? I'm guessing it's the defines
>in the dt-bindings header?
Yes. The values are in dt-bindings header and aligned with dt-schema.
>Please connect these two somehow, maybe
>through an enum.
ok. I will add back enum in V5.
>Also, why are these u32? Shouldn't these be more common
>types like unsigned long or unsigned long long instead being exactly 32
>bits?
u32 is large enough for modfreq_hz and spread_bp.
modfreq_hz will not exceed a few MHz, normally [1-9] * 10KHz per my
understanding.
>
>> +};
>> +
>> /**
>> * struct clk_ops - Callback operations for hardware clocks; these are to
>> * be provided by the clock implementation, and will be called by drivers
>> @@ -178,6 +191,12 @@ struct clk_duty {
>> * separately via calls to .set_parent and .set_rate.
>> * Returns 0 on success, -EERROR otherwise.
>> *
>> + * @set_spread_spectrum: Optional callback used to configure the spread
>> + * spectrum modulation frequency, percentage, and method
>> + * to reduce EMI by spreading the clock frequency over a
>> + * wider range.
>> + * Returns 0 on success, -EERROR otherwise.
>> + *
>> * @recalc_accuracy: Recalculate the accuracy of this clock. The clock accuracy
>> * is expressed in ppb (parts per billion). The parent accuracy is
>> * an input parameter.
>> @@ -255,6 +274,8 @@ struct clk_ops {
>> int (*set_rate_and_parent)(struct clk_hw *hw,
>> unsigned long rate,
>> unsigned long parent_rate, u8 index);
>> + int (*set_spread_spectrum)(struct clk_hw *hw,
>> + struct clk_spread_spectrum *clk_ss);
>
>const clk_ss pointer? And is it actually 'conf' or 'ss_conf'?
I will use "const clk_spread_spectrum *ss_conf" in v5.
>
>> unsigned long (*recalc_accuracy)(struct clk_hw *hw,
>> unsigned long parent_accuracy);
>> int (*get_phase)(struct clk_hw *hw);
>> @@ -1430,6 +1451,7 @@ void clk_hw_get_rate_range(struct clk_hw *hw, unsigned long *min_rate,
>> unsigned long *max_rate);
>> void clk_hw_set_rate_range(struct clk_hw *hw, unsigned long min_rate,
>> unsigned long max_rate);
>> +int clk_hw_set_spread_spectrum(struct clk_hw *hw, struct clk_spread_spectrum *conf);
>
>const conf? And 'ss_conf' again?
yeah. Fix in v5.
Thanks,
Peng
next prev parent reply other threads:[~2025-09-22 0:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 8:29 [PATCH v4 0/5] clk: Support spread spectrum and use it in clk-scmi Peng Fan
2025-09-15 8:29 ` [PATCH v4 1/5] dt-bindings: clock: Add spread spectrum definition Peng Fan
2025-09-22 16:02 ` Rob Herring (Arm)
2025-09-15 8:29 ` [PATCH v4 2/5] clk: Introduce clk_hw_set_spread_spectrum Peng Fan
2025-09-21 20:53 ` Stephen Boyd
2025-09-22 2:05 ` Peng Fan [this message]
2025-09-15 8:29 ` [PATCH v4 3/5] clk: conf: Support assigned-clock-sscs Peng Fan
2025-10-06 10:44 ` Sebin Francis
2025-10-08 12:31 ` Peng Fan
2025-09-15 8:29 ` [PATCH v4 4/5] clk: Add KUnit tests for assigned-clock-sscs Peng Fan
2025-09-15 12:29 ` Brian Masney
2025-09-15 8:29 ` [PATCH v4 5/5] clk: scmi: Support Spread Spectrum for NXP i.MX95 Peng Fan
2025-09-23 10:52 ` Sebin Francis
2025-09-23 11:57 ` Peng Fan
2025-09-24 9:25 ` Sebin Francis
2025-09-24 11:43 ` Peng Fan
2025-09-24 12:15 ` Sebin Francis
2025-09-24 12:40 ` Cristian Marussi
2025-09-24 12:59 ` Sudeep Holla
2025-09-24 14:14 ` Peng Fan
2025-09-24 13:13 ` Sudeep Holla
2025-09-24 14:35 ` Peng Fan
2025-09-24 14:44 ` [PATCH v4 0/5] clk: Support spread spectrum and use it in clk-scmi Peng Fan
2025-09-24 15:33 ` Brian Masney
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=20250922020511.GA14753@nxa18884-linux.ap.freescale.net \
--to=peng.fan@oss.nxp.com \
--cc=arm-scmi@vger.kernel.org \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--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=m.felsch@pengutronix.de \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.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®