Re: [PATCH] clk: Add clk_determine_rate function call

[Jayesh Choudhary]

Hello Brian,

On 18/06/25 01:33, Brian Masney wrote:
> 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@xxxxxx>
>
> 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

Based on the conversation in [1], this patch is no longer required.
This can be handled with preexisting functions.

[1]: 
https://lore.kernel.org/all/f2e54128-f7c1-4193-a511-13775559e261@xxxxxx/

Thanks and Warm Regards,
Jayesh