All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-mmc@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH 0/3] tmio: set max_busy_timeout
Date: Wed, 25 Nov 2020 22:29:58 +0100	[thread overview]
Message-ID: <20201125213001.15003-1-wsa+renesas@sang-engineering.com> (raw)

This is a follow-up to the series "mmc: tmio: honor busy timeouts
properly" which I sent out a few days ago. One of the patches there
needs more discussion, so I regrouped the series with another one, and
this is the first outcome. It is solely about max_busy_timeout:

Patch 1 is from the previous series (with the comment from Shimoda-san
addressed) and sets max_busy_timeout with what TMIO always did. Patch 2
introduces a hook and a default fallback for extended timeout ranges.
Patch 3 uses the hook for the extended range of R-Car Gen3 SDHIs.

It has been tested that the applied values make sense. I have not
measured if the MMC core really sends R1 instead of R1B when the desired
timeout value is exceeded. All on a Salvator-XS with R-Car M3N.

The patches are based on mmc/next as of today. The branch is here:

git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/sdhi/extop

Looking forward to comments!

Happy hacking,

   Wolfram


Wolfram Sang (3):
  mmc: tmio: set max_busy_timeout
  mmc: tmio: add hook for custom busy_wait calculation
  mmc: renesas_sdhi: populate hook for longer busy_wait

 drivers/mmc/host/renesas_sdhi_core.c | 23 +++++++++++++++++++++++
 drivers/mmc/host/tmio_mmc.h          |  5 +++++
 drivers/mmc/host/tmio_mmc_core.c     | 22 ++++++++++++++++++++++
 drivers/mmc/host/uniphier-sd.c       |  1 +
 include/linux/mfd/tmio.h             |  7 ++++++-
 5 files changed, 57 insertions(+), 1 deletion(-)

-- 
2.28.0


             reply	other threads:[~2020-11-25 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 21:29 Wolfram Sang [this message]
2020-11-25 21:29 ` [PATCH 1/3] mmc: tmio: set max_busy_timeout Wolfram Sang
2020-11-25 21:30 ` [PATCH 2/3] mmc: tmio: add hook for custom busy_wait calculation Wolfram Sang
2020-11-25 21:34   ` Wolfram Sang
2020-11-25 21:30 ` [PATCH 3/3] mmc: renesas_sdhi: populate hook for longer busy_wait Wolfram Sang
2020-11-25 21:32   ` Wolfram Sang
2020-12-02 13:08 ` [PATCH 0/3] tmio: set max_busy_timeout Yoshihiro Shimoda
2020-12-04 14:38 ` 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=20201125213001.15003-1-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.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.