diff options
| author | Dmitry Osipenko <digetx@gmail.com> | 2019-08-12 00:00:35 +0300 |
|---|---|---|
| committer | Thierry Reding <treding@nvidia.com> | 2019-11-11 14:55:26 +0100 |
| commit | b56563d0138c3622634e50f3dbca1359b5e7237b (patch) | |
| tree | 46b198917f7495d5e17652c655992e7f34d191b1 /drivers | |
| parent | f541efaa7459621fb68eb6e54546e195ab48d43a (diff) | |
| download | linux-b56563d0138c3622634e50f3dbca1359b5e7237b.tar.bz2 | |
memory: tegra: Increase handshake timeout on Tegra20
Turned out that it could take over a millisecond under some circumstances,
like running on a very low CPU/memory frequency. TRM says that handshake
happens when there is a "safe" moment, but not explains exactly what that
moment is. Apparently at least memory should be idling and thus the low
frequency should be a reasonable cause for a longer handshake delay.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/memory/tegra/tegra20-emc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/memory/tegra/tegra20-emc.c b/drivers/memory/tegra/tegra20-emc.c index 25a6aad6a7a9..da75efc632c7 100644 --- a/drivers/memory/tegra/tegra20-emc.c +++ b/drivers/memory/tegra/tegra20-emc.c @@ -236,7 +236,7 @@ static int emc_complete_timing_change(struct tegra_emc *emc, bool flush) } timeout = wait_for_completion_timeout(&emc->clk_handshake_complete, - usecs_to_jiffies(100)); + msecs_to_jiffies(100)); if (timeout == 0) { dev_err(emc->dev, "EMC-CAR handshake failed\n"); return -EIO; |