11 files changed, 69 insertions, 15 deletions
diff --git a/projects/linux/io/I2C-add_RECV_LEN-support.yaml b/projects/linux/io/I2C-add_RECV_LEN-support.yaml
index e591a48..496e2aa 100644
--- a/projects/linux/io/I2C-add_RECV_LEN-support.yaml
+++ b/projects/linux/io/I2C-add_RECV_LEN-support.yaml
@@ -2,7 +2,7 @@ title: I2C; add RECV_LEN support to the i2c-rcar driver
 team: IO
 key: 3c3dd6fe-03d9-11eb-ad24-7782efa69bb6
 assignee: Wolfram
-status: Active
+status: Paused
 
 comments:
  - "I2C core preparation:"
@@ -22,3 +22,4 @@ comments:
  - "Revert of the above: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20210209110556.18814-1-wsa+renesas@sang-engineering.com/"
  - "testunit updates:"
  - "add SMBUS_PROC_CALL v1: http://patchwork.ozlabs.org/project/linux-i2c/patch/20210209111927.19169-1-wsa+renesas@sang-engineering.com/"
+ - "stalled because of other priorities"
diff --git a/projects/linux/io/SDHI-upport-BSP-fixes.yaml b/projects/linux/io/SDHI-upport-BSP-fixes.yaml
index 3027d9a..63d80c5 100644
--- a/projects/linux/io/SDHI-upport-BSP-fixes.yaml
+++ b/projects/linux/io/SDHI-upport-BSP-fixes.yaml
@@ -16,6 +16,7 @@ upstream:
 comments:
  - 0237478dc67b71ff92082e06323c015631098b71
    - do we have V3H hardware in Magnus lab?
+   - Magnus so far has only a Condor board, but not v3hsk
  - c2ca1ccb83afd7c790ae361c720d257e050483f2
    - https://patchwork.kernel.org/project/linux-mmc/patch/1605005330-7178-1-git-send-email-yoshihiro.shimoda.uh@renesas.com/
  - 5d60e36aaa96fa39d1a524cc4ff373c0f36616e0
diff --git a/projects/linux/io/Thermal-add-interrupts.yaml b/projects/linux/io/Thermal-add-interrupts.yaml
deleted file mode 100644
index 7685500..0000000
--- a/projects/linux/io/Thermal-add-interrupts.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
-title: Thermal; add interrupts for critical events
-team: IO
-key: c7ddcb6c-9d01-11eb-828f-2f1e3d023263
-assignee: Niklas
-status: New
-
-upstream:
-
-comments:
- - we don't want interrupts for temperature changes but to indicate critical events
diff --git a/projects/linux/io/V3U-enable_CAN.yaml b/projects/linux/io/V3U-enable_CAN.yaml
index 1a18eb0..cc0d9d6 100644
--- a/projects/linux/io/V3U-enable_CAN.yaml
+++ b/projects/linux/io/V3U-enable_CAN.yaml
@@ -1,7 +1,7 @@
 title: V3U; upport CAN driver additions and enable for V3U
 team: IO
 key: 125dd332-ae9e-11eb-bba9-13d957d1734c
-status: Paused
+status: Active
 assignee: Ulrich
 
 bsp41x:
@@ -18,3 +18,4 @@ comments:
     - register layout probably needs to be converted to regmap
     - regmap conversion could be tested on Gen3 locally and on V3U by Renesas in Japan
     - waiting for budget
+    - Ulrich was contracted
diff --git a/projects/linux/io/V3U-enable_RPC.yaml b/projects/linux/io/V3U-enable_RPC.yaml
index 0513747..f687267 100644
--- a/projects/linux/io/V3U-enable_RPC.yaml
+++ b/projects/linux/io/V3U-enable_RPC.yaml
@@ -2,6 +2,7 @@ title: V3U; upport RPC fixes and enable for V3U
 team: IO
 key: af952030-922c-11eb-a0e9-17a4402ca5c4
 status: New
+assignee: Wolfram
 
 bsp41x:
  - c419cfd7766efb7bbc95d964586ca3668b61cdb7 # memory: renesas-rpc-if: Use burst read operation
@@ -21,3 +22,4 @@ comments:
  - "0d37f69cacb3343514380ff4a9c271b746959190 very likely must be refactored. The mixture of regmap and direct register writes does not look good"
  - "because HW access to V3U is still very limited, it is suggested to upport/refactor the driver fixes using locally available boards first"
  - "for that, RPC must be enabled in TFA, cf: https://github.com/ARM-software/arm-trusted-firmware/commit/6e93392b7a761c43c1f4b5b564fe57c51d806388"
