blob: 2d809571693e544eafa3f9d64bd702e838c7cd62 [file] [log] [blame]
From 893a40d937aca18329eef739610edc1e2c8ce9ab Mon Sep 17 00:00:00 2001
From: Michael Hennerich <>
Date: Fri, 8 Nov 2019 09:17:18 +0200
Subject: [PATCH] clk: clk-gpio: propagate rate change to parent
commit fc59462c5ce60da119568fac325c92fc6b7c6175 upstream.
For an external clock source, which is gated via a GPIO, the
rate change should typically be propagated to the parent clock.
The situation where we are requiring this propagation, is when an
external clock is connected to override an internal clock (which typically
has a fixed rate). The external clock can have a different rate than the
internal one, and may also be variable, thus requiring the rate
This rate change wasn't propagated until now, and it's unclear about cases
where this shouldn't be propagated. Thus, it's unclear whether this is
fixing a bug, or extending the current driver behavior. Also, it's unsure
about whether this may break any existing setups; in the case that it does,
a device-tree property may be added to disable this flag.
Signed-off-by: Michael Hennerich <>
Signed-off-by: Alexandru Ardelean <>
Signed-off-by: Stephen Boyd <>
Signed-off-by: Paul Gortmaker <>
diff --git a/drivers/clk/clk-gpio.c b/drivers/clk/clk-gpio.c
index 9d930edd6516..13304cf5f2a8 100644
--- a/drivers/clk/clk-gpio.c
+++ b/drivers/clk/clk-gpio.c
@@ -280,7 +280,7 @@ static int gpio_clk_driver_probe(struct platform_device *pdev)
clk = clk_register_gpio_gate(&pdev->dev, node->name,
parent_names ? parent_names[0] : NULL, gpiod,
- 0);
if (IS_ERR(clk))
return PTR_ERR(clk);