summaryrefslogtreecommitdiff
path: root/projects/linux/io/SDHI-HW-busy-timeout.yaml
diff options
context:
space:
mode:
authorWolfram Sang <wsa+renesas@sang-engineering.com>2020-11-26 10:18:22 +0100
committerWolfram Sang <wsa+renesas@sang-engineering.com>2020-11-26 10:18:22 +0100
commitcd4a7636acb273809d43b66bebb16c6aa1e0be1e (patch)
tree27d44a0e60c7f8f14121f7937b99dbd48195aaee /projects/linux/io/SDHI-HW-busy-timeout.yaml
parent4fb3cb542b23eda99998b151c04db6ae71be6f96 (diff)
projects: linux: io: update tasks after updates 20201126
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Diffstat (limited to 'projects/linux/io/SDHI-HW-busy-timeout.yaml')
-rw-r--r--projects/linux/io/SDHI-HW-busy-timeout.yaml7
1 files changed, 6 insertions, 1 deletions
diff --git a/projects/linux/io/SDHI-HW-busy-timeout.yaml b/projects/linux/io/SDHI-HW-busy-timeout.yaml
index 0c260f4..895c004 100644
--- a/projects/linux/io/SDHI-HW-busy-timeout.yaml
+++ b/projects/linux/io/SDHI-HW-busy-timeout.yaml
@@ -1,7 +1,7 @@
title: SDHI; implement support for HW busy timeout
team: IO
key: e2c455e0-1210-11ea-8389-b359bc6084c5
-status: New
+status: Active
upstream:
@@ -9,3 +9,8 @@ comments:
- "currently we use a tasklet to detect busy timeouts"
- "MMC maintainer says this is OKish, but HW timeout would be much better"
- "this is all for supporting MMC_CAP_ERASE properly"
+ - "MMC_CAP_ERASE has been removed meanwhile, and we set max_busy_timeout, too"
+ - "we still should care about handling when data timeouts happen"
+ - "RFT v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=388391&state=*"
+ - "RFT v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=388435&state=*"
+ - "needs some refactoring"