From: Shawn Guo <shawn.guo@linaro.org>
To: Alim Akhtar <alim.akhtar@gmail.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Seungwon Jeon <tgih.jun@samsung.com>,
Chris Ball <chris@printf.net>,
stable@vger.kernel.org, Jaehoon Chung <jh80.chung@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] mmc: dw_mmc: fix card read threshold for PIO mode
Date: Mon, 24 Nov 2014 08:25:09 +0800 [thread overview]
Message-ID: <20141124002508.GI11253@dragon> (raw)
In-Reply-To: <CAGOxZ50+k3Z5gHrRasveM=7V+GS+1dRmcz0u5WSyo=XBE9iT3g@mail.gmail.com>
On Mon, Nov 24, 2014 at 03:36:13AM +0530, Alim Akhtar wrote:
> Hi Shawn,
>
> On Sun, Nov 23, 2014 at 9:00 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > One thing I need to check with hardware vendor is whether register
> > CDTHRCTL is available on my dwmmc controller. From my testing, even
> > reading this register every time dw_mci_submit_data() is called causes
> > problem for me.
> >
> yes, your guess is right, did you tested with ulf's -next branch?
> Recently patch [1] is merged, that most likely to solve your platform
> issue. Have a try.
>
> [1] http://www.spinics.net/lists/stable/msg69884.html
Yeah, the patch fixes my problem. Thanks a lot for the pointer, Alim.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: dw_mmc: fix card read threshold for PIO mode
Date: Mon, 24 Nov 2014 08:25:09 +0800 [thread overview]
Message-ID: <20141124002508.GI11253@dragon> (raw)
In-Reply-To: <CAGOxZ50+k3Z5gHrRasveM=7V+GS+1dRmcz0u5WSyo=XBE9iT3g@mail.gmail.com>
On Mon, Nov 24, 2014 at 03:36:13AM +0530, Alim Akhtar wrote:
> Hi Shawn,
>
> On Sun, Nov 23, 2014 at 9:00 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > One thing I need to check with hardware vendor is whether register
> > CDTHRCTL is available on my dwmmc controller. From my testing, even
> > reading this register every time dw_mci_submit_data() is called causes
> > problem for me.
> >
> yes, your guess is right, did you tested with ulf's -next branch?
> Recently patch [1] is merged, that most likely to solve your platform
> issue. Have a try.
>
> [1] http://www.spinics.net/lists/stable/msg69884.html
Yeah, the patch fixes my problem. Thanks a lot for the pointer, Alim.
Shawn
next prev parent reply other threads:[~2014-11-24 0:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 6:39 [PATCH] mmc: dw_mmc: fix card read threshold for PIO mode Shawn Guo
2014-11-21 6:39 ` Shawn Guo
2014-11-21 10:30 ` Jaehoon Chung
2014-11-21 10:30 ` Jaehoon Chung
2014-11-21 11:48 ` Shawn Guo
2014-11-21 11:48 ` Shawn Guo
2014-11-21 13:03 ` Shawn Guo
2014-11-21 13:03 ` Shawn Guo
2014-11-21 23:31 ` Shawn Guo
2014-11-21 23:31 ` Shawn Guo
2014-11-22 13:26 ` Alim Akhtar
2014-11-22 13:26 ` Alim Akhtar
2014-11-23 15:30 ` Shawn Guo
2014-11-23 15:30 ` Shawn Guo
2014-11-23 22:06 ` Alim Akhtar
2014-11-23 22:06 ` Alim Akhtar
2014-11-24 0:25 ` Shawn Guo [this message]
2014-11-24 0:25 ` Shawn Guo
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=20141124002508.GI11253@dragon \
--to=shawn.guo@linaro.org \
--cc=alim.akhtar@gmail.com \
--cc=chris@printf.net \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tgih.jun@samsung.com \
--cc=ulf.hansson@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 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.