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] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <PAXPR04MB84594DDFFE47E67552718F77881CA@PAXPR04MB8459.eurprd04.prod.outlook.com>
Date: Wed, 24 Sep 2025 14:14:11 +0000
From: Peng Fan <peng.fan@....com>
To: Cristian Marussi <cristian.marussi@....com>, Sebin Francis
	<sebin.francis@...com>
CC: Michael Turquette <mturquette@...libre.com>, Stephen Boyd
	<sboyd@...nel.org>, Sudeep Holla <sudeep.holla@....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>, Dhruva Gole <d-gole@...com>, 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 Cristian,

> Subject: Re: [PATCH v4 5/5] clk: scmi: Support Spread Spectrum for
> NXP i.MX95
>
...
 
> 
> So yes the ideal solutiomn would be to extend in a generic way the
> SCMI framework so that you can add in these cases custom handling of
> vendor extensions for standard protocols (and then generalize the
> current clk-scmi IMX support and add the new TI one...)...but I have not
> thought about this and I certainly dont have enough bandwidth now to
> work on this

I see. So I get the point IMX SSC OEM is allowed, but need an elegant way
to extend SCMI framework or extend clk-scmi.c in an elegant way to make
it easier to support other platforms. 

...beside having already in the pipeline other stuff/fixes like
> a proper fix for vendor drivers coex like Peng askes (rightly so a few
> months ago)

Thanks for working on that.

I could continue give a look on this, if any suggestions, I would appreciate
that.

Thanks
Peng

> 
> Thanks,
> Cristian