| Message ID | 1431978219-14226-6-git-send-email-eric@anholt.net (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On 05/18/2015 01:43 PM, Eric Anholt wrote:
> Nothing uses it, and I can't find any evidence that anything ever has.
Does the clock actually exist though? If it does, it seems reasonable to
keep it.
Stephen Warren <swarren@wwwdotorg.org> writes: > On 05/18/2015 01:43 PM, Eric Anholt wrote: >> Nothing uses it, and I can't find any evidence that anything ever has. > > Does the clock actually exist though? If it does, it seems reasonable to > keep it. Yes, it's kept in the form of the core clock in the RPi driver, and the clock-frequency values in spi and i2c in bcm2835.dtsi.
diff --git a/drivers/clk/clk-bcm2835.c b/drivers/clk/clk-bcm2835.c index 6b950ca..dd295e4 100644 --- a/drivers/clk/clk-bcm2835.c +++ b/drivers/clk/clk-bcm2835.c @@ -32,11 +32,6 @@ void __init bcm2835_init_clocks(void) struct clk *clk; int ret; - clk = clk_register_fixed_rate(NULL, "sys_pclk", NULL, CLK_IS_ROOT, - 250000000); - if (IS_ERR(clk)) - pr_err("sys_pclk not registered\n"); - clk = clk_register_fixed_rate(NULL, "apb_pclk", NULL, CLK_IS_ROOT, 126000000); if (IS_ERR(clk))
Nothing uses it, and I can't find any evidence that anything ever has. Signed-off-by: Eric Anholt <eric@anholt.net> --- drivers/clk/clk-bcm2835.c | 5 ----- 1 file changed, 5 deletions(-)