From 2e7dbf124bdaec75e9191732d20a8da49b1eb58f Mon Sep 17 00:00:00 2001 From: Wolfram Sang Date: Thu, 2 Sep 2021 17:27:26 +0200 Subject: projects: linux: io: update tasks after meeting 20210902 Signed-off-by: Wolfram Sang --- projects/linux/io/V3U-enable_RPC.yaml | 2 ++ 1 file changed, 2 insertions(+) (limited to 'projects/linux/io/V3U-enable_RPC.yaml') 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" -- cgit v1.2.3