+ - "another option is to use Eagle/Condor boards remotely with JFFS2 and check for CRC failures"
diff --git a/projects/linux/io/V3U-enable_TPU_PWM.yaml b/projects/linux/io/V3U-enable_TPU_PWM.yaml
index 06ab5df..10ccde2 100644
--- a/projects/linux/io/V3U-enable_TPU_PWM.yaml
+++ b/projects/linux/io/V3U-enable_TPU_PWM.yaml
@@ -20,3 +20,9 @@ upstream:
 comments:
  - TPU can probably be tested using GPIO_CN with the GPIO logic analyzer
  - testing PWM is currently unclear; BSP also doesn't have PWM on Falcon
+ - TPU
+   - testing TPU with GPIO logic analyzer was successful
+   - V3U enablement
+     - v1; https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=540427&state=*
+   - binding updates
+     - v1; https://lore.kernel.org/all/20210901090719.35375-1-wsa+renesas@sang-engineering.com/
diff --git a/projects/linux/io/done/I2C-support-virtio-upstreaming.yaml b/projects/linux/io/done/I2C-support-virtio-upstreaming.yaml
new file mode 100644
index 0000000..1d92864
--- /dev/null
+++ b/projects/linux/io/done/I2C-support-virtio-upstreaming.yaml
@@ -0,0 +1,26 @@
+title: I2C; support upstream efforts of a virtio interface for I2C
+team: IO
+key: 4d372cc0-eb06-11eb-938b-c38d68bf72e4
+assignee: Wolfram
+status: Done
+
+upstream:
+ - torvalds: 3cfc88380413d20f777dc6648a38f683962e52bf # i2c: virtio: add a virtio i2c frontend driver
+ - next: 8ca662351317bb3d57d690469d22079ac7dff9f9 # dt-bindings: i2c: Add bindings for i2c-virtio
+
+comments:
+ - we originally wanted to do this on our own, now let's assist another team working on it
+ - driver
+   - v10; http://patchwork.ozlabs.org/project/linux-i2c/patch/226a8d5663b7bb6f5d06ede7701eedb18d1bafa1.1616493817.git.jie.deng@intel.com/
+   - v11; http://patchwork.ozlabs.org/project/linux-i2c/patch/510c876952efa693339ab0d6cc78ba7be9ef6897.1625104206.git.jie.deng@intel.com/
+   - v12; http://patchwork.ozlabs.org/project/linux-i2c/patch/f229cd761048bc143f88f33a3437bdbf891c39fd.1625214435.git.jie.deng@intel.com/
+   - v13; http://patchwork.ozlabs.org/project/linux-i2c/patch/8908f35a741e25a630d521e1012494e67d31ea64.1625466616.git.jie.deng@intel.com/
+   - v14; http://patchwork.ozlabs.org/project/linux-i2c/patch/984ebecaf697058eb73389ed14ead9dd6d38fb53.1625796246.git.jie.deng@intel.com/
+   - v15; http://patchwork.ozlabs.org/project/linux-i2c/patch/bcf2fb9bbe965862213f27e05f87ffc91283c0c5.1627018061.git.jie.deng@intel.com/
+   - merged
+  - bindings
+   - v1; http://patchwork.ozlabs.org/project/linux-i2c/patch/e650cecb3bc6a0ed16eb37460ac57cb191ba92e4.1626173013.git.viresh.kumar@linaro.org/
+   - v2; http://patchwork.ozlabs.org/project/linux-i2c/patch/705f4426a17a395bf190ee6ed6c341ac25550f6b.1626947324.git.viresh.kumar@linaro.org/
+   - v3; http://patchwork.ozlabs.org/project/linux-i2c/patch/4182aff2d1437b30025f3d17d11e5fdc21845239.1627273794.git.viresh.kumar@linaro.org/
+   - v4; http://patchwork.ozlabs.org/project/linux-i2c/patch/33c317b95097ce491845c697db1e8285e3ec1d41.1627362340.git.viresh.kumar@linaro.org/
+   - merged
diff --git a/projects/linux/io/PCI-fix-suspend.yaml b/projects/linux/io/done/PCI-fix-suspend.yaml
index 8e7443a..c232a13 100644
--- a/projects/linux/io/PCI-fix-suspend.yaml
+++ b/projects/linux/io/done/PCI-fix-suspend.yaml
@@ -1,7 +1,7 @@
 title: "PCIe: handle suspend problem"
 team: IO
 key: 61128a40-edce-11ea-90d7-7f8bdf62ff21
-status: Active
+status: Done
 assignee: Marek
 
 bsp41x:
@@ -9,6 +9,8 @@ bsp41x:
  - 3283eefba71ffd708c53048e4187dcdbc8638fb3 # PCI: pcie-rcar: Support runtime PM, link state L1 handling
 
 upstream:
