linux-kernel - RE: [PATCH v4 5/5] clk: scmi: Support Spread Spectrum for NXP i.MX95

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID:
 <PAXPR04MB8459CE9F22CD56A9BFDB5E78881DA@PAXPR04MB8459.eurprd04.prod.outlook.com>
Date: Tue, 23 Sep 2025 11:57:48 +0000
From: Peng Fan <peng.fan@....com>
To: Sebin Francis <sebin.francis@...com>, Michael Turquette
	<mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, Sudeep Holla
	<sudeep.holla@....com>, Cristian Marussi <cristian.marussi@....com>, Marco
 Felsch <m.felsch@...gutronix.de>, Rob Herring <robh@...nel.org>, Krzysztof
 Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Brian
 Masney <bmasney@...hat.com>
CC: Dan Carpenter <dan.carpenter@...aro.org>, Geert Uytterhoeven
	<geert@...ux-m68k.org>, "linux-clk@...r.kernel.org"
	<linux-clk@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "arm-scmi@...r.kernel.org"
	<arm-scmi@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "devicetree@...r.kernel.org"
	<devicetree@...r.kernel.org>
Subject: RE: [PATCH v4 5/5] clk: scmi: Support Spread Spectrum for NXP i.MX95

Hi Sebin,

> Subject: Re: [PATCH v4 5/5] clk: scmi: Support Spread Spectrum for
> NXP i.MX95
> 
> > --- a/include/linux/scmi_protocol.h
> > +++ b/include/linux/scmi_protocol.h
> > @@ -80,9 +80,14 @@ enum scmi_clock_oem_config {
> >       SCMI_CLOCK_CFG_DUTY_CYCLE = 0x1,
> >       SCMI_CLOCK_CFG_PHASE,
> >       SCMI_CLOCK_CFG_OEM_START = 0x80,
> > +     SCMI_CLOCK_CFG_IMX_SSC = 0x80,
> 
> TI is also planning to implement the same in our upcoming platform. so
> can we use a generic ID instead of vender specfic message ID?

I tried to push to new generic ID [1] in half a year ago, but in the end ARM
decided not to add generic ID for spread spectrum support.

To i.MX, it is too late to use a generic ID and waiting spec, i.MX firmware
has been public for quite some time and passed several external releases.
So I need to use what our firmware adds and spec allows: vendor
extension.

[1] https://lore.kernel.org/arm-scmi/Z8iKErarE0lHWxEy@pluto/

Regards,
Peng.