From: Jisheng Zhang <jszhang@marvell.com>
To: sebastian.hesselbarth@gmail.com, mturquette@linaro.org,
sboyd@codeaurora.org, alexandre.belloni@free-electrons.com,
antoine.tenart@free-electrons.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Jisheng Zhang <jszhang@marvell.com>
Subject: [PATCH 3/3] clk: berlin: bg2q: remove non-exist "smemc" gate clock
Date: Wed, 31 Dec 2014 16:57:52 +0800 [thread overview]
Message-ID: <1420016272-6789-4-git-send-email-jszhang@marvell.com> (raw)
In-Reply-To: <1420016272-6789-1-git-send-email-jszhang@marvell.com>
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 },
- { "smemc", "perif", 19 },
{ "pcie", "perif", 22 },
};
--
2.1.4
next prev parent reply other threads:[~2014-12-31 8:57 UTC|newest]
Thread overview: 14+ 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
[not found] ` <1420016272-6789-1-git-send-email-jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
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
[not found] ` <1420016272-6789-2-git-send-email-jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
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
2015-01-07 14:22 ` Sebastian Hesselbarth
2014-12-31 8:57 ` Jisheng Zhang [this message]
2015-01-07 14:11 ` [PATCH 3/3] clk: berlin: bg2q: remove non-exist "smemc" gate clock Sebastian Hesselbarth
[not found] ` <54AD3EAE.6090009-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-07 14:22 ` Jisheng Zhang
2015-01-07 14:30 ` Sebastian Hesselbarth
[not found] ` <54AD431F.6060403-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-09 12:13 ` Jisheng Zhang
2015-01-10 13:08 ` Sebastian Hesselbarth
2015-01-13 0:28 ` Mike Turquette
2015-01-13 12:17 ` Sebastian Hesselbarth
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=1420016272-6789-4-git-send-email-jszhang@marvell.com \
--to=jszhang@marvell.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=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=sebastian.hesselbarth@gmail.com \
--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: 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;
as well as URLs for NNTP newsgroup(s).