linux-kernel - Re: [PATCH v2 1/5] clk: scmi: Allocate CLK operations dynamically

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: <4e014c33-44d7-483c-a9be-b24bb82cd1aa@gmail.com>
Date: Fri, 29 Mar 2024 20:42:49 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Cristian Marussi <cristian.marussi@....com>,
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-clk@...r.kernel.org
Cc: sudeep.holla@....com, james.quinlan@...adcom.com,
 vincent.guittot@...aro.org, peng.fan@....nxp.com, michal.simek@....com,
 quic_sibis@...cinc.com, quic_nkela@...cinc.com, souvik.chakravarty@....com,
 mturquette@...libre.com, sboyd@...nel.org
Subject: Re: [PATCH v2 1/5] clk: scmi: Allocate CLK operations dynamically



On 25/03/2024 14:00, Cristian Marussi wrote:
> SCMI Clocks descriptors expose an increasing number of properties, thing
> which, in turn, leads to a varying set of supported CLK operations to be
> associated with each clock.
> 
> Providing statically pre-defined CLK operations structs for all the
> possible combinations of allowed clock features is becoming cumbersome and
> error-prone.
> 
> Allocate the per-clock operations descriptors dynamically and populate it
> with the strictly needed set of operations depending on the advertised
> clock properties: one descriptor is created for each distinct combination
> of clock operations, so minimizing the number of clk_ops structures to the
> strictly minimum needed.
> 
> CC: Michael Turquette <mturquette@...libre.com>
> CC: Stephen Boyd <sboyd@...nel.org>
> CC: linux-clk@...r.kernel.org
> Signed-off-by: Cristian Marussi <cristian.marussi@....com>

Reviewed-by: Florian Fainelli <florian.fainelli@...adcom.com>
-- 
Florian