title: S4; enable IO devices for r8a779f0 team: IO key: 96783090-d6a7-11ec-857c-172fbeb15dc7 assignee: Wolfram status: Done upstream: - torvalds: 525b296185b4b0abab0d35a7143fc5a99c385230 # dt-bindings: timer: renesas,cmt: Add r8a779f0 and generic Gen4 CMT support - torvalds: bd0ed737d5fda2ec55f915ed2c4f586363f71129 # dt-bindings: timer: renesas,cmt: R-Car V3U is R-Car Gen4 - torvalds: aa84506ea644d0952a75136dee7386cc54b234b0 # clocksource/drivers/sh_cmt: Add R-Car Gen4 support - next: 32fb5425547bae46c0d61ec01de1422ffe6d4758 # clk: renesas: r8a779f0: Add CMT clocks - next: d227fcc390e3e995fb8b0cd1d63f8be0ad2b47d3 # arm64: dts: renesas: r8a779f0: Add CMT support - next: e1e62f05d5d9d7726349e00562299d829e478ce9 # spi: renesas,sh-msiof: Add generic Gen4 and r8a779f0 support - next: ea9d001550abaf2f4c75cf4fcd936ea19f932b84 # spi: sh-msiof: add generic Gen4 binding - next: b076fdd02133e6a31db167f8acc368edc2530cc0 # spi: renesas,sh-msiof: R-Car V3U is R-Car Gen4 - next: 644814c1070d9d165b85064e9ff1a80681b560fe # clk: renesas: r8a779f0: Add MSIOF clocks - next: 1cc6987e501d9cb5b83c26da1f07f5e662db7c4c # arm64: dts: renesas: r8a779f0: Add MSIOF nodes - torvalds: 080bcd8d5997b1a615e17cab02bd9d16d1d4fbf3 # [PATCH v2] clk: renesas: r8a779f0: Add HSCIF clocks - torvalds: 599fc76a5a00a3351caf06f96fc8a7e1bf67d9ea # [PATCH] dt-bindings: serial: renesas,hscif: Document r8a779f0 bindings - torvalds: 01a787f78bfd156d61b1844155f1dc4910e446c0 # [PATCH v2] arm64: dts: renesas: r8a779f0: Add HSCIF nodes - torvalds: c62872a6893ffdc38890b00d98d6bab2fce81d2f # [PATCH 1/3] arm64: dts: renesas: r8a779f0: Add DMA properties to SCIF3 - torvalds: 40753144256b63b4e3fb9d80874605dda16ad713 # [PATCH v2] arm64: dts: renesas: r8a779f0: Add SCIF nodes - torvalds: 1614c8624a48b9c9161b2071e9e727bf5a1817ef # arm64: dts: renesas: spider-cpu: Enable SCIF0 on second connector - torvalds: 7b651cc6de2470e112b3e792ba2e7775e1127c04 # mmc: renesas_sdhi: add R-Car Gen4 fallback compatibility string - torvalds: 3576c0b2709c8204a18371d5f8b44a724234ffe7 # dt-bindings: mmc: renesas,sdhi: Document R-Car S4-8 and generic Gen4 support - torvalds: 75fe45a000a70ea35e2071eb7f8b873648590982 # [PATCH] clk: renesas: r8a779f0: Add SDHI0 clock - torvalds: cae45c2d4fb3a9084954f14bf991500c49c970c9 # [PATCH] dt-bindings: mmc: renesas,sdhi: R-Car V3U is R-Car Gen4 - torvalds: 0f6fe934a628b0ce0ba138697064fbc8802c21b1 # [PATCH] dt-bindings: mmc: renesas,sdhi: Add R-Car Gen4 clock requirements - next: 9b5dd1ff705c68549f7a2a91dd8beee14bc543e1 # clk: renesas: r8a779f0: Add sdh0 clock - next: 6a24768c6e301a48c0610f0fac6f4461750ebf16 # arm64: dts: renesas: r8a779f0: Add SDHI0 support - next: 1ada3e53b78afc03d30f5fd7e9d54f297d09cf61 # arm64: dts: renesas: spider-cpu: enable eMMC0 - torvalds: 3c1fa94cd0baca8d573aead43f33785eca66ed42 # dt-bindings: thermal: rcar-gen3-thermal: use positive logic - torvalds: 83b4466b3f1b00da0cbc754e055e89a7b02b2034 # dt-bindings: thermal: rcar-gen3-thermal: Add r8a779f0 support - torvalds: 61a6737fcad8810258bdf1329f063b58ac27b230 # clk: renesas: r8a779f0: Add thermal clock - torvalds: 5b2ca9bc3f1bb1a65e8a2c636047ea51aaa924b1 # thermal: rcar_gen3_thermal: Add r8a779f0 support - torvalds: 404dd7dfb13028d315514f63ed3cf9da46307a39 # thermal: rcar_gen3_thermal: improve logging during probe - torvalds: 5a3ad6f466fe7a187cbf4889d80a48606181c367 # arm64: dts: renesas: r8a779f0: Add thermal support - next: fa7fc5243f9e7d64ea7e73c247218f22499c3479 # dt-bindings: timer: renesas,tmu: Add r8a779f0 support - next: 1e56ebc9872feb2cf9a002c0a23d79a68f6493cb # clk: renesas: r8a779f0: Add TMU and parent SASYNC clocks - next: 7adc69f8ac35109eab2742e6bb7a747dd811d1f6 # arm64: dts: renesas: r8a779f0: Add TMU nodes comments: - CMT0/1 - prototype patches exist, clocksouce-switch test fails for CMT3, needs investigation - the issue with clearing CMCNT happens on V3U as well, Gen3 seems not affected - moving the issue to a seperate task - enablement patches sent out - patches merged - done - HSCIF - HSCIF 0+1 can be muxed to FTDI chips, HSCIF3 to MSIOF headers using an external FTDI, HSCIF2 maybe via unpopulated I2C header - all HSCIFs could be tested, patches sent - patch to switch from SCIF3 to HSCIF0 was dropped because it won't work with all firmware revisions - all other patches merged - done - MSIOF - MSIOF0+2 work. MSIOF1+3 can't be tested because they are parallel with the FTDI serial for debug - enablement patches sent - concluded that MSIOF will be added to S4-8 DTSI file but not to Spider board because the voltage selection is unclear - sent v2 of DTSI addition - merged - done - RPC - not for upstream because RPC shall only be accessed via OPTEE. See BSP commit 1f83a133b853138fad712d0a08a7689aac1e0183 ("Disable SPI flash via RPC") - done - SCIF - SCIF 0+3 can be muxed to FTDI chips, SCIF1 to MSIOF headers using an external FTDI, SCIF4 maybe via unpopulated I2C header - all SCIFs could be tested, patches sent - patches merged - done - SD/MMC - eMMC enabled and works, microSD enabled but still needs testing - first patches sent, only final DTS addition kept until testing is done - SD0H support was missing, resend needed - eMMC works but is too slow compared to BSP, investigation needed - microSD fails the same way the BSP does - Shimoda-san researched that this is because SW6 needs to select the proper voltage - SW is under the heat sink, though. So, for upstream only eMMC is desired - resend patches to enable eMMC only - slower speed than BSP moved to separate task - slower speed was because of wrong kernel config, upstream kernel is actually faster - SD0H patches sent out - patches merged - done - THS/CIVM - first version sent - patch to improve logging needed more versions but we now came to a conclusion - binding documentation needed more versions to handle the differences between all SoCs - all patches merged - done - TMU - probably possible; pinmux to TCLK1-4 and check via non-populated I2C header on breakout board - enablement patches sent out - all patches merged - done - all other devices are in the control domain which we do not handle. Only the application domain is our job. - for a domain overview, check '001_R-CarS4_Bus Architecture_Rev0p70.pptx' (attachment in the S4 docs)