summaryrefslogtreecommitdiff
path: root/projects
diff options
context:
space:
mode:
authorWolfram Sang <wsa+renesas@sang-engineering.com>2019-11-28 17:34:34 +0100
committerWolfram Sang <wsa+renesas@sang-engineering.com>2019-11-28 20:18:29 +0100
commit43717ae31ee76dab029cc6ba0aa07e6cd7688a55 (patch)
tree81ed899916e0200073513b00ac15248336d0d959 /projects
parent4b97f9e0753e82d95c191a8b295c6e3c3d9fa9de (diff)
projects: linux: io: update tasks after updates 20191128
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Diffstat (limited to 'projects')
-rw-r--r--projects/linux/io/I2C-new_device_conversion.yaml6
-rw-r--r--projects/linux/io/SDHI-HW-busy-timeout.yaml11
-rw-r--r--projects/linux/io/SDHI-non_removable_fix.yaml (renamed from projects/linux/io/done/SDHI-non_removable_fix.yaml)8
-rw-r--r--projects/linux/io/bsp397_SDHI.yaml1
-rw-r--r--projects/linux/io/done/RAVB-MTU_with_interface_up.yaml (renamed from projects/linux/io/RAVB-MTU_with_interface_up.yaml)5
-rw-r--r--projects/linux/io/done/SDHI-bugreport_for_ES1.yaml (renamed from projects/linux/io/maybe/SDHI-bugreport_for_ES1.yaml)3
6 files changed, 29 insertions, 5 deletions
diff --git a/projects/linux/io/I2C-new_device_conversion.yaml b/projects/linux/io/I2C-new_device_conversion.yaml
index 19570ce..07da35a 100644
--- a/projects/linux/io/I2C-new_device_conversion.yaml
+++ b/projects/linux/io/I2C-new_device_conversion.yaml
@@ -40,3 +40,9 @@ comments:
- "http://patchwork.ozlabs.org/patch/1150270/"
- "http://patchwork.ozlabs.org/patch/1150271/"
- "http://patchwork.ozlabs.org/project/linux-i2c/list/?series=126277"
+ - "instead of listing patches and patch series, I will follow Morimoto-san's example how to describe big API changes"
+ - "step 1: convert i2c_new_dummy() [mostly done, last driver to be fixed in 5.5-rc1]"
+ - "step 2: convert i2c_new_secondary_device() [done]"
+ - "step 3: convert i2c_new_probed_device() [core changes done, driver changes to be sent after 5.5-rc1]"
+ - "step 4: convert i2c_new_device() [core changes done, driver changes on-going]"
+ - "step 5: remove old API calls [blocked by steps 1-4]"
diff --git a/projects/linux/io/SDHI-HW-busy-timeout.yaml b/projects/linux/io/SDHI-HW-busy-timeout.yaml
new file mode 100644
index 0000000..0c260f4
--- /dev/null
+++ b/projects/linux/io/SDHI-HW-busy-timeout.yaml
@@ -0,0 +1,11 @@
+title: SDHI; implement support for HW busy timeout
+team: IO
+key: e2c455e0-1210-11ea-8389-b359bc6084c5
+status: New
+
+upstream:
+
+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"
diff --git a/projects/linux/io/done/SDHI-non_removable_fix.yaml b/projects/linux/io/SDHI-non_removable_fix.yaml
index 99bcd61..4ce4b2b 100644
--- a/projects/linux/io/done/SDHI-non_removable_fix.yaml
+++ b/projects/linux/io/SDHI-non_removable_fix.yaml
@@ -2,11 +2,11 @@ title: SDHI; remove workaround to enable 'non-removable' property
team: IO
key: 5799545f-2472-4332-aba9-f0909e1d2154
assignee: Wolfram
-status: Done
-target-date: 2019-08-31
+status: Blocked
+target-date: 2019-12-31
relationships:
- - depends: f0a3a834-9c53-41a1-865c-6bbeabefe499
+ - depends: d8082b1e-0535-11ea-b216-574c9e1142f4
upstream:
- torvalds: 8861474a105c91e812d38cd65d3be795c7f32c4f # Revert "mmc: tmio: move runtime PM enablement to the driver implementations"
@@ -21,3 +21,5 @@ comments:
- "maintainer version: https://patchwork.kernel.org/project/linux-mmc/list/?series=173737"
- "version seems to work fine, tested by Geert and Wolfram"
- "workaround removal patch: https://patchwork.kernel.org/patch/11149285/"
+ - "regression was discovered, reopening"
+ - "first investigations showed stalled SCC, so blocking on the SCC clock handling task"
diff --git a/projects/linux/io/bsp397_SDHI.yaml b/projects/linux/io/bsp397_SDHI.yaml
index 7fd10f4..e4125ab 100644
--- a/projects/linux/io/bsp397_SDHI.yaml
+++ b/projects/linux/io/bsp397_SDHI.yaml
@@ -14,6 +14,7 @@ bsp-commits:
- bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434 # mmc: renesas_sdhi: Add manual correction
- 8a21392f2c0472712c208ab3f526bc7ce2ea25ea # mmc: renesas_sdhi: Fix value of Hardware Adjustment Register in HS400
- 8ce90dc51484a7d4f98c2a5f0aa4085e1e33fd85 # mmc: renesas_sdhi: Improved the data structure of quirks
+ - addfe9203290e3c274bca15e64e3f11638649e66 # mmc: renesas_sdhi: Fix hang up in HS400 timing mode selection
upstream:
diff --git a/projects/linux/io/RAVB-MTU_with_interface_up.yaml b/projects/linux/io/done/RAVB-MTU_with_interface_up.yaml
index 6ea4084..905811d 100644
--- a/projects/linux/io/RAVB-MTU_with_interface_up.yaml
+++ b/projects/linux/io/done/RAVB-MTU_with_interface_up.yaml
@@ -2,9 +2,10 @@ title: EtherAVB; configure MTU size while interface is up
team: IO
key: 1463749f-9ca1-47a9-b366-732f77ca206c
assignee: Ulrich
-status: Active
+status: Done
upstream:
+ - next: 15fb35fa9ff456b81159033eba6397fcee85e671 # ravb: implement MTU change while device is up
comments:
- "https://patchwork.kernel.org/patch/10936095/"
@@ -12,3 +13,5 @@ comments:
- "v3 https://patchwork.kernel.org/patch/11104487/"
- "v4 already developed, testing needed"
- "new approach sent to internal list as '[LOCAL RFC] ravb: implement MTU change while device is up'"
+ - "v4 https://patchwork.kernel.org/patch/11242931/"
+ - "accepted and merged"
diff --git a/projects/linux/io/maybe/SDHI-bugreport_for_ES1.yaml b/projects/linux/io/done/SDHI-bugreport_for_ES1.yaml
index ed7f701..c6dfa6d 100644
--- a/projects/linux/io/maybe/SDHI-bugreport_for_ES1.yaml
+++ b/projects/linux/io/done/SDHI-bugreport_for_ES1.yaml
@@ -1,10 +1,11 @@
title: SDHI; validate (and fix) upstream report about accessing large files on ES1.0
team: IO
key: 774f988e-90b9-4946-9cc8-b2f12c6d7765
-status: Paused
+status: Abandoned
upstream:
comments:
- "initial bug report: https://www.spinics.net/lists/linux-mmc/msg52372.html"
- "couldn't be reproduced by Wolfram on his Salvator-X with H3 ES1.0"
+ - "also reporter has not tried the Kernel which Wolfram suggested for a year now, marking abandoned"