hpi_time_threshold can be set to configure elapsed time in ms, after which an ongoing request will not be preempted. Explain the hpi_time_threhold parameter for MMC devices. Signed-off-by: Venkatraman S <svenkatr@xxxxxx> --- Documentation/ABI/testing/sysfs-devices-mmc | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Documentation/ABI/testing/sysfs-devices-mmc b/Documentation/ABI/testing/sysfs-devices-mmc index 5a50ab6..133dba5 100644 --- a/Documentation/ABI/testing/sysfs-devices-mmc +++ b/Documentation/ABI/testing/sysfs-devices-mmc @@ -19,3 +19,15 @@ Description: is enabled, this attribute will indicate the size of enhanced data area. If not, this attribute will be -EINVAL. Unit KByte. Format decimal. + +What: /sys/devices/.../mmc_host/mmcX/mmcX:XXXX/hpi_time_threshold +Date: April 2012 +Contact: Venkatraman S <svenkatr@xxxxxx> +Description: + High Priority Interrupt is a new feature defined in eMMC4.4 + standard. If this feature is enabled, stack needs to decide + till what time since the last issued request is considered + preemptible. This attribute value (in milliseconds) is + used for arriving at the most optimal value for a specific + card. Default is zero, which also disables the feature, as + the request becomes non-preemptible immediately. -- 1.7.10.rc2 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
