Re: [PATCH v5 12/27] clk: bcm: rpi: Use CCF boundaries instead of rolling our own
From: Stephen Boyd
Date: Wed Jun 24 2020 - 20:44:52 EST
Quoting Maxime Ripard (2020-06-15 01:40:52)
> The raspberrypi firmware clock driver has a min_rate / max_rate clamping by
> storing the info it needs in a private structure.
>
> However, the CCF already provides such a facility, so we can switch to it
> to remove the boilerplate.
>
> Reviewed-by: Nicolas Saenz Julienne <nsaenzjulienne@xxxxxxx>
> Tested-by: Nicolas Saenz Julienne <nsaenzjulienne@xxxxxxx>
> Signed-off-by: Maxime Ripard <maxime@xxxxxxxxxx>
> ---
Applied to clk-next