From 43717ae31ee76dab029cc6ba0aa07e6cd7688a55 Mon Sep 17 00:00:00 2001 From: Wolfram Sang Date: Thu, 28 Nov 2019 17:34:34 +0100 Subject: projects: linux: io: update tasks after updates 20191128 Signed-off-by: Wolfram Sang --- projects/linux/io/I2C-new_device_conversion.yaml | 6 ++++++ projects/linux/io/RAVB-MTU_with_interface_up.yaml | 14 ------------ projects/linux/io/SDHI-HW-busy-timeout.yaml | 11 ++++++++++ projects/linux/io/SDHI-non_removable_fix.yaml | 25 ++++++++++++++++++++++ projects/linux/io/bsp397_SDHI.yaml | 1 + .../linux/io/done/RAVB-MTU_with_interface_up.yaml | 17 +++++++++++++++ projects/linux/io/done/SDHI-bugreport_for_ES1.yaml | 11 ++++++++++ projects/linux/io/done/SDHI-non_removable_fix.yaml | 23 -------------------- .../linux/io/maybe/SDHI-bugreport_for_ES1.yaml | 10 --------- 9 files changed, 71 insertions(+), 47 deletions(-) delete mode 100644 projects/linux/io/RAVB-MTU_with_interface_up.yaml create mode 100644 projects/linux/io/SDHI-HW-busy-timeout.yaml create mode 100644 projects/linux/io/SDHI-non_removable_fix.yaml create mode 100644 projects/linux/io/done/RAVB-MTU_with_interface_up.yaml create mode 100644 projects/linux/io/done/SDHI-bugreport_for_ES1.yaml delete mode 100644 projects/linux/io/done/SDHI-non_removable_fix.yaml delete mode 100644 projects/linux/io/maybe/SDHI-bugreport_for_ES1.yaml (limited to 'projects/linux/io') 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/RAVB-MTU_with_interface_up.yaml b/projects/linux/io/RAVB-MTU_with_interface_up.yaml deleted file mode 100644 index 6ea4084..0000000 --- a/projects/linux/io/RAVB-MTU_with_interface_up.yaml +++ /dev/null @@ -1,14 +0,0 @@ -title: EtherAVB; configure MTU size while interface is up -team: IO -key: 1463749f-9ca1-47a9-b366-732f77ca206c -assignee: Ulrich -status: Active - -upstream: - -comments: - - "https://patchwork.kernel.org/patch/10936095/" - - "v2 https://patchwork.kernel.org/patch/10977185/" - - "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'" 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/SDHI-non_removable_fix.yaml b/projects/linux/io/SDHI-non_removable_fix.yaml new file mode 100644 index 0000000..4ce4b2b --- /dev/null +++ b/projects/linux/io/SDHI-non_removable_fix.yaml @@ -0,0 +1,25 @@ +title: SDHI; remove workaround to enable 'non-removable' property +team: IO +key: 5799545f-2472-4332-aba9-f0909e1d2154 +assignee: Wolfram +status: Blocked +target-date: 2019-12-31 + +relationships: + - depends: d8082b1e-0535-11ea-b216-574c9e1142f4 + +upstream: + - torvalds: 8861474a105c91e812d38cd65d3be795c7f32c4f # Revert "mmc: tmio: move runtime PM enablement to the driver implementations" + - torvalds: aa86f1a3887523d78bfadd1c4e4df8f919336511 # mmc: tmio: Fixup runtime PM management during probe + - torvalds: 87b5d602a1cc76169b8d81ec2c74c8d95d9350dc # mmc: tmio: Fixup runtime PM management during remove + - next: 2eac14c380b16ae649ec39fe1d7fffd6b49a57c6 # mmc: tmio: remove workaround for NON_REMOVABLE + +comments: + - "v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=146493" + - "v2 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=153581" + - "v2 maintainer offered a better solution, we need to wait a little" + - "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/done/RAVB-MTU_with_interface_up.yaml b/projects/linux/io/done/RAVB-MTU_with_interface_up.yaml new file mode 100644 index 0000000..905811d --- /dev/null +++ b/projects/linux/io/done/RAVB-MTU_with_interface_up.yaml @@ -0,0 +1,17 @@ +title: EtherAVB; configure MTU size while interface is up +team: IO +key: 1463749f-9ca1-47a9-b366-732f77ca206c +assignee: Ulrich +status: Done + +upstream: + - next: 15fb35fa9ff456b81159033eba6397fcee85e671 # ravb: implement MTU change while device is up + +comments: + - "https://patchwork.kernel.org/patch/10936095/" + - "v2 https://patchwork.kernel.org/patch/10977185/" + - "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/done/SDHI-bugreport_for_ES1.yaml b/projects/linux/io/done/SDHI-bugreport_for_ES1.yaml new file mode 100644 index 0000000..c6dfa6d --- /dev/null +++ b/projects/linux/io/done/SDHI-bugreport_for_ES1.yaml @@ -0,0 +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: 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" diff --git a/projects/linux/io/done/SDHI-non_removable_fix.yaml b/projects/linux/io/done/SDHI-non_removable_fix.yaml deleted file mode 100644 index 99bcd61..0000000 --- a/projects/linux/io/done/SDHI-non_removable_fix.yaml +++ /dev/null @@ -1,23 +0,0 @@ -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 - -relationships: - - depends: f0a3a834-9c53-41a1-865c-6bbeabefe499 - -upstream: - - torvalds: 8861474a105c91e812d38cd65d3be795c7f32c4f # Revert "mmc: tmio: move runtime PM enablement to the driver implementations" - - torvalds: aa86f1a3887523d78bfadd1c4e4df8f919336511 # mmc: tmio: Fixup runtime PM management during probe - - torvalds: 87b5d602a1cc76169b8d81ec2c74c8d95d9350dc # mmc: tmio: Fixup runtime PM management during remove - - next: 2eac14c380b16ae649ec39fe1d7fffd6b49a57c6 # mmc: tmio: remove workaround for NON_REMOVABLE - -comments: - - "v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=146493" - - "v2 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=153581" - - "v2 maintainer offered a better solution, we need to wait a little" - - "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/" diff --git a/projects/linux/io/maybe/SDHI-bugreport_for_ES1.yaml b/projects/linux/io/maybe/SDHI-bugreport_for_ES1.yaml deleted file mode 100644 index ed7f701..0000000 --- a/projects/linux/io/maybe/SDHI-bugreport_for_ES1.yaml +++ /dev/null @@ -1,10 +0,0 @@ -title: SDHI; validate (and fix) upstream report about accessing large files on ES1.0 -team: IO -key: 774f988e-90b9-4946-9cc8-b2f12c6d7765 -status: Paused - -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" -- cgit v1.2.3