From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> To: Jisheng Zhang <jszhang@marvell.com> Cc: "mturquette@linaro.org" <mturquette@linaro.org>, "sboyd@codeaurora.org" <sboyd@codeaurora.org>, "alexandre.belloni@free-electrons.com" <alexandre.belloni@free-electrons.com>, "antoine.tenart@free-electrons.com" <antoine.tenart@free-electrons.com>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "pawel.moll@arm.com" <pawel.moll@arm.com>, "mark.rutland@arm.com" <mark.rutland@arm.com>, "ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>, "galak@codeaurora.org" <galak@codeaurora.org>, "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "stable@vger.kernel.org" <stable@vger.kernel.org> Subject: Re: [PATCH 3/3] clk: berlin: bg2q: remove non-exist "smemc" gate clock Date: Sat, 10 Jan 2015 14:08:22 +0100 [thread overview] Message-ID: <54B12446.4030703@gmail.com> (raw) In-Reply-To: <20150109201306.4d1a296b@xhacker> On 09.01.2015 13:13, Jisheng Zhang wrote: > On Wed, 7 Jan 2015 06:30:55 -0800 > Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote: >> On 07.01.2015 15:22, Jisheng Zhang wrote: >>> On Wed, 7 Jan 2015 06:11:58 -0800 >>> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote: >>>> On 31.12.2014 09:57, Jisheng Zhang wrote: >>>>> The "smemc" clock is removed on BG2Q SoCs. In fact, bit19 of clkenable >>>>> register is for nfc. Current code use bit19 for non-exist "smemc" >>>>> incorrectly, this prevents eMMC from working due to the sdhci's >>>>> "core" clk is still gated. >>>>> >>>>> Signed-off-by: Jisheng Zhang <jszhang@marvell.com> >>>>> Cc: stable@vger.kernel.org # 3.16+ >>>>> --- >>>>> drivers/clk/berlin/bg2q.c | 1 - >>>>> 1 file changed, 1 deletion(-) >>>>> >>>>> diff --git a/drivers/clk/berlin/bg2q.c b/drivers/clk/berlin/bg2q.c >>>>> index 21784e4..440ef81 100644 >>>>> --- a/drivers/clk/berlin/bg2q.c >>>>> +++ b/drivers/clk/berlin/bg2q.c >>>>> @@ -285,7 +285,6 @@ static const struct berlin2_gate_data bg2q_gates[] >>>>> __initconst = { { "pbridge", "perif", 15, >>>>> CLK_IGNORE_UNUSED }, { "sdio", "perif", 16, >>>>> CLK_IGNORE_UNUSED }, { "nfc", "perif", 18 }, >>> >>> The nfc here is really confusing, we call it as nfccore internally. Is it >>> better to rename it as nfccore? >> >> I guess it comes from some early Marvell BSP code, if there is no >> issues with the name, e.g. something already depends on "nfc", feel >> free to rename it to something more meaningful. > > In BG2, mrvl call the clock as nfccore. The code use "nfc" for it. > The situation is similar for usbcore, satacore etc. So keep the name here, > what do you think? Yes, I am fine with keeping the name as is. >>>>> - { "smemc", "perif", 19 }, >>>> >>>> if bit 19 is for nfc, how does that work out with bit 18 which is >>>> still assigned to nfc? Can you re-evaluate clkenable registers for >>> >>> bit 19 is for nfcEcc, the "io" clock; bit 18 is for nfcCore, the "core" >>> clock. >> >> Ok, then both bits should be dealt with accordingly, i.e. rename >> "smemc" to "nfcecc" and use it in the corresponding dts node. >> >> If this clk_gate just disables a clock that is fed into another >> gateable clock module, I can live with removing it - although I >> still think it is best to leave the clk_gate in place and pick >> another name that does not collide with any other clock name. > > The nfcecc is already defined in the bg2q_divs, the gate bit is correct there. Ok, I had a look in the actual code and agree that the same bit 19 is used twice. The patch is fine and we can take it as is. This is clk subsystem, so either Mike takes it through his fixes branch including my Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> or decides to agree that I take it instead with his Ack. I am fine with both. Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 3/3] clk: berlin: bg2q: remove non-exist "smemc" gate clock Date: Sat, 10 Jan 2015 14:08:22 +0100 [thread overview] Message-ID: <54B12446.4030703@gmail.com> (raw) In-Reply-To: <20150109201306.4d1a296b@xhacker> On 09.01.2015 13:13, Jisheng Zhang wrote: > On Wed, 7 Jan 2015 06:30:55 -0800 > Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote: >> On 07.01.2015 15:22, Jisheng Zhang wrote: >>> On Wed, 7 Jan 2015 06:11:58 -0800 >>> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote: >>>> On 31.12.2014 09:57, Jisheng Zhang wrote: >>>>> The "smemc" clock is removed on BG2Q SoCs. In fact, bit19 of clkenable >>>>> register is for nfc. Current code use bit19 for non-exist "smemc" >>>>> incorrectly, this prevents eMMC from working due to the sdhci's >>>>> "core" clk is still gated. >>>>> >>>>> Signed-off-by: Jisheng Zhang <jszhang@marvell.com> >>>>> Cc: stable at vger.kernel.org # 3.16+ >>>>> --- >>>>> drivers/clk/berlin/bg2q.c | 1 - >>>>> 1 file changed, 1 deletion(-) >>>>> >>>>> diff --git a/drivers/clk/berlin/bg2q.c b/drivers/clk/berlin/bg2q.c >>>>> index 21784e4..440ef81 100644 >>>>> --- a/drivers/clk/berlin/bg2q.c >>>>> +++ b/drivers/clk/berlin/bg2q.c >>>>> @@ -285,7 +285,6 @@ static const struct berlin2_gate_data bg2q_gates[] >>>>> __initconst = { { "pbridge", "perif", 15, >>>>> CLK_IGNORE_UNUSED }, { "sdio", "perif", 16, >>>>> CLK_IGNORE_UNUSED }, { "nfc", "perif", 18 }, >>> >>> The nfc here is really confusing, we call it as nfccore internally. Is it >>> better to rename it as nfccore? >> >> I guess it comes from some early Marvell BSP code, if there is no >> issues with the name, e.g. something already depends on "nfc", feel >> free to rename it to something more meaningful. > > In BG2, mrvl call the clock as nfccore. The code use "nfc" for it. > The situation is similar for usbcore, satacore etc. So keep the name here, > what do you think? Yes, I am fine with keeping the name as is. >>>>> - { "smemc", "perif", 19 }, >>>> >>>> if bit 19 is for nfc, how does that work out with bit 18 which is >>>> still assigned to nfc? Can you re-evaluate clkenable registers for >>> >>> bit 19 is for nfcEcc, the "io" clock; bit 18 is for nfcCore, the "core" >>> clock. >> >> Ok, then both bits should be dealt with accordingly, i.e. rename >> "smemc" to "nfcecc" and use it in the corresponding dts node. >> >> If this clk_gate just disables a clock that is fed into another >> gateable clock module, I can live with removing it - although I >> still think it is best to leave the clk_gate in place and pick >> another name that does not collide with any other clock name. > > The nfcecc is already defined in the bg2q_divs, the gate bit is correct there. Ok, I had a look in the actual code and agree that the same bit 19 is used twice. The patch is fine and we can take it as is. This is clk subsystem, so either Mike takes it through his fixes branch including my Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> or decides to agree that I take it instead with his Ack. I am fine with both. Sebastian
next prev parent reply other threads:[~2015-01-10 13:08 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-31 8:57 [PATCH 0/3] fix non-working eMMC on Marvell BG2Q DMP board Jisheng Zhang 2014-12-31 8:57 ` Jisheng Zhang 2014-12-31 8:57 ` Jisheng Zhang 2014-12-31 8:57 ` [PATCH 1/3] ARM: dts: berlin: fix io clk and add missing core clk for BG2Q sdhci2 host Jisheng Zhang 2014-12-31 8:57 ` Jisheng Zhang 2014-12-31 8:57 ` Jisheng Zhang 2015-01-07 14:22 ` Sebastian Hesselbarth 2015-01-07 14:22 ` Sebastian Hesselbarth 2015-01-07 14:22 ` Sebastian Hesselbarth 2014-12-31 8:57 ` [PATCH 2/3] ARM: berlin: add broken-cd and set bus width for eMMC in Marvell DMP DT Jisheng Zhang 2014-12-31 8:57 ` Jisheng Zhang 2014-12-31 8:57 ` Jisheng Zhang 2015-01-07 14:22 ` Sebastian Hesselbarth 2015-01-07 14:22 ` Sebastian Hesselbarth 2014-12-31 8:57 ` [PATCH 3/3] clk: berlin: bg2q: remove non-exist "smemc" gate clock Jisheng Zhang 2014-12-31 8:57 ` Jisheng Zhang 2014-12-31 8:57 ` Jisheng Zhang 2015-01-07 14:11 ` Sebastian Hesselbarth 2015-01-07 14:11 ` Sebastian Hesselbarth 2015-01-07 14:22 ` Jisheng Zhang 2015-01-07 14:22 ` Jisheng Zhang 2015-01-07 14:22 ` Jisheng Zhang 2015-01-07 14:22 ` Jisheng Zhang 2015-01-07 14:30 ` Sebastian Hesselbarth 2015-01-07 14:30 ` Sebastian Hesselbarth 2015-01-07 14:30 ` Sebastian Hesselbarth 2015-01-09 12:13 ` Jisheng Zhang 2015-01-09 12:13 ` Jisheng Zhang 2015-01-09 12:13 ` Jisheng Zhang 2015-01-09 12:13 ` Jisheng Zhang 2015-01-10 13:08 ` Sebastian Hesselbarth [this message] 2015-01-10 13:08 ` Sebastian Hesselbarth 2015-01-10 13:08 ` Sebastian Hesselbarth 2015-01-13 0:28 ` Mike Turquette 2015-01-13 0:28 ` Mike Turquette 2015-01-13 0:28 ` Mike Turquette 2015-01-13 12:17 ` Sebastian Hesselbarth 2015-01-13 12:17 ` Sebastian Hesselbarth 2015-01-13 12:17 ` Sebastian Hesselbarth 2015-01-13 19:27 ` Mike Turquette 2015-01-13 19:27 ` Mike Turquette 2015-01-13 19:27 ` Mike Turquette
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=54B12446.4030703@gmail.com \ --to=sebastian.hesselbarth@gmail.com \ --cc=alexandre.belloni@free-electrons.com \ --cc=antoine.tenart@free-electrons.com \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=ijc+devicetree@hellion.org.uk \ --cc=jszhang@marvell.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=mark.rutland@arm.com \ --cc=mturquette@linaro.org \ --cc=pawel.moll@arm.com \ --cc=robh+dt@kernel.org \ --cc=sboyd@codeaurora.org \ --cc=stable@vger.kernel.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: linkBe 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.