On Mon, 24 Jan 2022 14:17:14 +0100, Patrick Delaunay wrote:
> It is safe to check if the uclass id on the device is UCLASS_CLK
> before to call the clk_ functions, but today this comparison is
> not done on the device used in API: clkp->dev->parent
> but on the device himself: clkp->dev.
>
> This patch corrects this behavior and tests if the parent device
> is a clock device before to call the clock API, clk_enable or
> clk_disable, on this device.
>
> [...]
Applied, thanks!
[1/1] clk: ccf: correct the test on the parent uclass in clk_enable/clk_disable
commit: b0cdd8287add19d1af6668b6e9e968046506c08d
Best regards,
--
Sean Anderson <sean...@gmail.com>
