summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--projects/linux/io/V3U-enable_RPC.yaml24
1 files changed, 17 insertions, 7 deletions
diff --git a/projects/linux/io/V3U-enable_RPC.yaml b/projects/linux/io/V3U-enable_RPC.yaml
index f687267..3b2fd35 100644
--- a/projects/linux/io/V3U-enable_RPC.yaml
+++ b/projects/linux/io/V3U-enable_RPC.yaml
@@ -1,7 +1,7 @@
title: V3U; upport RPC fixes and enable for V3U
team: IO
key: af952030-922c-11eb-a0e9-17a4402ca5c4
-status: New
+status: Active
assignee: Wolfram
bsp41x:
@@ -17,9 +17,19 @@ bsp41x:
upstream:
comments:
- - "85f41a8a4d61f366d1591516349ba2447a59e06f is the revert of 3612986e5109c4de99cd3f75caf5bf6c756ef0f0: no action needed for those"
- - "0d37f69cacb3343514380ff4a9c271b746959190 must be upported before enabling V3U. Otherwise flash memory might get broken, i.e. wrongly fused"
- - "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"
+ - 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, see 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
+ - using the user-partition on an Eagle board turned out to be sufficient
+
+ - c419cfd7766efb7bbc95d964586ca3668b61cdb7
+ - not a bugfix, no need to upport now
+ - needs more investigation if burst read support needs more driver updates
+ - f817442ce56d351a2c69515570ca750edb54622b
+ - needs more information why the undocumented bits were needed previously
+ - 3612986e5109c4de99cd3f75caf5bf6c756ef0f0, 85f41a8a4d61f366d1591516349ba2447a59e06f
+ - no action needed, they revert each other
+ - 0d37f69cacb3343514380ff4a9c271b746959190
+ - must be upported before enabling V3U. Otherwise flash memory might get broken, i.e. wrongly fused
+ - very likely must be refactored. The mixture of regmap and direct register writes does not look good
+ - RFC v1 sent to an internal mailing list