On 4/19/20 12:20 AM, Greg KH wrote:
External email: Use caution opening links or attachments
On Fri, Apr 17, 2020 at 12:14:01PM -0700, Sowjanya Komatineni wrote:
This series includes manually backported changes that implements Tegra
specific timeout callback to switch between finite and infinite HW busy
detection wait modes.
sdhci-tegra driver patch implements set_timeout callback based on one of
the sdhci host driver patch that refactors sdhci_set_timeout and allows
drivers to call __sdhci_set_timeout with their timeout callback
implementation.
Both of these patches are manually backported in this series.
Is this a bugfix or a new feature? I can't tell, but it feels like it's
a new feature. What's wrong with just using the 5.4.y kernel tree?
thanks,
greg k-h
Ulf recent patches for increased timeout adds capability
MMC_CAP_NEED_RSP_BUSY for sdhci-tegra as well.
So, it will always use R1B for R1B type commands so there are no known
bugs or failures with mmc devices we use on our platforms.
So, we can treat this patch as an improvement for long operation
commands where HW will wait as long as device is busy.
Yes, should be fine to have this from 5.4.y
For 5.4.y and 5.5.y, we can back-port same patch that was applied to 5.6.y
Will send back-port request of that..
Thanks
Sowjanya
