From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Mike Turquette'" <mturquette@linaro.org>,
"'Tushar Behera'" <tushar.behera@linaro.org>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: patches@linaro.org, "'Thomas Abraham'" <thomas.abraham@linaro.org>
Subject: RE: [PATCH] clk: exynos5250: Fix divider values for sclk_mmc{0,1,2,3}
Date: Mon, 08 Apr 2013 16:22:58 +0900 [thread overview]
Message-ID: <2c9001ce3429$e5989a50$b0c9cef0$%kim@samsung.com> (raw)
In-Reply-To: <20130404213331.8665.7028@quantum>
Mike Turquette wrote:
>
> Quoting Tushar Behera (2013-04-02 01:20:40)
> > In legacy setup, sclk_mmc{0,1,2,3} used PRE_RATIO bit-field (8-bit wide)
> > instead of RATIO bit-field (4-bit wide) for dividing clock rate.
> >
> > With current common clock setup, we are using RATIO bit-field which
> > is creating FIFO read errors while accessing eMMC. Changing over to
> > use PRE_RATIO bit-field fixes this issue.
> >
> > dwmmc_exynos 12200000.dwmmc0: data FIFO error (status=00008020)
> > mmcblk0: error -5 transferring data, sector 1, nr 7, cmd response 0x900,
> card status 0x0
> > end_request: I/O error, dev mmcblk0, sector 1
> >
> > Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
> > CC: Thomas Abraham <thomas.abraham@linaro.org>
>
> I guess this will be applied through the samsung tree, so:
>
> Acked-by: Mike Turquette <mturquette@linaro.org>
>
Thanks, applied.
- Kukjin
next prev parent reply other threads:[~2013-04-08 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 8:20 Tushar Behera
2013-04-04 21:33 ` Mike Turquette
2013-04-08 7:22 ` Kukjin Kim [this message]
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
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='2c9001ce3429$e5989a50$b0c9cef0$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®