Hi Wolfram-san, > From: Wolfram Sang, Sent: Thursday, November 26, 2020 6:30 AM > > 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. Thank you for the patch! I tested on Salvator-XS with R-Car H3 and I checked the MMC core use R1 instead of R1B by using an additional printk on mmc_do_erase(). So, Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@xxxxxxxxxxx> Tested-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@xxxxxxxxxxx> Best regards, Yoshihiro Shimoda
