[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=WPKV78=Wx5qE43+LsVpx_X9KAfKvcXKWy2hZfDoRLi0w@mail.gmail.com>
Date: Tue, 26 May 2015 13:44:33 -0700
From: Doug Anderson <dianders@...omium.org>
To: Alim Akhtar <alim.akhtar@...il.com>
Cc: Jaehoon Chung <jh80.chung@...sung.com>,
Seungwon Jeon <tgih.jun@...sung.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Sonny Rao <sonnyrao@...omium.org>,
Andrew Bresticker <abrestic@...omium.org>,
Heiko Stuebner <heiko@...ech.de>,
Addy Ke <addy.ke@...k-chips.com>,
Alexandru Stan <amstan@...omium.org>,
Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
Chris Zhong <zyw@...k-chips.com>,
Caesar Wang <wxt@...k-chips.com>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mmc: dw_mmc: Wait for data transfer after response errors
Alim,
On Tue, May 26, 2015 at 11:02 AM, Alim Akhtar <alim.akhtar@...il.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 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...
-Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists