9 files changed, 77 insertions, 21 deletions
diff --git a/projects/linux/io/I2C-dynamic_client_addresses.yaml b/projects/linux/io/I2C-dynamic_client_addresses.yaml
index 8b6e8d9..4ffe54c 100644
--- a/projects/linux/io/I2C-dynamic_client_addresses.yaml
+++ b/projects/linux/io/I2C-dynamic_client_addresses.yaml
@@ -18,3 +18,4 @@ comments:
   - "prep series v1: http://patchwork.ozlabs.org/project/linux-i2c/list/?series=159794&state=*"
   - "prep series v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=258263&state=*"
   - "refactored bindings docs as preparation: https://patchwork.kernel.org/patch/11491099/"
+  - "not enough worktime for this currently"
diff --git a/projects/linux/io/I2C-implement-HostNotify.yaml b/projects/linux/io/I2C-implement-HostNotify.yaml
index 35f6944..75d3039 100644
--- a/projects/linux/io/I2C-implement-HostNotify.yaml
+++ b/projects/linux/io/I2C-implement-HostNotify.yaml
@@ -10,3 +10,4 @@ comments:
   - "RFC v1: https://patchwork.kernel.org/patch/11635623/"
   - "core fix: https://patchwork.kernel.org/patch/11635635/"
   - "generic binding proposal: https://patchwork.kernel.org/patch/11637351/"
+  - "waiting for the binding proposal to be accepted"
diff --git a/projects/linux/io/IIC-I2C-add-atomic_xfer.yaml b/projects/linux/io/IIC-I2C-add-atomic_xfer.yaml
index cc2f3c3..f818b79 100644
--- a/projects/linux/io/IIC-I2C-add-atomic_xfer.yaml
+++ b/projects/linux/io/IIC-I2C-add-atomic_xfer.yaml
@@ -10,3 +10,6 @@ comments:
   - "Ulrich prototypes the IIC driver first; can refactor non-atomic xfer routine"
   - "IIC v1: https://patchwork.kernel.org/patch/11598605/"
   - "IIC v2: https://patchwork.kernel.org/patch/11612451/"
+  - "IIC prototype tested by Wolfram, works"
+  - "need to ensure how to keep PM domain active that late, trying the reboot notifier"
+  - "reboot notifier v1: https://patchwork.kernel.org/patch/11749121/"
diff --git a/projects/linux/io/PCI-fix-suspend.yaml b/projects/linux/io/PCI-fix-suspend.yaml
new file mode 100644
index 0000000..8962438
--- /dev/null
+++ b/projects/linux/io/PCI-fix-suspend.yaml
@@ -0,0 +1,12 @@
+title: "PCIe: handle suspend problem"
+team: IO
+key: 61128a40-edce-11ea-90d7-7f8bdf62ff21
+status: Active
+assignee: Marek
+
+upstream:
+
+comments:
+  - "PCIe suspend causes an exception which needs to be handled"
+  - "For Gen3, a fix was made for ATF: https://github.com/ARM-software/arm-trusted-firmware/commit/0969397f295621aa26b3d14b76dd397d22be58bf"
+  - "For Gen2, a similar approach needs to be taken with hooks for Linux exception handling"
diff --git a/projects/linux/io/SDHI-manual-calibration.yaml b/projects/linux/io/SDHI-manual-calibration.yaml
index 1b4e73a..8b5e0c1 100644
--- a/projects/linux/io/SDHI-manual-calibration.yaml
+++ b/projects/linux/io/SDHI-manual-calibration.yaml
@@ -25,3 +25,6 @@ comments:
  - "new RFC patchset: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=298229&state=*"
  - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=298683&state=*"
  - "depends on the stalled SCC issue being fixed"
+ - "SCC issues was fixed"
+ - "Testing by Shimoda-san revealed an issue"
+ - "v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=342057&state=*"
diff --git a/projects/linux/io/SDHI-stalled-SCC.yaml b/projects/linux/io/SDHI-stalled-SCC.yaml
deleted file mode 100644
index b3710fb..0000000
--- a/projects/linux/io/SDHI-stalled-SCC.yaml
+++ /dev/null
@@ -1,19 +0,0 @@
-title: "SDHI; SCC may stall if SDnH is not provided"
-team: IO
-key: d593a7de-95e8-11ea-8695-9f6a675410b7
-status: Active
-assignee: Wolfram
-
-relationships:
-
-bsp-commits:
- - addfe9203290e3c274bca15e64e3f11638649e66 # mmc: renesas_sdhi: Fix hang up in HS400 timing mode selection
-
-upstream:
-
-comments:
- - "hang up is surprisingly hard to reproduce but we keep trying"
- - "updated manual calibration patchset makes the issue appear again"
- - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=298209&state=*"
- - "not all error paths covered; we need a new flag in the MMC core. Wolfram will work on it"
- - "delayed because of generic Gen3 board boot problems"
diff --git a/projects/linux/io/I2C-fix-slave-corner-cases.yaml b/projects/linux/io/done/I2C-fix-slave-corner-cases.yaml
index a71c6b3..7b8ef13 100644
--- a/projects/linux/io/I2C-fix-slave-corner-cases.yaml
+++ b/projects/linux/io/done/I2C-fix-slave-corner-cases.yaml
@@ -2,10 +2,11 @@ title: I2C; fix issues when using the slave mode
 team: IO
 key: cd177762-bc48-11ea-af02-1fe19e7a99a4
 assignee: Wolfram
-status: Active
+status: Done
 
 upstream:
   - torvalds: 314139f9f0abdba61ed9a8463bbcb0bf900ac5a2 # i2c: rcar: slave: only send STOP event when we have been addressed
+  - torvalds: 914a7b3563b8fb92f976619bbd0fa3a4a708baae # i2c: rcar: in slave mode, clear NACK earlier
   - torvalds: eb01597158ffb1853a7a7fc2c57d4c844640f75e # i2c: rcar: always clear ICSAR to avoid side effects
   - torvalds: c7c9e914f9a0478fba4dc6f227cfd69cf84a4063 # i2c: rcar: avoid race when unregistering slave
 
@@ -13,10 +14,13 @@ comments:
   - "Issue 1: we should not monitor every STOP but only when we have been addressed"
   - "v1 https://patchwork.kernel.org/patch/11632397/"
   - "v2 https://patchwork.kernel.org/patch/11632107/"
-  - "v1 merged"
+  - "v1 merged, v2 was not really better"
 
   - "Issue 2: how to properly handle the FNA bit"
   - "working prototype exists, waiting for confirmation from the HW team"
+  - "HW team acknowledged the prototype"
+  - "v1 https://patchwork.kernel.org/patch/11718127/"
+  - "v1 merged"
 
   - "Issue 3: do we need to clear SAR when disabling the slave interface?"
   - "working prototype exists, needs confirmation from the HW team"
diff --git a/projects/linux/io/done/SDHI-refactor-reset.yaml b/projects/linux/io/done/SDHI-refactor-reset.yaml
new file mode 100644
index 0000000..a88f43f
--- /dev/null
+++ b/projects/linux/io/done/SDHI-refactor-reset.yaml
@@ -0,0 +1,22 @@
+title: "SDHI; refactor reset into proper reset and hw_reset"
+team: IO
+key: b408bad6-edcd-11ea-942b-eb603d86bc58
+status: Done
+assignee: Wolfram
+
+bsp-commits:
+
+upstream:
+ - next: f4a8fe7eb26bedc3d8f8b4e8fa3957d87eb21caf # mmc: renesas_sdhi: move wrong 'hw_reset' to 'reset'
+ - next: 794d69bca9631018dd949e7f3a1b4237d5f28f88 # Revert "mmc: tmio: fix reset operation"
+ - next: f3b5f54f8b0086d78e4b004d48d0abe23a65d0fd # mmc: tmio: remove indirection of 'hw_reset' callback
+ - next: b306d0f4d4a5909902dc1fd773456cabe757bfed # mmc: tmio: factor out common parts of the reset routine
+ - next: c9358732c78bfeab01a168776494a8e337127553 # mmc: tmio: remove indirection of 'execute_tuning' callback
+ - next: 1fcf371e4a41d02cc72d5b928e5bf424f20268b9 # mmc: tmio: remove indirection of 'execute_tuning' callback
+
+comments:
+ - "Shimoda-san reported that after IP core reset, some card initialization needs to be done again"
+ - "Wolfram then evaluated that the usage of reset and hw_reset in the SDHI driver is different from what the MMC core expects"
+ - "a proper refactoring was needed"
+ - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=335877&state=*"
+ - "v1 merged"
diff --git a/projects/linux/io/done/SDHI-stalled-SCC.yaml b/projects/linux/io/done/SDHI-stalled-SCC.yaml
new file mode 100644
index 0000000..c463361
--- /dev/null
+++ b/projects/linux/io/done/SDHI-stalled-SCC.yaml
@@ -0,0 +1,29 @@
+title: "SDHI; SCC may stall if SDnH is not provided"
+team: IO
+key: d593a7de-95e8-11ea-8695-9f6a675410b7
+status: Done
+assignee: Wolfram
+
+relationships:
+
+bsp-commits:
+ - addfe9203290e3c274bca15e64e3f11638649e66 # mmc: renesas_sdhi: Fix hang up in HS400 timing mode selection
+
+upstream:
+ - next: 070d38ad4b5380d291089e1f03b4918d8132a156 # mmc: core: when downgrading HS400, callback into drivers earlier
+ - next: e2fa339c67440bb73fa324dcbb6a7567a524d134 # mmc: core: add a 'doing_init_tune' flag and a 'mmc_doing_tune' helper
+ - next: 81aef391ceada9264bf43f7203b58b49a7d5d81e # mmc: renesas_sdhi: keep SCC clock active when tuning
+
+comments:
+ - "hang up is surprisingly hard to reproduce but we keep trying"
+ - "updated manual calibration patchset makes the issue appear again"
+ - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=298209&state=*"
+ - "not all error paths covered; we need a new flag in the MMC core. Wolfram will work on it"
+ - "delayed because of generic Gen3 board boot problems"
+ - "patches for MMC core updates exists. However, currently not possible to trigger the issue again"
+ - "issue could be triggered again once"
+ - "patch to inject the fault for stalled SCC was created"
+ - "MMC core updates could be tested and worked"
+ - "v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=341697&state=*"
+ - "v2 tested and reviewed by Shimoda-san"
+ - "v2 merged"