[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=XCSTzX04M1TDCf9p4QqZrNsStTKG5s7uYbJNaAKmtkuw@mail.gmail.com>
Date: Wed, 13 Aug 2014 06:38:27 -0700
From: Doug Anderson <dianders@...omium.org>
To: Seungwon Jeon <tgih.jun@...sung.com>,
Ulf Hansson <ulf.hansson@...aro.org>
Cc: Jaehoon Chung <jh80.chung@...sung.com>,
Chris Ball <cjb@...top.org>, Sonny Rao <sonnyrao@...omium.org>,
Grant Grundler <grundler@...omium.org>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
Kukjin Kim <kgene.kim@...sung.com>,
sunil joshi <joshi@...sung.com>,
Tomasz Figa <t.figa@...sung.com>,
Yuvaraj Kumar C D <yuvaraj.cd@...il.com>,
Chris Ball <chris@...ntf.net>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] mmc: dw_mmc: Make sure we don't get stuck when we get
an error
Hi,
On Wed, May 21, 2014 at 2:08 AM, Seungwon Jeon <tgih.jun@...sung.com> wrote:
> On Wed, May 21, 2014, Doug Anderson wrote:
>> If we happened to get a data error at just the wrong time the dw_mmc
>> driver could get into a state where it would never complete its
>> request. That would leave the caller just hanging there.
>>
>> We fix this two ways and both of the two fixes on their own appear to
>> fix the problems we've seen:
>>
>> 1. Fix a race in the tasklet where the interrupt setting the data
>> error happens _just after_ we check for it, then we get a
>> EVENT_XFER_COMPLETE. We fix this by repeating a bit of code.
>> 2. Fix it so that if we detect that we've got an error in the "data
>> busy" state and we're not going to do anything else we end the
>> request and unblock anyone waiting.
>>
>> Signed-off-by: Doug Anderson <dianders@...omium.org>
>> Signed-off-by: Yuvaraj Kumar C D <yuvaraj.cd@...il.com>
>
> It will be applied after "mmc: dw_mmc: change to use recommended reset procedure"
>
> Acked-by: Seungwon Jeon <tgih.jun@...sung.com>
>
> Thanks,
> Seungwon Jeon
I saw that Ulf applied "mmc: dw_mmc: change to use recommended reset
procedure". Could we apply this one now, too? Do you want me to
repost?
-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