Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754164AbbBNOzP (ORCPT ); Sat, 14 Feb 2015 09:55:15 -0500 Received: from smtp03.smtpout.orange.fr ([80.12.242.125]:59056 "EHLO smtp.smtpout.orange.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754111AbbBNOzN (ORCPT ); Sat, 14 Feb 2015 09:55:13 -0500 X-ME-Helo: beldin.home X-ME-Date: Sat, 14 Feb 2015 15:55:10 +0100 X-ME-IP: 109.220.218.8 From: Robert Jarzmik To: Mike Turquette , Stephen Boyd Cc: linux-kernel@vger.kernel.org, Robert Jarzmik Subject: [PATCH] clk: pxa: pxa3xx: add missing os timer clock Date: Sat, 14 Feb 2015 15:54:58 +0100 Message-Id: <1423925698-18449-1-git-send-email-robert.jarzmik@free.fr> X-Mailer: git-send-email 2.1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1292 Lines: 35 The pxa3xx scheduler relies on the pxa-timer, which requires a clock for its rate. As the clock handling will be taken over by the clock framework, add this missing clock. The miss was discovered by attempting to run a zylonite platform in a device-tree configuration, with the future patch to shift clocks handling to clock framework applied. Signed-off-by: Robert Jarzmik --- drivers/clk/pxa/clk-pxa3xx.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/clk/pxa/clk-pxa3xx.c b/drivers/clk/pxa/clk-pxa3xx.c index 39f891b..4b93a1e 100644 --- a/drivers/clk/pxa/clk-pxa3xx.c +++ b/drivers/clk/pxa/clk-pxa3xx.c @@ -336,6 +336,9 @@ static void __init pxa3xx_base_clocks_init(void) clk_register_clk_pxa3xx_smemc(); clk_register_gate(NULL, "CLK_POUT", "osc_13mhz", 0, (void __iomem *)&OSCC, 11, 0, NULL); + clkdev_pxa_register(CLK_OSTIMER, "OSTIMER0", NULL, + clk_register_fixed_factor(NULL, "os-timer0", + "osc_13mhz", 0, 1, 4)); } int __init pxa3xx_clocks_init(void) -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/