Re: [PATCH] clk: ccf: correct the test on the parent uclass in clk_enable/clk_disable

2022-02-24 Thread Sean Anderson
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

Re: [PATCH] clk: ccf: correct the test on the parent uclass in clk_enable/clk_disable

2022-02-01 Thread Sean Anderson
On 1/24/22 8:17 AM, 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

[PATCH] clk: ccf: correct the test on the parent uclass in clk_enable/clk_disable

2022-01-24 Thread Patrick Delaunay
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