4 files changed, 32 insertions, 7 deletions
diff --git a/projects/linux/io/BSP41-need-KF-patches.yaml b/projects/linux/io/BSP41-need-KF-patches.yaml
index 137a78a..03b3f75 100644
--- a/projects/linux/io/BSP41-need-KF-patches.yaml
+++ b/projects/linux/io/BSP41-need-KF-patches.yaml
@@ -19,6 +19,8 @@ upstream:
 comments:
  - only Laurent has a KF board currently which is not available with remote access.
  - most patches here need physical access, though
+ - Wolfram got ULCB + KingFisher now from Laurent
+ - ULCB is bricked because of wrong firmware and needs to be unbricked first
 
  - a6c6f67592709f9c1e5cdc79ff29fb583afb362e
    - another driver went upstream meanwhile with accelerometer and magnetometer
diff --git a/projects/linux/io/SDHI-upport-BSP-fixes.yaml b/projects/linux/io/SDHI-upport-BSP-fixes.yaml
index ae8e27b..c33edeb 100644
--- a/projects/linux/io/SDHI-upport-BSP-fixes.yaml
+++ b/projects/linux/io/SDHI-upport-BSP-fixes.yaml
@@ -1,7 +1,7 @@
 title: SDHI; upport BSP patches
 team: IO
 key: fe6714da-a9b4-11eb-a028-6bbd20fa8e8a
-status: New
+status: Active
 assignee: Wolfram
 
 bsp41x:
@@ -13,22 +13,34 @@ bsp41x:
 
 bsp51x:
  - 1f8eaa32650a2f67cc318f39c603f2c8282831a4 # arm64: dts: r8a77980-v3hsk: Enable onboard eMMC
+ - ef716ad2e21ec228a138e1d22cc1c33e669e492b # arm64: dts: renesas: r8a77980-v3hsk: Disable MMC
  - e533a0ea555e061170b4102d9085c70546fe4768 # mmc: core: Issue power off notification in mmc_remove()
  - 15d7abbfc3f0dae379821824135d94a4f865a449 # mmc: renesas_sdhi: reset calibration register
  - 53c3958c01961421cd2b70c3dfebc9f391e00192 # mmc: renesas_sdhi: Add internal DMA transfer end
  - e54e9682fbc229e7a168d63b2e49bc174353caed # mmc: tmio: Add internal DMA transfer end
+ - 2d111ff70e13073395f33e989ca2ff63b4fb4d2e # mmc: renesas_sdhi: scc_ctl is always set in after R-Car Gen3
+ - ef6598cafe54825b537f47df7846dbcacbc73e88 # mmc: renesas_sdhi: Disable HS400 for r8a77995
+ - e741f08198c2973650cb8965a17337a126ea049e # arm64: dts: renesas: r8a77950-ulcb: disable eMMC
 
 upstream:
 
 comments:
- - 0237478dc67b71ff92082e06323c015631098b71
+ - 0237478dc67b71ff92082e06323c015631098b71, 1f8eaa32650a2f67cc318f39c603f2c8282831a4, ef716ad2e21ec228a138e1d22cc1c33e669e492b
    - do we have V3H hardware in Magnus lab?
    - Magnus so far has only a Condor board, but not v3hsk
- - c2ca1ccb83afd7c790ae361c720d257e050483f2
+   - BSP5.1x patch reverts because voltage specification of MMC is unclear
+   - abandoned unless we get HW ourselves
+ - c2ca1ccb83afd7c790ae361c720d257e050483f2, e533a0ea555e061170b4102d9085c70546fe4768
    - https://patchwork.kernel.org/project/linux-mmc/patch/1605005330-7178-1-git-send-email-yoshihiro.shimoda.uh@renesas.com/
- - 5d60e36aaa96fa39d1a524cc4ff373c0f36616e0
+ - 5d60e36aaa96fa39d1a524cc4ff373c0f36616e0, 15d7abbfc3f0dae379821824135d94a4f865a449
    - before calling 'renesas_sdhi_adjust_hs400_mode_disable()', change the if to 'if (gen3)'?
- - 73405fef502d43737be9a50d29935bee133fe7ab
+ - 73405fef502d43737be9a50d29935bee133fe7ab, 53c3958c01961421cd2b70c3dfebc9f391e00192
    - Only for H3/M3-W ES1.0, but why does mainline work?
- - 20e5623df1aaa74301675122b910f063cdcabe7e
+ - 20e5623df1aaa74301675122b910f063cdcabe7e, e54e9682fbc229e7a168d63b2e49bc174353caed
    - Why does mainline work without it?
+ - 2d111ff70e13073395f33e989ca2ff63b4fb4d2e
+   - needs refactoring
+ - ef6598cafe54825b537f47df7846dbcacbc73e88
+   - can't find it in the docs that HS400 is not supported. But D3 has indeed no strobe pin which is needed
+ - e741f08198c2973650cb8965a17337a126ea049e
+   - commit message mentions silicon bug? Which one?
diff --git a/projects/linux/io/V3U-enable_CAN.yaml b/projects/linux/io/done/V3U-enable_CAN.yaml
index 2ae2618..0c64820 100644
--- a/projects/linux/io/V3U-enable_CAN.yaml
+++ b/projects/linux/io/done/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: Active
+status: Done
 assignee: Ulrich
 
 bsp41x:
@@ -14,6 +14,10 @@ bsp51x:
  - 555f036fa9b0f289f44d57f4e823f835c76a10b5 # arm64: dts: r8a779a0-falcon: Add CANFD support
 
 upstream:
+ - next: 45721c406dcf50d4a20f95afafe8e1a2a7fa2341 # can: rcar_canfd: Add support for r8a779a0 SoC
+ - lore: 20220309162609.3726306-3-uli+renesas@fpond.eu # arm64: dts: renesas: r8a779a0: Add CANFD device node
+ - lore: 20220309162609.3726306-4-uli+renesas@fpond.eu # arm64: dts: renesas: r8a779a0-falcon: enable CANFD 0 and 1
+ - next: d6254d52d70de5301b4fd9acaea5cf1dd8d222b4 # dt-bindings: can: renesas,rcar-canfd: Document r8a779a0 support
 
 comments:
  - we are waiting for physical HW for the developer
@@ -30,3 +34,9 @@ comments:
     - discussing with Kieran and Ulrich how to accomplish this
     - Kieran can connect CAN interfaces of the Falcon board now
     - Uli is working on scripts to ease testing
+    - v2; https://lore.kernel.org/r/20220111162231.10390-1-uli+renesas@fpond.eu
+    - testing revealed that only channels 0+1 work, also with the BSP
+    - so we update the driver but don't enable the other channels upstream
+    - v3; https://lore.kernel.org/r/20220209163806.18618-1-uli+renesas@fpond.eu
+    - v4; https://lore.kernel.org/r/20220309162609.3726306-1-uli+renesas@fpond.eu
+    - merged
diff --git a/projects/linux/io/RPC-enable-burst.yaml b/projects/linux/io/maybe/RPC-enable-burst.yaml
index 426946f..4ea05a7 100644
--- a/projects/linux/io/RPC-enable-burst.yaml
+++ b/projects/linux/io/maybe/RPC-enable-burst.yaml
@@ -10,3 +10,4 @@ upstream:
 
 comments:
  - needs more investigation if burst read support needs more driver updates than this commit
+ - patch dropped from BSP5.1 and no test case, make it a maybe-item