Searched hist:e056a1b5b67b4e4bfad00bf143ab14f634777705 (Results 1 – 2 of 2) sorted by relevance
| /linux/include/linux/mmc/ |
| H A D | core.h | diff e056a1b5b67b4e4bfad00bf143ab14f634777705 Tue Jun 28 16:16:02 CEST 2011 Adrian Hunter <adrian.hunter@intel.com> mmc: queue: let host controllers specify maximum discard timeout
Some host controllers will not operate without a hardware
timeout that is limited in value. However large discards
require large timeouts, so there needs to be a way to
specify the maximum discard size.
A host controller driver may now specify the maximum discard
timeout possible so that max_discard_sectors can be calculated.
However, for eMMC when the High Capacity Erase Group Size
is not in use, the timeout calculation depends on clock
rate which may change. For that case Preferred Erase Size
is used instead.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
|
| /linux/drivers/mmc/core/ |
| H A D | core.c | diff e056a1b5b67b4e4bfad00bf143ab14f634777705 Tue Jun 28 16:16:02 CEST 2011 Adrian Hunter <adrian.hunter@intel.com> mmc: queue: let host controllers specify maximum discard timeout
Some host controllers will not operate without a hardware
timeout that is limited in value. However large discards
require large timeouts, so there needs to be a way to
specify the maximum discard size.
A host controller driver may now specify the maximum discard
timeout possible so that max_discard_sectors can be calculated.
However, for eMMC when the High Capacity Erase Group Size
is not in use, the timeout calculation depends on clock
rate which may change. For that case Preferred Erase Size
is used instead.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
|