mmc: host: omap_hsmmc: avoid possible overflow of timeout value
authorRavikumar Kattekola <rk@ti.com>
Mon, 30 Jan 2017 10:11:58 +0000 (15:41 +0530)
committerBen Hutchings <ben@decadent.org.uk>
Mon, 5 Jun 2017 20:13:48 +0000 (21:13 +0100)
commit723d852b871c37afdb1f66fb318fc900c35a4f59
tree96bbad92b4774d9cd2c14f92f5e83a30f1909c72
parent3397f7383687aaefb18f6d13e3cc7ca863d1570e
mmc: host: omap_hsmmc: avoid possible overflow of timeout value

commit a53210f56d7f3f75d1edc1b3a069ddb87b72a919 upstream.

Fixes: a45c6cb81647 ("[ARM] 5369/1: omap mmc: Add new omap
hsmmc controller for 2430 and 34xx, v3")

when using really large timeout (up to 4*60*1000 ms for bkops)
there is a possibility of data overflow using
unsigned int so use 64 bit unsigned long long.

Signed-off-by: Ravikumar Kattekola <rk@ti.com>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
[bwh: Backported to 3.2:
 - Drop change in omap_hsmmc_prepare_data()
 - Adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/mmc/host/omap_hsmmc.c