From: Alim Akhtar <alim.akhtar@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-samsung-soc@vger.kernel.org
Cc: s.nawrocki@samsung.com, tomasz.figa@gmail.com, kgene@kernel.org,
mturquette@baylibre.com, amit.daniel@samsung.com,
gautam.vivek@samsung.com, sboyd@codeaurora.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 04/11] clk: samsung: exynos7: Corrects CMU_CCORE clocks names
Date: Tue, 08 Sep 2015 18:48:22 +0530 [thread overview]
Message-ID: <55EEE01E.5040502@samsung.com> (raw)
In-Reply-To: <55EE8E82.8080800@samsung.com>
Hello,
On 09/08/2015 01:00 PM, Krzysztof Kozlowski wrote:
> On 04.09.2015 20:37, Alim Akhtar wrote:
>> This patch rename CMU_CCROE clocks names to match with user manual.
>
> s/rename/renames/ (everywhere...)
> s/CCROE/CCORE/
>
>
>> And also adds missing gate clock for aclk_ccore_133.
>>
>> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
>> ---
>> drivers/clk/samsung/clk-exynos7.c | 8 ++++++--
>> include/dt-bindings/clock/exynos7-clk.h | 3 ++-
>> 2 files changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/clk/samsung/clk-exynos7.c b/drivers/clk/samsung/clk-exynos7.c
>> index ba84e9b..0eb0f57 100644
>> --- a/drivers/clk/samsung/clk-exynos7.c
>> +++ b/drivers/clk/samsung/clk-exynos7.c
>> @@ -31,6 +31,7 @@
>> #define MUX_SEL_TOPC1 0x0204
>> #define MUX_SEL_TOPC2 0x0208
>> #define MUX_SEL_TOPC3 0x020C
>> +#define MUX_ENABLE_TOPC2 0x0308
>> #define DIV_TOPC0 0x0600
>> #define DIV_TOPC1 0x0604
>> #define DIV_TOPC3 0x060C
>> @@ -167,6 +168,9 @@ static struct samsung_gate_clock topc_gate_clks[] __initdata = {
>> ENABLE_SCLK_TOPC1, 1, 0, 0),
>> GATE(SCLK_CC_PLL_A, "sclk_cc_pll_a", "dout_sclk_cc_pll",
>> ENABLE_SCLK_TOPC1, 0, 0, 0),
>> +
>> + GATE(ACLK_CCORE_133, "aclk_ccore_133", "dout_aclk_ccore_133",
>> + MUX_ENABLE_TOPC2, 4, 0, 0),
>
> Hmmm... Shouldn't this be CLK_ENABLE_ACLK_TOPC0 register? For other
> similar clock configurations (e.g. SCLK_I2S1) the gate at the end is
> controlled, not the mux parent.
Good catch, will re-spin, as suggested by you, will separate adding Gate
and renaming clock names.
>
> Best regards,
> Krzysztof
>
>> };
>>
>> static struct samsung_pll_clock topc_pll_clks[] __initdata = {
>> @@ -544,7 +548,7 @@ CLK_OF_DECLARE(exynos7_clk_top1, "samsung,exynos7-clock-top1",
>> /*
>> * List of parent clocks for Muxes in CMU_CCORE
>> */
>> -PNAME(mout_aclk_ccore_133_p) = { "fin_pll", "dout_aclk_ccore_133" };
>> +PNAME(mout_aclk_ccore_133_user_p) = { "fin_pll", "aclk_ccore_133" };
>>
>> static unsigned long ccore_clk_regs[] __initdata = {
>> MUX_SEL_CCORE,
>> @@ -552,7 +556,7 @@ static unsigned long ccore_clk_regs[] __initdata = {
>> };
>>
>> static struct samsung_mux_clock ccore_mux_clks[] __initdata = {
>> - MUX(0, "mout_aclk_ccore_133_user", mout_aclk_ccore_133_p,
>> + MUX(0, "mout_aclk_ccore_133_user", mout_aclk_ccore_133_user_p,
>> MUX_SEL_CCORE, 1, 1),
>> };
>>
>> diff --git a/include/dt-bindings/clock/exynos7-clk.h b/include/dt-bindings/clock/exynos7-clk.h
>> index b63eba6..2e01235 100644
>> --- a/include/dt-bindings/clock/exynos7-clk.h
>> +++ b/include/dt-bindings/clock/exynos7-clk.h
>> @@ -30,7 +30,8 @@
>> #define SCLK_BUS0_PLL_A 17
>> #define SCLK_CC_PLL_B 18
>> #define SCLK_CC_PLL_A 19
>> -#define TOPC_NR_CLK 20
>> +#define ACLK_CCORE_133 20
>> +#define TOPC_NR_CLK 21
>>
>> /* TOP0 */
>> #define DOUT_ACLK_PERIC1 1
>>
>
>
next prev parent reply other threads:[~2015-09-08 13:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 11:37 [PATCH 00/11] clk: samsung: exynos7: Cleanup of clock file Alim Akhtar
2015-09-04 11:37 ` [PATCH 01/11] clk: samsung: exynos7: Change the CMU_TOPC block clock name Alim Akhtar
2015-09-07 5:33 ` Krzysztof Kozlowski
2015-09-07 7:26 ` Alim Akhtar
2015-09-07 7:39 ` Krzysztof Kozlowski
2015-09-04 11:37 ` [PATCH 02/11] clk: samsung: exynos7: Corrects CMU_TOP0 clocks names Alim Akhtar
2015-09-08 7:12 ` Krzysztof Kozlowski
2015-09-04 11:37 ` [PATCH 03/11] clk: samsung: exynos7: Corrects CMU_TOP1 " Alim Akhtar
2015-09-04 11:37 ` [PATCH 04/11] clk: samsung: exynos7: Corrects CMU_CCORE " Alim Akhtar
2015-09-08 7:30 ` Krzysztof Kozlowski
2015-09-08 13:18 ` Alim Akhtar [this message]
2015-09-04 11:37 ` [PATCH 05/11] clk: samsung: exynos7: Corrects CMU_PERIC0 " Alim Akhtar
2015-09-10 4:01 ` Krzysztof Kozlowski
2015-09-04 11:37 ` [PATCH 06/11] clk: samsung: exynos7: Corrects CMU_PERIC1 " Alim Akhtar
2015-09-10 4:01 ` Krzysztof Kozlowski
2015-09-04 11:37 ` [PATCH 07/11] clk: samsung: exynos7: Corrects CMU_PERIS " Alim Akhtar
2015-09-10 4:02 ` Krzysztof Kozlowski
2015-09-04 11:37 ` [PATCH 08/11] clk: samsung: exynos7: Corrects CMU_FSYS0 " Alim Akhtar
2015-09-10 4:04 ` Krzysztof Kozlowski
2015-09-04 11:37 ` [PATCH 09/11] clk: samsung: exynos7: Corrects CMU_FSYS1 " Alim Akhtar
2015-09-10 4:05 ` Krzysztof Kozlowski
2015-09-04 11:37 ` [PATCH 10/11] clk: samsung: exynos7: Add missing fixed_clks to cmu_info Alim Akhtar
2015-09-10 4:05 ` Krzysztof Kozlowski
2015-09-04 11:37 ` [PATCH 11/11] clk: samsung: exynos7: Add required clock tree for UFS Alim Akhtar
2015-09-10 4:08 ` Krzysztof Kozlowski
2015-09-10 8:53 ` Alim Akhtar
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=55EEE01E.5040502@samsung.com \
--to=alim.akhtar@samsung.com \
--cc=amit.daniel@samsung.com \
--cc=gautam.vivek@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@codeaurora.org \
--cc=tomasz.figa@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox