From: Douglas Anderson <dianders@chromium.org>
To: jh80.chung@samsung.com, ulf.hansson@linaro.org, shawn.lin@rock-chips.com
Cc: briannorris@chromium.org, amstan@chromium.org,
xzy.xu@rock-chips.com, Douglas Anderson <dianders@chromium.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] mmc: dw_mmc: Fix the CTO timer patch
Date: Wed, 27 Sep 2017 13:56:28 -0700 [thread overview]
Message-ID: <20170927205631.31559-1-dianders@chromium.org> (raw)
Recently we landed 03de19212ea3 ("mmc: dw_mmc: introduce timer for
broken command transfer over scheme"). I found a bunch of problems
with that patch, so this series attempts to solve some of them.
NOTE: this series has only been lighly tested so far. I can at least
reproduce the need for the CTO timer on one of my devices and so I can
confirm that part still works. As mentioned in the 3rd patch I also
ran the mmc_test kernel module on this and did manage to see the 3rd
patch doing something useful.
Douglas Anderson (3):
mmc: dw_mmc: cancel the CTO timer after a voltage switch
mmc: dw_mmc: Fix the CTO timeout calculation
mmc: dw_mmc: Add locking to the CTO timer
drivers/mmc/host/dw_mmc.c | 101 ++++++++++++++++++++++++++++++++++++++++------
1 file changed, 89 insertions(+), 12 deletions(-)
--
2.14.2.822.g60be5d43e6-goog
next reply other threads:[~2017-09-27 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 20:56 Douglas Anderson [this message]
2017-09-27 20:56 ` [PATCH 1/3] mmc: dw_mmc: cancel the CTO timer after a voltage switch Douglas Anderson
2017-10-09 6:57 ` Shawn Lin
2017-09-27 20:56 ` [PATCH 2/3] mmc: dw_mmc: Fix the CTO timeout calculation Douglas Anderson
2017-10-09 7:03 ` Shawn Lin
2017-10-11 23:55 ` Doug Anderson
2017-09-27 20:56 ` [PATCH 3/3] mmc: dw_mmc: Add locking to the CTO timer Douglas Anderson
2017-10-03 18:45 ` Doug Anderson
2017-10-09 7:41 ` Shawn Lin
2017-10-11 23:53 ` 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=20170927205631.31559-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=amstan@chromium.org \
--cc=briannorris@chromium.org \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@linaro.org \
--cc=xzy.xu@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.