* [PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions
@ 2023-09-05 22:16 Maksim Kiselev
2023-11-01 18:52 ` Sean Anderson
2023-11-01 21:03 ` Sean Anderson
0 siblings, 2 replies; 3+ messages in thread
From: Maksim Kiselev @ 2023-09-05 22:16 UTC (permalink / raw)
To: u-boot; +Cc: Maksim Kiselev, Lukasz Majewski, Sean Anderson
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 <bigunclemax@gmail.com>
---
drivers/clk/clk-uclass.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/clk-uclass.c b/drivers/clk/clk-uclass.c
index dc3e9d6a26..542ec41cba 100644
--- a/drivers/clk/clk-uclass.c
+++ b/drivers/clk/clk-uclass.c
@@ -649,7 +649,7 @@ int clk_enable(struct clk *clk)
}
if (ops->enable) {
- ret = ops->enable(clk);
+ ret = ops->enable(clkp ? clkp : clk);
if (ret) {
printf("Enable %s failed\n", clk->dev->name);
return ret;
@@ -706,7 +706,7 @@ int clk_disable(struct clk *clk)
}
if (ops->disable) {
- ret = ops->disable(clk);
+ ret = ops->disable(clkp ? clkp : clk);
if (ret)
return ret;
}
--
2.39.2
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions
2023-09-05 22:16 [PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions Maksim Kiselev
@ 2023-11-01 18:52 ` Sean Anderson
2023-11-01 21:03 ` Sean Anderson
1 sibling, 0 replies; 3+ messages in thread
From: Sean Anderson @ 2023-11-01 18:52 UTC (permalink / raw)
To: Maksim Kiselev, u-boot; +Cc: Lukasz Majewski
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 struct to
> container_of() results in an out of range error.
Yeah...
This is a big problem in the CCF code, where `struct clk` in U-Boot is
both `struct clk` from Linux (a "thick" pointer) and `struct clk_core`
(all the clock private data).
> 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
correctly
> must be passed.
>
> Signed-off-by: Maksim Kiselev <bigunclemax@gmail.com>
> ---
> drivers/clk/clk-uclass.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/clk-uclass.c b/drivers/clk/clk-uclass.c
> index dc3e9d6a26..542ec41cba 100644
> --- a/drivers/clk/clk-uclass.c
> +++ b/drivers/clk/clk-uclass.c
> @@ -649,7 +649,7 @@ int clk_enable(struct clk *clk)
> }
>
> if (ops->enable) {
> - ret = ops->enable(clk);
> + ret = ops->enable(clkp ? clkp : clk);
> if (ret) {
> printf("Enable %s failed\n", clk->dev->name);
> return ret;
> @@ -706,7 +706,7 @@ int clk_disable(struct clk *clk)
> }
>
> if (ops->disable) {
> - ret = ops->disable(clk);
> + ret = ops->disable(clkp ? clkp : clk);
> if (ret)
> return ret;
> }
Reviewed-by: Sean Anderson <seanga2@gmail.com>
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions
2023-09-05 22:16 [PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions Maksim Kiselev
2023-11-01 18:52 ` Sean Anderson
@ 2023-11-01 21:03 ` Sean Anderson
1 sibling, 0 replies; 3+ messages in thread
From: Sean Anderson @ 2023-11-01 21:03 UTC (permalink / raw)
To: bigunclemax, u-boot; +Cc: Sean Anderson, Lukasz Majewski
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 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.
>
> [...]
Applied, thanks!
[1/1] clk: use private clk struct in CLK_CCF's enable/disable functions
commit: 0755db477fa7478e2659568bb7da038a9eaabb8d
Best regards,
--
Sean Anderson <seanga2@gmail.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-11-01 21:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-05 22:16 [PATCH v1] clk: use private clk struct in CLK_CCF's enable/disable functions Maksim Kiselev
2023-11-01 18:52 ` Sean Anderson
2023-11-01 21:03 ` Sean Anderson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox