From: Douglas Anderson <dianders@chromium.org>
To: jh80.chung@samsung.com, ulf.hansson@linaro.org, shawn.lin@rock-chips.com
Cc: xzy.xu@rock-chips.com, amstan@chromium.org,
linux-rockchip@lists.infradead.org, briannorris@chromium.org,
linux-samsung-soc@vger.kernel.org, kernel@esmil.dk,
Douglas Anderson <dianders@chromium.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] mmc: dw_mmc: Fix the CTO timer patch, plus the DTO timer
Date: Thu, 12 Oct 2017 13:11:13 -0700 [thread overview]
Message-ID: <20171012201118.23570-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.
This also fixes the DTO timer in some of the same ways even though I
haven't personally seen problems with the DTO timer.
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.
Changes in v2:
- Removed extra "int i"
- Fix the DTO timeout calculation new for v2
- Cleanup the DTO timer new for v2
Douglas Anderson (5):
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
mmc: dw_mmc: Fix the DTO timeout calculation
mmc: dw_mmc: Cleanup the DTO timer like the CTO one
drivers/mmc/host/dw_mmc.c | 162 +++++++++++++++++++++++++++++++++++++++++-----
1 file changed, 146 insertions(+), 16 deletions(-)
--
2.15.0.rc0.271.g36b669edcc-goog
next reply other threads:[~2017-10-12 20:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:11 Douglas Anderson [this message]
2017-10-12 20:11 ` [PATCH v2 2/5] mmc: dw_mmc: Fix the CTO timeout calculation Douglas Anderson
2017-10-12 20:11 ` [PATCH v2 4/5] mmc: dw_mmc: Fix the DTO " Douglas Anderson
2017-10-13 1:02 ` Shawn Lin
[not found] ` <20171012201118.23570-1-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-10-12 20:11 ` [PATCH v2 1/5] mmc: dw_mmc: cancel the CTO timer after a voltage switch Douglas Anderson
2017-10-12 20:11 ` [PATCH v2 3/5] mmc: dw_mmc: Add locking to the CTO timer Douglas Anderson
2017-10-13 1:32 ` Shawn Lin
2017-10-13 4:20 ` Doug Anderson
2017-10-17 0:54 ` Shawn Lin
2017-10-17 16:40 ` Doug Anderson
2017-10-23 17:59 ` Doug Anderson
2017-10-24 1:41 ` Jaehoon Chung
2017-10-12 20:11 ` [PATCH v2 5/5] mmc: dw_mmc: Cleanup the DTO timer like the CTO one Douglas Anderson
2017-10-17 1:17 ` Shawn Lin
2017-10-17 5:05 ` Doug Anderson
2017-10-17 6:33 ` Shawn Lin
2017-10-30 11:40 ` [PATCH v2 0/5] mmc: dw_mmc: Fix the CTO timer patch, plus the DTO timer Ulf Hansson
2017-10-31 7:05 ` Shawn Lin
2017-10-31 18:14 ` Doug Anderson
2017-11-01 14:18 ` Ulf Hansson
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=20171012201118.23570-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=amstan@chromium.org \
--cc=briannorris@chromium.org \
--cc=jh80.chung@samsung.com \
--cc=kernel@esmil.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@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 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).