Re: [PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions

2023-11-01 Thread Sean Anderson
On Wed, 6 Sep 2023 01:16:49 +0300, Maksim Kiselev wrote: > In clk_enable()/clk_disable() functions, when CCF is activated, > we must pass a private clk struct to enable()/disable() ops functions. > Otherwise, the use of a container_of() construction within these ops > should be banned. Because pass

Re: [PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions

2023-11-01 Thread Sean Anderson
On 9/5/23 18:16, Maksim Kiselev wrote: In clk_enable()/clk_disable() functions, when CCF is activated, we must pass a private clk struct to enable()/disable() ops functions. Otherwise, the use of a container_of() construction within these ops should be banned. Because passing a non-private clk st

[PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions

2023-09-05 Thread Maksim Kiselev
In clk_enable()/clk_disable() functions, when CCF is activated, we must pass a private clk struct to enable()/disable() ops functions. Otherwise, the use of a container_of() construction within these ops should be banned. Because passing a non-private clk struct to container_of() results in an out