From: Chris Ball <cjb@laptop.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Heiko Stübner" <heiko@sntech.de>
Subject: Re: [PATCH v2 1/4] mmc: sdhci-s3c: fix the wrong register value, when clock is disabled
Date: Thu, 29 Aug 2013 21:18:41 -0400 [thread overview]
Message-ID: <87a9k0x9fy.fsf@octavius.laptop.org> (raw)
In-Reply-To: <51FBBD7A.4050501@samsung.com> (Jaehoon Chung's message of "Fri, 02 Aug 2013 23:08:58 +0900")
Hi Jaehoon,
On Fri, Aug 02 2013, Jaehoon Chung wrote:
> When use the QUIRK_NONSTANDARD_CLOCK, then never set to 0 at clock control register.
> This patch is fixed this problem.
> ([PATCHv2] mmc: sdhci-s3c: fix teh wrong register value, when clock is disabled)
>
> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> Changelog v2:
> - modified the comment
>
> drivers/mmc/host/sdhci-s3c.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci-s3c.c b/drivers/mmc/host/sdhci-s3c.c
> index 926aaf6..1572b6a 100644
> --- a/drivers/mmc/host/sdhci-s3c.c
> +++ b/drivers/mmc/host/sdhci-s3c.c
> @@ -296,9 +296,12 @@ static void sdhci_cmu_set_clock(struct sdhci_host *host, unsigned int clock)
> unsigned long timeout;
> u16 clk = 0;
>
> - /* don't bother if the clock is going off */
> - if (clock == 0)
> + /* If the clock is going off, set to 0 at clock control register */
> + if (clock == 0) {
> + sdhci_writew(host, 0, SDHCI_CLOCK_CONTROL);
> + host->clock = clock;
> return;
> + }
>
> sdhci_s3c_set_clock(host, clock);
Thanks, pushed to mmc-next for 3.12.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
prev parent reply other threads:[~2013-08-30 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 14:08 [PATCH v2 1/4] mmc: sdhci-s3c: fix the wrong register value, when clock is disabled Jaehoon Chung
2013-08-30 1:18 ` Chris Ball [this message]
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=87a9k0x9fy.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=heiko@sntech.de \
--cc=jh80.chung@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@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