From: tgih.jun@samsung.com (Seungwon Jeon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: dw_mmc: Make sure we don't get stuck when we get an error
Date: Wed, 21 May 2014 18:05:33 +0900 [thread overview]
Message-ID: <000f01cf74d3$d2938b40$77baa1c0$%jun@samsung.com> (raw)
In-Reply-To: <CAD=FV=Vtpup1DaAnN1cO4R5CgxMKa0aosw53sj1eKcUPJsEoYg@mail.gmail.com>
On Wed, May 21, 2014, Doug Anderson wrote:
> Seungwon,
>
> On Mon, May 19, 2014 at 6:51 PM, Seungwon Jeon <tgih.jun@samsung.com> wrote:
> >> > >> >> + } else {
> >> > >> >> + /*
> >> > >> >> + * If we don't have a command complete now we'll
> >> > >> >> + * never get one since we just reset everything;
> >> > >> >> + * better end the request.
> >> > >> >> + *
> >> > >> >> + * If we do have a command complete we'll fall
> >> > >> >> + * through to the SENDING_STOP command and
> >> > >> >> + * everything will be peachy keen.
> >> > >> >> + *
> >> > >> >> + * TODO: I guess we shouldn't send a stop?
> >
> > Please remove TODO:
>
> OK
>
> > We already reset controller in dw_mci_data_complete() through "mmc: dw_mmc: change to use
> recommended reset procedure"?
> > I guess it depends on that patch.
> > Then, we don't need to stop sequence anymore.
>
> Even without that patch we've still pretty much stopped everything in
> dw_mci_fifo_reset(), so I'm not sure there's any strong dependency.
> ...but in our tree this did land after the patch you mention, so you
> could wait until it lands if you want.
>
ciu-reset or stop/abort cmd is needed for recovery of controller FSM after getting error.
dw_mci_fifo_reset eventually has ciu-reset from that patch.
I think it's fine to apply after that.
>
> NOTE: We found that on some machines we were getting warnings after
> enabling tuning and using this patch. The warnings were benign, but
> we should probably squash the fix into this patch. See
> <https://chromium-review.googlesource.com/#/c/200652/> for details.
Can it be accessible?
Thanks,
Seungwon Jeon
>
> -Doug
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-05-21 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 6:18 [PATCH] mmc: dw_mmc: Make sure we don't get stuck when we get an error Yuvaraj Kumar C D
2014-05-08 9:42 ` Yuvaraj Kumar
2014-05-09 3:21 ` Sonny Rao
2014-05-10 14:11 ` Seungwon Jeon
2014-05-12 21:50 ` Doug Anderson
2014-05-13 4:52 ` Seungwon Jeon
2014-05-13 15:56 ` Doug Anderson
2014-05-16 1:46 ` Seungwon Jeon
2014-05-16 16:21 ` Doug Anderson
2014-05-20 1:24 ` Seungwon Jeon
2014-05-20 1:51 ` Seungwon Jeon
2014-05-20 22:08 ` Doug Anderson
2014-05-21 9:05 ` Seungwon Jeon [this message]
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='000f01cf74d3$d2938b40$77baa1c0$%jun@samsung.com' \
--to=tgih.jun@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).