+ - torvalds: ce351636c67f75a9f282ab69283be231d2c8e845 # PCI: rcar: Add suspend/resume
+ - next: a115b1bd3af0c2963e72f6e47143724c59251be6 # PCI: rcar: Add L1 link state fix into data abort hook
 
 comments:
   - "PCIe suspend causes an exception which needs to be handled"
@@ -23,3 +25,5 @@ comments:
   - "Marek is busy currently but has not forgotten about it"
   - "v5: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20210411185030.8818-1-marek.vasut@gmail.com/"
   - "v6: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20210514200549.431275-1-marek.vasut@gmail.com/"
+  - "v7: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20210815181650.132579-1-marek.vasut@gmail.com/"
+  - "finally merged!"
diff --git a/projects/linux/io/SCIF-investigate-DMA-limitations.yaml b/projects/linux/io/done/SCIF-investigate-DMA-limitations.yaml
index 3f60909..15f9dde 100644
--- a/projects/linux/io/SCIF-investigate-DMA-limitations.yaml
+++ b/projects/linux/io/done/SCIF-investigate-DMA-limitations.yaml
@@ -1,10 +1,16 @@
 title: SCIF; check DMA problems with SysRq, BREAK and parity errors
 team: IO
 key: 3cdb3c8c-03d9-11eb-91e0-b7234f6a00bc
-status: Active
+status: Done
 assignee: Ulrich
 
+upstream:
+ - next: 87b8061bad9bd4b549b2daf36ffbaa57be2789a2 # serial: sh-sci: fix break handling for sysrq
+
 comments:
  - "check IO IRC log from 2020-10-01 for details"
  - "it seems we need to enable interrupts during DMA again, discard the receive interrupts and deal with break and parity"
  - "Ulrich will try if it works and how it will affect DMA performance"
+ - "Ulrich said it has nothing to do with DMA, break support is broken per se"
+ - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20210816162201.28801-1-uli+renesas@fpond.eu/"
+ - "merged"
diff --git a/projects/linux/io/done/Thermal-add-interrupts.yaml b/projects/linux/io/done/Thermal-add-interrupts.yaml
new file mode 100644
index 0000000..677c5b7
--- /dev/null
+++ b/projects/linux/io/done/Thermal-add-interrupts.yaml
@@ -0,0 +1,15 @@
+title: Thermal; add interrupts for critical events
+team: IO
+key: c7ddcb6c-9d01-11eb-828f-2f1e3d023263
+assignee: Niklas
+status: Done
+
+upstream:
+ - next: 47cf09e0f4fc51200ecea15387bec3584562f55d # thermal/drivers/rcar_gen3_thermal: Add support for hardware trip points
+ - next: d3a2328e741bf6e9e6bda750e0a63832fa365a74 # thermal/drivers/rcar_gen3_thermal: Store TSC id as unsigned int
+
+comments:
+ - we don't want interrupts for temperature changes but to indicate critical events
+ - v1; https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=511979&state=*
+ - v2; https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=526113&state=*
+ - merged
diff --git a/projects/linux/io/V3U-enable_CMT_TMU.yaml b/projects/linux/io/done/V3U-enable_CMT_TMU.yaml
index 7641a47..63b0806 100644
--- a/projects/linux/io/V3U-enable_CMT_TMU.yaml
+++ b/projects/linux/io/done/V3U-enable_CMT_TMU.yaml
@@ -2,7 +2,7 @@ title: V3U; enable CMT and TMU timer
 team: IO
 key: d14a0472-7b3c-11eb-aa9b-7beb02b72542
 assignee: Wolfram
-status: Active
+status: Done
 
 bsp41x:
  - 63d7c98edd0d95500ab568dbfd571695bd977b25 # dt-bindings: timer: renesas, tmu: Document r8a779a0 TMU support
@@ -20,6 +20,7 @@ upstream:
  - torvalds: 0eedab655ec1817d450085dcb12219726cb415ff # clk: renesas: r8a779a0: Add CMT clocks
  - torvalds: 7e2a95d953534ec6297c6ff2356ce8e20da04126 # arm64: dts: renesas: r8a779a0: Add CMT support
  - torvalds: cdbbe6ce26f6e991014596e50d6be280fbc302be # dt-bindings: timer: renesas,tmu: add r8a779a0 TMU support
+ - torvalds: be83c3b6e7b8ff22f72827a613bf6f3aa5afadbb # clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock source channel
 
 comments:
  - "also decide if we want to enable timers in board files or the dtsi"
@@ -47,3 +48,4 @@ comments:
  - "merged"
  - "re-added a35d44aa2e8df18d399e04ccfd8c91666d90520d5, handled by Niklas"
  - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20210422123443.73334-1-niklas.soderlund+renesas@ragnatech.se/"
+ - "merged"