diff options
| author | Maksim Kiselev <[email protected]> | 2023-09-06 01:16:49 +0300 |
|---|---|---|
| committer | Sean Anderson <[email protected]> | 2023-11-01 15:14:09 -0400 |
| commit | 0755db477fa7478e2659568bb7da038a9eaabb8d (patch) | |
| tree | 40a0862bd3664a6fe9dffeca4d2d778989dacc8f /doc/develop/python_cq.rst | |
| parent | b6a56f553318b4c0c8fb8b1ea05f2e15b2662ccb (diff) | |
clk: use private clk struct in CLK_CCF's enable/disable functions
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 of range error.
At the moment, clk-mux, clk-fixed-factor, clk-gate and possibly other
clocks use container_of() in their enable()/disable() functions.
Therefore, for these functions to work correclty, private clk struct
must be passed.
Signed-off-by: Maksim Kiselev <[email protected]>
Reviewed-by: Sean Anderson <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'doc/develop/python_cq.rst')
0 files changed, 0 insertions, 0 deletions
