From cd4a7636acb273809d43b66bebb16c6aa1e0be1e Mon Sep 17 00:00:00 2001 From: Wolfram Sang Date: Thu, 26 Nov 2020 10:18:22 +0100 Subject: projects: linux: io: update tasks after updates 20201126 Signed-off-by: Wolfram Sang --- projects/linux/io/SDHI-HW-busy-timeout.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'projects/linux/io/SDHI-HW-busy-timeout.yaml') 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" -- cgit v1.2.3