linux-kernel - Re: [PATCH] clk: Add clk_determine

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: <aFHKGvHlXP-cdC7d@x1>
Date: Tue, 17 Jun 2025 16:03:38 -0400
From: Brian Masney <bmasney@...hat.com>
To: Jayesh Choudhary <j-choudhary@...com>
Cc: mturquette@...libre.com, sboyd@...nel.org, linux@...linux.org.uk,
	linux-clk@...r.kernel.org, devarsht@...com,
	linux-kernel@...r.kernel.org, tomi.valkeinen@...asonboard.com,
	Maxime Ripard <mripard@...nel.org>
Subject: Re: [PATCH] clk: Add clk_determine_rate function call

On Mon, Jun 16, 2025 at 04:05:27PM +0530, Jayesh Choudhary wrote:
> Add a function to determine if a particular rate can be set for a clock
> with its argument being the clock and the desired rate so that it could
> be exposed to other peripherals.
> For example, the display controllers typically has to perform multiple
> checks for supported display resolutions including those related to
> clock rates. The controller has to check this way before it actually
> enables the clock and has to do it multiple times (typically for each
> mode), and therefore using the clk_set_rate when its not needed, does
> not make sense.
> 
> The driver does have "__clk_determine_rate()" but this cannot be used
> by other subsystems because of the function arguments used.
> "clk_hw" is not accessible to other peripherals due to clk and clk_core
> structure definition in driver instead of include file, so we cannot use
> already exisiting "__clk_determine_rate()" in other drivers.
> 
> Signed-off-by: Jayesh Choudhary <j-choudhary@...com>

Do you have a link to how this will be used within the DRM subsystem? If
not, could you post a new series to include the user of this new API so
that we can see specifically how it will be used.

Thanks,

Brian