From: Jaehoon Chung <jh80.chung@samsung.com>
To: Doug Anderson <dianders@chromium.org>,
Alim Akhtar <alim.akhtar@gmail.com>
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Sonny Rao <sonnyrao@chromium.org>,
Andrew Bresticker <abrestic@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
Addy Ke <addy.ke@rock-chips.com>,
Alexandru Stan <amstan@chromium.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Chris Zhong <zyw@rock-chips.com>,
Caesar Wang <wxt@rock-chips.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: dw_mmc: Wait for data transfer after response errors
Date: Wed, 27 May 2015 10:53:07 +0900 [thread overview]
Message-ID: <55652383.2020204@samsung.com> (raw)
In-Reply-To: <CAD=FV=WPKV78=Wx5qE43+LsVpx_X9KAfKvcXKWy2hZfDoRLi0w@mail.gmail.com>
Hi, All.
Thanks for your effort and sorry for late!
On 05/27/2015 05:44 AM, Doug Anderson wrote:
> Alim,
>
> On Tue, May 26, 2015 at 11:02 AM, Alim Akhtar <alim.akhtar@gmail.com> wrote:
>> Hi Doug,
>> On peach-pi, I got a hung task once in 4 cold boot as [1].
>
> OK, I'll have to get my peach-pi or peach-pit up and running again. I
> ran out of desk space and I haven't gotten it set back up. :(
>
> I've been testing on an rk3288-based device. Past experience has
> taught me that the rk3288 dw_mmc works differently than the exynos
> one, so perhaps this is a difference.
>
> Could you possibly patch in something like
> <https://chromium-review.googlesource.com/#/c/244347/> and provide the
> console for the failure? I'll put it on my list to try this myself,
> too
I don't test with this..but if needs, i will test.
It needs to fix the Alim's problem.
>
>
>> I was checking on v4.1-rc5, git hash as below:
>>
>> 862e58a mmc: dw_mmc: Wait for data transfer after response errors
>> ba155e2 Linux 4.1-rc5
>> 5b13966
>>
>> Not sure if I missed any dependent patch??
>
> I'm currently testing out of tree, but my dw_mmc is very close to mainline.
>
>
>> Have not checked the dw TRM for this change, will do that as soon as I
>> get access to it.
>
> OK, sounds good. I have some old version of the DesignWare TRM, so
> possibly something is different in the newer one...
Which version do you have? I also need to check the TRM version.
Best Regards,
Jaehoon Chung
>
>
> -Doug
>
next prev parent reply other threads:[~2015-05-27 1:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 15:53 [PATCH] mmc: dw_mmc: Wait for data transfer after response errors Doug Anderson
2015-05-26 18:02 ` Alim Akhtar
2015-05-26 20:44 ` Doug Anderson
2015-05-27 1:53 ` Jaehoon Chung [this message]
2015-05-27 16:52 ` Doug Anderson
-- strict thread matches above, loose matches on Subject: below --
2016-03-17 12:12 Enric Balletbo Serra
2016-03-21 22:38 ` Doug Anderson
2016-03-24 11:26 ` Enric Balletbo Serra
2016-03-24 15:16 ` Doug Anderson
2016-03-24 15:30 ` Russell King - ARM Linux
2016-03-24 16:06 ` Doug Anderson
2016-03-24 16:22 ` Russell King - ARM Linux
2016-03-30 17:16 ` Enric Balletbo Serra
2016-03-30 17:26 ` Russell King - ARM Linux
[not found] ` <CAFqH_51sMLbURO4n7OTEuC8S-6w0Q4aRv47nEoCAmK8-MJ+Jbw@mail.gmail.com>
2016-03-30 20:39 ` Russell King - ARM Linux
2016-03-31 1:56 ` Shawn Lin
2016-03-31 2:03 ` Jaehoon Chung
2016-03-31 6:39 ` Enric Balletbo Serra
2016-03-31 18:12 ` Doug Anderson
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=55652383.2020204@samsung.com \
--to=jh80.chung@samsung.com \
--cc=abrestic@chromium.org \
--cc=addy.ke@rock-chips.com \
--cc=alim.akhtar@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=amstan@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sonnyrao@chromium.org \
--cc=tgih.jun@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=wxt@rock-chips.com \
--cc=zyw@rock-chips.com \
/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.