[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130424025326.GA10479@quad.lixom.net>
Date: Tue, 23 Apr 2013 19:53:26 -0700
From: Olof Johansson <olof@...om.net>
To: Tushar Behera <tushar.behera@...aro.org>
Cc: linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
dianders@...omium.org, kgene.kim@...sung.com,
mturquette@...aro.org, thomas.abraham@...aro.org,
olofj@...omium.org, patches@...aro.org
Subject: Re: [PATCH] clk: exynos5250: Fix parent clock for sclk_mmc{0,1,2,3}
On Tue, Apr 23, 2013 at 12:01:51PM +0530, Tushar Behera wrote:
> commit 688f7d8c9fef ("clk: exynos5250: Fix divider values for
> sclk_mmc{0,1,2,3}") incorrectly sets the divider for sclk_mmc{0,1,2,3}
> to fix the wrong clock value. Though this fixed issue with Arndale,
> it created regressions for other boards like Snow.
>
> On Exynos5250, sclk_mmc<n> is generated like below (as per the clock
> names in drivers/clk/samsung/clk-exynos5250.c)
>
> mout_group1_p ==> mout_mmc<n> ==>
> div_mmc<n> ==> div_mmc_pre<n> => sclk_mmc<n>
>
> Earlier div_mmc<n> was set as the parent for sclk_mmc<n>, hence
> div_mmc_pre<n> was not getting referred in kernel code and depending
> on its value set during preboot, sclk_mmc<n> value was different for
> various boards.
>
> Setting the correct clock generation path should fix the issues
> reported in above referenced commit. The changes committed during the
> earlier patch has also been reverted here.
>
> Signed-off-by: Tushar Behera <tushar.behera@...aro.org>
> CC: Doug Anderson <dianders@...omium.org>
> ---
> Doug,
>
> Would you please test whether this patch works for Snow?
Applied to next/drivers in arm-soc.git.
-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists