Re: [PATCH v5 12/27] clk: bcm: rpi: Use CCF boundaries instead of rolling our own
From: Stephen Boyd <sboyd@kernel.org>
Date: 2020-06-25 00:44:52
Also in:
linux-clk, lkml
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 <redacted> Tested-by: Nicolas Saenz Julienne <redacted> Signed-off-by: Maxime Ripard <redacted> ---
Applied to clk-next _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel