From: Kukjin Kim <kgene.kim@samsung.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: Tushar Behera <tushar.behera@linaro.org>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
dianders@chromium.org, kgene.kim@samsung.com,
thomas.abraham@linaro.org, olofj@chromium.org,
patches@linaro.org
Subject: Re: [PATCH] clk: exynos5250: Fix parent clock for sclk_mmc{0,1,2,3}
Date: Wed, 24 Apr 2013 01:42:25 +0900 [thread overview]
Message-ID: <5176B9F1.3030300@samsung.com> (raw)
In-Reply-To: <20130423162349.17530.35976@quantum>
On 04/24/13 01:23, Mike Turquette wrote:
> Quoting Tushar Behera (2013-04-22 23:31:51)
>> 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@linaro.org>
>> CC: Doug Anderson<dianders@chromium.org>
>
> Change looks good to me.
>
+1
Olof, I think, you can pick this up in the arm-soc directly.
If you want:
Acked-by: Kukjin Kim <kgene.kim@samsung.com>
Thanks.
- Kukjin
>> ---
>> Doug,
>>
>> Would you please test whether this patch works for Snow?
>>
>>
>> drivers/clk/samsung/clk-exynos5250.c | 16 ++++++++--------
>> 1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/clk/samsung/clk-exynos5250.c b/drivers/clk/samsung/clk-exynos5250.c
>> index 7290faa..bb54606 100644
>> --- a/drivers/clk/samsung/clk-exynos5250.c
>> +++ b/drivers/clk/samsung/clk-exynos5250.c
>> @@ -276,10 +276,10 @@ struct samsung_div_clock exynos5250_div_clks[] __initdata = {
>> DIV(none, "div_pcm0", "sclk_audio0", DIV_MAU, 4, 8),
>> DIV(none, "div_sata", "mout_sata", DIV_FSYS0, 20, 4),
>> DIV(none, "div_usb3", "mout_usb3", DIV_FSYS0, 24, 4),
>> - DIV(none, "div_mmc0", "mout_mmc0", DIV_FSYS1, 8, 8),
>> - DIV(none, "div_mmc1", "mout_mmc1", DIV_FSYS1, 24, 8),
>> - DIV(none, "div_mmc2", "mout_mmc2", DIV_FSYS2, 8, 8),
>> - DIV(none, "div_mmc3", "mout_mmc3", DIV_FSYS2, 24, 8),
>> + DIV(none, "div_mmc0", "mout_mmc0", DIV_FSYS1, 0, 4),
>> + DIV(none, "div_mmc1", "mout_mmc1", DIV_FSYS1, 16, 4),
>> + DIV(none, "div_mmc2", "mout_mmc2", DIV_FSYS2, 0, 4),
>> + DIV(none, "div_mmc3", "mout_mmc3", DIV_FSYS2, 16, 4),
>> DIV(none, "div_uart0", "mout_uart0", DIV_PERIC0, 0, 4),
>> DIV(none, "div_uart1", "mout_uart1", DIV_PERIC0, 4, 4),
>> DIV(none, "div_uart2", "mout_uart2", DIV_PERIC0, 8, 4),
>> @@ -421,13 +421,13 @@ struct samsung_gate_clock exynos5250_gate_clks[] __initdata = {
>> SRC_MASK_DISP1_0, 20, 0, 0),
>> GATE(sclk_audio0, "sclk_audio0", "div_audio0",
>> SRC_MASK_MAU, 0, CLK_SET_RATE_PARENT, 0),
>> - GATE(sclk_mmc0, "sclk_mmc0", "div_mmc0",
>> + GATE(sclk_mmc0, "sclk_mmc0", "div_mmc_pre0",
>> SRC_MASK_FSYS, 0, CLK_SET_RATE_PARENT, 0),
>> - GATE(sclk_mmc1, "sclk_mmc1", "div_mmc1",
>> + GATE(sclk_mmc1, "sclk_mmc1", "div_mmc_pre1",
>> SRC_MASK_FSYS, 4, CLK_SET_RATE_PARENT, 0),
>> - GATE(sclk_mmc2, "sclk_mmc2", "div_mmc2",
>> + GATE(sclk_mmc2, "sclk_mmc2", "div_mmc_pre2",
>> SRC_MASK_FSYS, 8, CLK_SET_RATE_PARENT, 0),
>> - GATE(sclk_mmc3, "sclk_mmc3", "div_mmc3",
>> + GATE(sclk_mmc3, "sclk_mmc3", "div_mmc_pre3",
>> SRC_MASK_FSYS, 12, CLK_SET_RATE_PARENT, 0),
>> GATE(sclk_sata, "sclk_sata", "div_sata",
>> SRC_MASK_FSYS, 24, CLK_SET_RATE_PARENT, 0),
>> --
>> 1.7.9.5
next prev parent reply other threads:[~2013-04-23 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 8:20 [PATCH] clk: exynos5250: Fix divider values for sclk_mmc{0,1,2,3} Tushar Behera
2013-04-04 21:33 ` Mike Turquette
2013-04-08 7:22 ` Kukjin Kim
2013-04-16 19:35 ` Doug Anderson
2013-04-22 17:40 ` Olof Johansson
2013-04-23 2:52 ` Tushar Behera
2013-04-23 6:31 ` [PATCH] clk: exynos5250: Fix parent clock " Tushar Behera
2013-04-23 15:59 ` Doug Anderson
2013-04-23 16:23 ` Mike Turquette
2013-04-23 16:42 ` Kukjin Kim [this message]
2013-04-24 2:53 ` Olof Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5176B9F1.3030300@samsung.com \
--to=kgene.kim@samsung.com \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=olofj@chromium.org \
--cc=patches@linaro.org \
--cc=thomas.abraham@linaro.org \
--cc=tushar.behera@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.