[PATCH v5 12/27] clk: bcm: rpi: Use CCF boundaries instead of rolling our own

Stephen Boyd sboyd at kernel.org
Wed Jun 24 20:44:49 EDT 2020

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 at suse.de>
> Tested-by: Nicolas Saenz Julienne <nsaenzjulienne at suse.de>
> Signed-off-by: Maxime Ripard <maxime at cerno.tech>
> ---

Applied to clk-next

More information about the linux-arm-kernel mailing list